Make production launch the immediate overhaul milestone

[kim-em]

This maintainer scope amendment shortens the launch critical path without changing the retained product surface.

• limits exact-candidate live prelaunch evidence to the browser and headless archive/evaluate/Result/State paths
• accepts repository coverage and the retained bounded staging evidence for optional lifecycle routes
• binds live publication opt-in to the private-first production canary
• preserves independent flags and rollback for the launch-enabled lifecycle APIs
• keeps full completion calendar-bound by overlap/notice and the canary’s first automatic release
• records the now-terminal exact-f03 staging acceptance and all-false cleanup

Current terminal bindings: staging State c604bb446a51fc833c96887053ec64672c912d8c, staging Results 1deb87414faf64edfa31639a8430fcf98fb2ccb5, audit 666950ce7702d1d2a1392b12f9104781ac9446e3. State validation run 33582505523 passed; callback run 33577385219 attempt 2 passed.

Local checks: git diff --check, Markdown heading/local-link validation, and action-pin audit.