Sprint 17.G — Align release documentation and promotion status

[maruson08]

Goal

Leave one accurate, explicit v2 release-readiness conclusion without promoting or deploying.

Acceptance criteria

• Reconcile README, CHANGELOG, release QA, UX audit, and actual GitHub v1 release facts.
• Update CI/release documentation only where concrete gaps exist.
• State exactly READY FOR PROMOTION, READY EXCEPT MANUAL QA, or BLOCKED.
• List all remaining blockers precisely.
• Do not merge v2 to main or publish a release.

[maruson08]

Completed in PR #44. README, changelog, historical v1 QA context, UX audit, and the live v2 promotion decision are aligned as READY EXCEPT MANUAL QA.