You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adds an argument-closed, staging-only Firebase Hosting release path for the App Check rollout. A staging deploy now requires the exact club account/project/quota/scope, an in-memory short-lived token, Firebase CLI 15.24.0, no credential-file override, and a bounded non-placeholder reCAPTCHA Enterprise public site key. The executable artifact verifier must find that selected key in built JavaScript.
Closes the source phase of #676. Provider configuration, Hosting publication, enforcement, and browser proof remain a separate post-merge phase under the same issue.
Officer impact: No website or provider behavior changes from this pull request. Backup officers gain a plain-language review procedure that distinguishes a source guard from live App Check.
Officer documentation: OFFICER_START_HERE.md, docs/officers/README.md, docs/officers/PUBLISH_AND_CHECK.md, and docs/officers/SYSTEM_MAPS.md.
Deployment evidence: Source and tests only. No Firebase API, reCAPTCHA key, App Check registration/enforcement setting, Hosting version, Function, billing link, IAM binding, user, record, production Firebase surface, Netlify deploy, DNS setting, or runmprc.com behavior changed.
Source boundary
Adds scripts/firebase-hosting-staging-contract.js and exact package lifecycle commands.
Extends the existing Hosting deploy/artifact contract only for staging App Check key presence.
Extends the existing focused Hosting contract suite with positive and negative source, environment, CLI, artifact, and redaction cases.
Updates authoritative engineering and officer-facing status/rollback documentation.
Self-review complete on exact head 0195402c86c685ae0ce44ce180c0b70a70a9ef77: no findings. I checked staging/project/account/scope binding, package/lock/CLI pinning, appended-argument rejection, credential-file rejection, fixed diagnostics, site-key shape and artifact presence, local/preview compatibility, production exclusion, officer continuity, and unchanged billing/Functions/provider boundaries. CI run 33017961284 passed all five required jobs; Netlify preview/header/redirect checks passed and Pages changed was neutral.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Adds an argument-closed, staging-only Firebase Hosting release path for the App Check rollout. A staging deploy now requires the exact club account/project/quota/scope, an in-memory short-lived token, Firebase CLI 15.24.0, no credential-file override, and a bounded non-placeholder reCAPTCHA Enterprise public site key. The executable artifact verifier must find that selected key in built JavaScript.
Closes the source phase of #676. Provider configuration, Hosting publication, enforcement, and browser proof remain a separate post-merge phase under the same issue.
Officer impact: No website or provider behavior changes from this pull request. Backup officers gain a plain-language review procedure that distinguishes a source guard from live App Check.
Officer documentation:
OFFICER_START_HERE.md,docs/officers/README.md,docs/officers/PUBLISH_AND_CHECK.md, anddocs/officers/SYSTEM_MAPS.md.Deployment evidence: Source and tests only. No Firebase API, reCAPTCHA key, App Check registration/enforcement setting, Hosting version, Function, billing link, IAM binding, user, record, production Firebase surface, Netlify deploy, DNS setting, or
runmprc.combehavior changed.Source boundary
scripts/firebase-hosting-staging-contract.jsand exact package lifecycle commands.Verification
git diff --check, fixed-output canaries, and sensitive-shape review passed.Security review