feat(bmad): 6.10 compatibility hardening + quick-dev refresh

[ikunin]

Makes Sprintpilot correct against BMAD Method v6.10 (was tested-through v6.8), verified against the real bmad-method@6.10.0 package. All six invoked skills present; invoked surface byte-stable.

Compatibility hardening

• config.toml tolerance — new _Sprintpilot/lib/runtime/bmad-output.js (dedupes 3 copy-pasted output_folder readers) prefers config.yaml, falls back to the v6.4+ _bmad/config.toml / config.user.toml; installer mirror in lib/core/bmad-config.js. Confirmed necessary — the 6.10 installer writes config.toml as the primary config.
• Soft version guard — checkBmadCompat() warns (never blocks) at install when BMad is below floor or above tested-through.
• sprint-status resilience — all three readers verified robust to v6.9 retrospective action-items (bracketed top-level + nested fixtures).
• code-review heading tolerance — verifyCodeReview accepts v6.10 heading variants (heading confirmed still ### Review Findings; kept strict findings[] contract).
• memlog non-conflict — ARCHITECTURE note + static guard test.
• manifest — tested-through → v6.10.0 (floor stays >=6.2.1) + parseable bmad_tested_through.

Quick-dev (nano) refresh

• Lock-in test: verifyNanoQuickDev requires terminal done even as 6.10 quick-dev self-syncs sprint-status through in-progress/review/done.

Docs (design)

• docs/bmad-dev-auto-evaluation.md — dev-auto/bmad-loop spike (stay differentiated; never run bmad-loop concurrently).
• docs/quick-dev-fast-lane-plan.md — approved design for a per-story fast lane (build tracked separately).

Verification

• cd tests && npm test → 2267 passed (+33), 0 failures
• Biome clean; orchestrator files node --check clean

Version bump/publish intentionally deferred to /release.

🤖 Generated with Claude Code