* feat: installer detects Python version and warns when 3.11+ (tomllib) is missing
Several BMAD features need Python at runtime: memlog (3.8+) and the TOML
config resolution scripts (3.11+ for stdlib tomllib). Users install into
varied environments (Linux, Windows, WSL, Docker) where Python may be
missing or too old, and previously only found out via runtime errors.
The installer now probes PATH at startup (py -3 / python3 / python) and
classifies the result: 3.11+ passes silently with a success line; 3.8-3.10
or missing/too-old Python gets a warning naming exactly which features
degrade, plus per-platform install hints. The warning requires an explicit
ack — continue (fix later, no reinstall needed) or quit and re-run after
installing Python. Warn-don't-block: most of BMAD works without Python, so
the install is never refused. In --yes mode the warning logs and continues
without prompting.
* fix: align Python check with runtime truth (python3) and harden edge cases
Review fixes for the installer Python check:
- Probe python3 first on all platforms: every runtime call site invokes a
literal python3, so only that command vouches for BMAD features. Python
found via py/python now gets an explicit mismatch warning instead of a
false "all BMAD features supported".
- Treat closed/piped stdin as non-interactive (in addition to --yes) so
scripted installs no longer silently exit 0 via clack's cancel path.
- Retry probes with shell:true on win32 EINVAL (CVE-2024-27980 hardening
rejects .bat/.cmd shims like pyenv-win's without a shell).
- Add Suite 46 branch tests for checkPythonEnvironment with stubbed
detection, prompts, and process.exit.
Brian