Replace the standalone python3 environment check with a uv check, since
uv is becoming the de facto standard for running BMad's Python scripts
(`uv run <script>`) and uv provisions the interpreter itself.
Installer:
- Remove tools/installer/core/python-check.js and its wiring in ui.js
- Add tools/installer/core/uv-check.js: warn-don't-block, no ack prompt
(the migration is in progress, so a missing uv never blocks install).
Missing uv warns and points the user at setup, preferring "ask your
agent to set up uv"
- Add a uv heads-up to the install intro (install-messages.yaml) and a
uv tip line to the final "BMAD is ready" summary box
- Swap test Suite 46 from python-check to uv-check coverage
Docs and script comments (no functional skill invocations changed):
- resolve_config.py / resolve_customization.py docstrings: drop the
"No uv ... plain python3 is sufficient" claims; frame uv run as the
standard, python3 as the transition fallback; examples use uv run
- customize-bmad.md (en/fr/vi-vn): same reframing; example commands use
uv run
- Update uv run hints in brain.py / list_customizable test comments