docs: record rc9 production governance rollout

[evergardener]

What changed

• update the handoff baseline to the deployed rc.9 immutable revision
• record the authorized H5 production apply and idempotent replay evidence
• record the pre/post restore-verified backups, Hermes read-only UAT, and remaining review items
• preserve the distinction between runtime PASS and the existing DEGRADED quality status

Why

The source documents still described the pre-authorization rc.8 state after rc.9 was published and deployed. This PR aligns the durable handoff and governance reports with the verified production state without changing runtime code.

Validation

• production runtime Gate: PASS
• H5 apply: 36 governed, 22 evidence merged, candidates 38 to 2
• idempotent replay: already applied, zero writes
• restore verification and Vault roundtrip: PASS before and after H5
• Hermes jiuyue browse, recall, and trace: PASS
• front-end login page load and console check: PASS
• documentation diff check: PASS

Remaining boundaries

• do not replay the three existing failed jobs without separate authorization
• do not decide the two retained review items automatically
• do not promote beyond canary_active from this documentation PR