Execute the v2.0 release-candidate to GA checklist

[HsiangNianian]

Parent

• [RFC-0005] Verification, Documentation, and Release #2

What to build

Run the complete v2 release checklist against candidate artifacts, including clean-room installation, v1 upgrade and migration checks, documentation publication, rollback readiness, and post-release smoke verification.

Acceptance criteria

• Candidate wheels and source distribution pass clean-room installation on the supported matrix.
• Documented v1 upgrade and v2 migration paths are exercised against released artifacts.
• PyPI, CLI, SDK, and documentation smoke checks pass from public endpoints.
• No P0 or P1 issue remains open when GA is published.
• Rollback, yank, and one-week observation ownership are recorded.

Blocked by

• Rebuild the production documentation information architecture #20
• Use the real grammar as the documentation source and fix project links #25
• Install and smoke-test every supported wheel target #30
• Harden trusted publishing and release provenance #34
• Ship v1-to-v2 language compatibility diagnostics and migration guidance #29
• Harden Program-aware CLI and TUI error, progress, and command flows #28

RFC-0005 contract

Execute the RFC-0005 M5 mapping for v2.0.0 and verify every cumulative evidence record, public endpoint, artifact digest, milestone link, observation owner, and rollback owner. A green build alone is not GA completion.