Skip to content

WEB-001A2: record isolated Firebase staging deployment - #666

Merged
daliu merged 1 commit into
mainfrom
codex/issue-665-firebase-staging
Aug 26, 2026
Merged

WEB-001A2: record isolated Firebase staging deployment#666
daliu merged 1 commit into
mainfrom
codex/issue-665-firebase-staging

Conversation

@daliu

@daliu daliu commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Record the club-owned run-mprc-staging Firebase project and first static Hosting release.
  • Document exact source/version and signed-out desktop, phone, direct-route, and empty-data readback.
  • Preserve the boundary: staging has no backend/provider test estate, protected release authority, marker, rollback, security-header policy, or production role.

Officer impact: Officers now have a clear, public status for engineering staging and a firm warning not to sign in, enter data, deploy, or treat it as production or a fallback.

Officer documentation: OFFICER_START_HERE.md; docs/officers/PUBLISH_AND_CHECK.md; docs/officers/SYSTEM_MAPS.md; docs/officers/ACCESS_CONTINUITY.md; docs/officers/EMERGENCY_AND_RECOVERY.md; docs/officers/GLOSSARY.md

Deployment evidence: Website — https://run-mprc-staging.web.app and direct /events returned 200; signed-out desktop and 390px phone rendering/navigation passed with no broken images or horizontal overflow; empty staging Events settled to the fixed no-events state. Firebase — project run-mprc-staging, one web app, finalized Hosting version 3ffadcf2ac8cc760 from exact merged source a614c68; live channel released 2026-08-26T16:53:11.810Z. Provider surfaces — production Firebase Hosting still returns 404; runmprc.com/Netlify, GitHub Pages, DNS, backend services, provider sandboxes, accounts, sign-in, and production data were not changed.

Verification

  • Node 20.20.2: npm run test:firebase-hosting — 7/7 passed.
  • Exact staging build and Hosting predeploy validation passed before publication.
  • Executable artifact contained the staging identity and no known production Firebase identity.
  • Provider readback: staging root 200, staging /events 200, production Firebase Hosting 404.
  • git diff --check passed; generated public/sitemap.xml was restored and is unchanged.

Closes #665

@netlify

netlify Bot commented Aug 26, 2026

Copy link
Copy Markdown

Deploy Preview for luminous-fox-7c393f ready!

Name Link
🔨 Latest commit 3bde951
🔍 Latest deploy log https://app.netlify.com/projects/luminous-fox-7c393f/deploys/6a8f1d0d9399150008571f8c
😎 Deploy Preview https://deploy-preview-666--luminous-fox-7c393f.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

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

@daliu daliu left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self-review completed on exact head 3bde951. No blocking findings. The diff is documentation-only, leaves public/sitemap.xml unchanged, records exact staging provider/UI evidence, and explicitly preserves the no-sign-in/no-backend/no-production boundary. Node 20 Hosting contract tests passed 7/7 and all PR checks are green.

@daliu
daliu merged commit b115433 into main Aug 26, 2026
4 checks passed
@daliu
daliu deleted the codex/issue-665-firebase-staging branch August 26, 2026 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

WEB-001A2 — Provision isolated Firebase staging and publish an exact-source Hosting site

1 participant