Release: re-pause temporary Netlify hotfix gate

[daliu]

Makes the completed #457 release manifest inactive and records the verified production result. This is the mandatory shutdown step after the exact page-header release.

Refs #457

Officer impact: no visible page change; ordinary Git-triggered Netlify production builds return to their paused state.

Officer documentation: OFFICER_START_HERE.md, docs/officers/README.md, docs/officers/PUBLISH_AND_CHECK.md, docs/officers/REQUEST_A_CHANGE.md, docs/officers/ACCESS_CONTINUITY.md, and docs/officers/SYSTEM_MAPS.md, plus matching root design, security, implementation, README, and runbook records.

Deployment evidence: Netlify deploy 6a61c544171ea80008307623 and runmprc.com were verified on 2026-07-23 America/Los_Angeles. The marker matches trigger 4f67e6cafb975a3f985fefc67f094b3a37526702, source ed1b0833f25822cee80c99ded8753722b5608a3f, tree 878c6628d961f4484cb49208aef53f1e9f2e3b47, 60 files, and digest 7570955c2a00926e5813aef135f1799172cfd046072ac89fb4e492bed0797092. Desktop and 390px phone checks passed. Firebase and outside providers are unchanged.

Shutdown proof:

• active changes from true to false.
• Focused policy tests pass 12/12, including inactive-manifest refusal.
• codex/netlify-source-457-header is deleted and verified absent.
• The exact rollback ref remains at e86a0f702cff6495f50630c5de3337290db8b8cb; draft Rollback: prepare exact pre-header Netlify artifact #462 has a current green preview.
• Netlify must skip the production attempt for this merge, leaving deploy 6a61c544171ea80008307623 live.

Merge requirement: use a normal merge commit after current-head checks pass, then confirm the Netlify production attempt is skipped and the live marker remains unchanged.

[netlify]

✅ Deploy Preview for luminous-fox-7c393f ready!

Name	Link
🔨 Latest commit	69f59b9
🔍 Latest deploy log	https://app.netlify.com/projects/luminous-fox-7c393f/deploys/6a61c81e01e3f90008da981b
😎 Deploy Preview	https://deploy-preview-463--luminous-fox-7c393f.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[daliu]

Post-release shutdown evidence (2026-07-23 America/Los_Angeles):

• Production deploy 6a61c544171ea80008307623 is ready from merge 4f67e6cafb975a3f985fefc67f094b3a37526702.
• runmprc.com/.well-known/run-mprc-release.json matches source ed1b0833f25822cee80c99ded8753722b5608a3f, tree 878c6628d961f4484cb49208aef53f1e9f2e3b47, 60 files, and digest 7570955c2a00926e5813aef135f1799172cfd046072ac89fb4e492bed0797092.
• Live desktop and 390px phone checks passed for Events, Shop, and the signed-out Account/Login path.
• codex/netlify-source-457-header is deleted and verified absent. The exact rollback ref remains at e86a0f702cff6495f50630c5de3337290db8b8cb.
• This PR sets only the release authority to inactive, adapts its tests, and records dated website evidence. The production ignore command returns success for an inactive manifest, which means Netlify skips the build rather than replacing the live deploy.

Officer impact: no visible page change; ordinary Git-triggered Netlify production builds return to their paused state.

Officer documentation: OFFICER_START_HERE.md, docs/officers/README.md, docs/officers/PUBLISH_AND_CHECK.md, docs/officers/REQUEST_A_CHANGE.md, docs/officers/ACCESS_CONTINUITY.md, and docs/officers/SYSTEM_MAPS.md, plus matching root design/security/runbook records.

Deployment evidence: website is live and verified; this follow-up must be observed as skipped after merge; Firebase and outside providers remain unchanged.

[daliu]

Temporarily closing and reopening at the same reviewed head because GitHub Actions did not emit a run for 69f59b9 after the force update. No code or production state is changing.

[daliu]

Post-merge production-safety verification completed on 2026-07-23.

• Merged as 04d6d2cd88dda0e6ec7e2b6a71514e6ce2e4db25.
• Current-head PR runs 29989755752 and 29989805911 passed all five jobs; post-merge main run 29989945103 also passed.
• Netlify created production attempt 6a61ca460c41450008ee531d for the merge with state error, published_at: null, and no deploy time, as expected from the inactive gate.
• Netlify provider readback still reports published deploy 6a61c544171ea80008307623 at release control commit 4f67e6cafb975a3f985fefc67f094b3a37526702.
• https://runmprc.com/.well-known/run-mprc-release.json remains byte-for-byte consistent with the released source/tree/file-count/digest, and live bundles remain main.9ab083e3.js / main.9b75243f.css.

Officer impact: ordinary main merges are paused from publishing the website again.

Officer documentation: updated in this PR.

Deployment evidence: Netlify skip attempt, provider published-deploy readback, public marker/bundle readback, and GitHub Actions verified. Firebase and outside providers were unchanged.