Release: deploy exact page-header hotfix to Netlify

[daliu]

Publishes the already reviewed Events, Shop, and Account header fix as one exact, web-only Netlify artifact while keeping every ordinary production build paused.

Refs #457

Officer impact: Events, Shop, and My Account regain readable headings and page images; the shared header layout prevents the same overlap on every page that uses it.

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, docs/officers/GLOSSARY.md, and docs/officers/SYSTEM_MAPS.md.

Deployment evidence: exact local pinned build passed with source ed1b0833f25822cee80c99ded8753722b5608a3f, tree 878c6628d961f4484cb49208aef53f1e9f2e3b47, 60 files, and SHA-256 7570955c2a00926e5813aef135f1799172cfd046072ac89fb4e492bed0797092; exact Netlify Deploy Preview and live runmprc.com checks are pending. Firebase, Functions, Rules, provider configuration, and production data are unchanged.

Release controls:

• Production authorizes only a two-parent merge whose first parent is 491cc22d80de1faae1960bd63c80ce62e648397b.
• Preview and production fetch the same release-specific ref in a clean credential-free repository and verify the exact source, tree, artifact count, and artifact digest.
• The pinned build receives no React/provider or server credential environment.
• Build hooks and every uncertain state fail closed.
• Exact rollback source e86a0f702cff6495f50630c5de3337290db8b8cb is prepared on codex/issue-457-netlify-rollback.
• codex/issue-457-netlify-repause disables the gate after successful live verification.

Merge requirement: use a merge commit only. Squash and rebase merges are incompatible with the exact-parent production policy.

Verification:

• node --test tests/release-workflow.test.js — 12/12 passed
• Full frontend suite — 14 suites, 727/727 passed
• SPA navigation suite — 11/11 passed
• Exact pinned build — passed
• git diff --check — passed

[netlify]

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

Name	Link
🔨 Latest commit	308905c
🔍 Latest deploy log	https://app.netlify.com/projects/luminous-fox-7c393f/deploys/6a61c2b3da28ae0008d31785
😎 Deploy Preview	https://deploy-preview-461--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]

Reopening immediately to obtain a fresh CI run for the shallow-checkout test correction at 4903614; the exact Netlify preview is already ready.

[daliu]

Final review evidence (2026-07-22 America/Los_Angeles):

• Current head 308905c72a41c1f11f79027046ace22393e85988; exact base 491cc22d80de1faae1960bd63c80ce62e648397b.
• All five GitHub CI jobs passed in run 29988513494.
• Netlify preview deploy 6a61c2b3da28ae0008d31785 is ready. Its public marker matches source ed1b0833f25822cee80c99ded8753722b5608a3f, tree 878c6628d961f4484cb49208aef53f1e9f2e3b47, 60 files, and digest 7570955c2a00926e5813aef135f1799172cfd046072ac89fb4e492bed0797092.
• Desktop and 390px phone checks show Events and Shop hero images and readable headings below the navigation. /account safely redirects signed-out visitors to the readable Login hero; authenticated Account layout is covered by the reviewed source/tests without using production member data.
• Rollback preview Rollback: prepare exact pre-header Netlify artifact #462 is ready and matches the current live JS/CSS artifact.
• Three independent code/security/release reviews report no blocker.

Officer impact: Events, Shop, and My Account headers become readable and image-backed through the shared page-header component.

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, docs/officers/GLOSSARY.md, and docs/officers/SYSTEM_MAPS.md.

Deployment evidence: website preview verified as above; production pending this merge; Firebase and outside providers are unchanged.

Admin merge is used only to satisfy the user-authorized release because the PR author cannot approve their own PR. Merge method remains merge commit, as required by the production gate.

[daliu]

Date correction for the final review evidence: Netlify published at 2026-07-23 00:41 America/Los_Angeles, so the dated production verification is 2026-07-23. The hashes, deploy IDs, and results in the earlier comment are unchanged.