From 966ba101caf9ed3c186891a1e09219a6041f2f54 Mon Sep 17 00:00:00 2001 From: Dave Liu <7david12liu@gmail.com> Date: Wed, 26 Aug 2026 14:06:51 -0700 Subject: [PATCH] docs: record staging Auth provider evidence --- GITHUB_ISSUES.md | 2 +- IMPLEMENTATION_PLAN.md | 2 +- OFFICER_START_HERE.md | 2 +- OPERATIONS_RUNBOOK.md | 8 +++-- README.md | 8 ++--- SECURITY.md | 4 +-- SYSTEM_DESIGN.md | 18 ++++++----- docs/officers/PUBLISH_AND_CHECK.md | 48 ++++++++++++++++-------------- docs/officers/README.md | 2 +- docs/officers/SYSTEM_MAPS.md | 9 +++--- 10 files changed, 55 insertions(+), 48 deletions(-) diff --git a/GITHUB_ISSUES.md b/GITHUB_ISSUES.md index af8af49..df937c6 100644 --- a/GITHUB_ISSUES.md +++ b/GITHUB_ISSUES.md @@ -146,7 +146,7 @@ Do not redesign routing or hosting in this issue; WEB-001 owns that. WEB-001A1 [ **Current CI-001C boundary:** CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) supplies the staging-only protected read-only OIDC proof: exact immutable repository/owner IDs, `main`, the `staging` environment, one verifier workflow, two named individual reviewers, and a keyless principal with only project-identity read permission. Parent #133 still owns Firebase deployment roles and production protection; #136 still owns an actual backend release. -**Current CI-001D boundary:** CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) supplies the first staging data boundary: empty Native/Standard `(default)` Firestore in `us-west2`, delete protection enabled, PITR disabled, and exact Rules/indexes from `ee16bd16220ab58bd3a2add80dd2f39a1d514dd7`. The 418-case Rules suite passed, provider definitions matched, fixed anonymous server-only reads were denied, and root collection count remained zero. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) adds an email/password-only Auth source contract plus an exact staging/account/scope deployment guard; its first phase does not initialize Auth or create a user. Functions, App Check, provider sandboxes, reusable deploy authority, application records, and production behavior remain absent. Parent #133 still owns keyless Firebase deployment roles and production protection; #136 still owns the compatible synthetic backend release. +**Current CI-001D boundary:** CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) supplies the first staging data boundary: empty Native/Standard `(default)` Firestore in `us-west2`, delete protection enabled, PITR disabled, and exact Rules/indexes from `ee16bd16220ab58bd3a2add80dd2f39a1d514dd7`. The 418-case Rules suite passed, provider definitions matched, fixed anonymous server-only reads were denied, and root collection count remained zero. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) deploys the email/password-only Auth contract from exact merged source `42542303d043f87a8f1a04be2f0b4f2a88e0318c`. Provider readback and disposable API/browser checks prove password-required sign-in, improved email privacy, only staging domains, no other provider, billing disabled, and final cleanup to zero users/records. Functions, App Check, provider sandboxes, reusable deploy authority, application records, and production behavior remain absent. Parent #133 still owns keyless Firebase deployment roles and production protection; #136 still owns the compatible synthetic backend release. ### Problem diff --git a/IMPLEMENTATION_PLAN.md b/IMPLEMENTATION_PLAN.md index f0b6574..657662d 100644 --- a/IMPLEMENTATION_PLAN.md +++ b/IMPLEMENTATION_PLAN.md @@ -44,7 +44,7 @@ MPRC can open a race or merchandise item for sale only when the platform can: **CI-001D1 empty staging Firestore boundary:** [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) provisions `(default)` as an empty Native/Standard database in `us-west2`, enables delete protection, keeps PITR disabled, and deploys only exact Rules/indexes from `ee16bd16220ab58bd3a2add80dd2f39a1d514dd7` with Firebase CLI 15.24.0. The Node 20/Java 21 Rules suite passes 418/418; provider readback matches the active Rules digest, four composite indexes, and 28 field overrides; fixed anonymous server-only reads are denied; root collection count remains zero. This completes only the first staging data boundary. Auth test configuration, Functions, App Check, outside-provider sandboxes, keyless Firebase deployment roles, synthetic signed-in flows, website republication, production protection, and production behavior remain later children of #105/#133/#136. -**CI-001D2 staging Auth source contract:** [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) adds only `emailPassword: true` under the Firebase Auth provider source, preserves the `demo-mprc-local` default alias, and pins a guarded staging-only `--only auth` command to Firebase CLI 15.24.0. The guard requires the exact staging project, quota project, club-account declaration, Auth-only scope, and short-lived token path while rejecting an ADC override. This source phase does not initialize Auth, enable a provider, create a user, send email, configure Google sign-in, change billing, deploy Functions, or prove signed-in behavior. Provider deployment and disposable create/sign-in/delete evidence follow only after this source reaches exact `main`. +**CI-001D2 staging Auth boundary:** [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) adds `emailPassword: true` under the Firebase Auth provider source, preserves the `demo-mprc-local` default alias, and pins a guarded staging-only `--only auth` command to Firebase CLI 15.24.0. The guard requires the exact staging project, quota project, club-account declaration, Auth-only scope, and short-lived token path while rejecting an ADC override. After exact source `42542303d043f87a8f1a04be2f0b4f2a88e0318c` reached `main`, the provider phase enabled password-required email/password only. Readback proved improved email privacy, only the two staging authorized domains, no other sign-in provider, billing disabled, and the instrumentless `IDENTITY_PLATFORM` subtype. Disposable API and browser sign-in/sign-out checks passed, requested no email/SMS, and returned Auth and Firestore to zero users/records. Functions, App Check, role/private-data behavior, reusable deployment authority, and production remain later work. ## 3. Dependency map diff --git a/OFFICER_START_HERE.md b/OFFICER_START_HERE.md index 2a0f9e4..514aa3c 100644 --- a/OFFICER_START_HERE.md +++ b/OFFICER_START_HERE.md @@ -50,7 +50,7 @@ As of **2026-08-13**, a merge runs checks but does not start the GitHub release. As of **2026-08-14**, [#659](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/659) completed one accessibility-only Netlify release. Deploy `6a7ece87c5ca4d0007c1a3fc` is live from frozen source `7496fe0881fb52908c4ff2f40f488df09c94c908`; its exact 62-file marker and signed-out desktop/phone route-focus and menu checks passed. Repause merge `3138a00c1c48e1d5d1dcda0b44722b09a2194ff7` made the manifest inactive. Its attempt `6a7ed0ddb00a46000818878d` published nothing and retained the verified deploy. #623 deploy `6a7e072f8f346b0008510d29` is the recorded rollback, not current production. #659 changed no Firebase, provider configuration, account, sign-in state, production data, payment, or connected directory behavior. Officers do not run commands, sign in, enter data, or approve this as a reusable release. Follow the completed record in [Review, merge, release, and check a change](./docs/officers/PUBLISH_AND_CHECK.md). -As of **2026-08-26**, WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) is merged, and WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) created the club-owned `run-mprc-staging` project and published exact source `a614c68d9a1a2be631a3be874a686d61e5d170a0` to [run-mprc-staging.web.app](https://run-mprc-staging.web.app). CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) adds a separate protected read-only identity check: Dave Liu or Jeff Chang reviews exact `main`, and a keyless five-minute identity may read only the staging project identity. It cannot deploy Firebase. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds an empty, delete-protected staging Firestore database and the exact reviewed Rules/index definitions. Anonymous reads of three fixed server-only paths were denied, and the database still had zero root collections after verification. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) first adds only the reviewed email/password Auth source and a fixed staging-only guard; that source does not initialize Auth or create a user. This remains an **ENGINEERING STAGING SITE ONLY**. It has no deployed Auth proof, Functions, App Check, provider sandbox, protected automatic release, release marker, tested predecessor rollback, security-header policy, custom domain, or officer publish control. Officers do not sign in, enter data, run commands, or treat the empty database or Auth source as a usable backend. Netlify still answers `runmprc.com`; production Firebase Hosting remains empty, and no DNS, GitHub Pages, Netlify, production Firebase, production data, or live website behavior changed. +As of **2026-08-26**, WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) is merged, and WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) created the club-owned `run-mprc-staging` project and published exact source `a614c68d9a1a2be631a3be874a686d61e5d170a0` to [run-mprc-staging.web.app](https://run-mprc-staging.web.app). CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) adds a separate protected read-only identity check: Dave Liu or Jeff Chang reviews exact `main`, and a keyless five-minute identity may read only the staging project identity. It cannot deploy Firebase. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds an empty, delete-protected staging Firestore database and the exact reviewed Rules/index definitions. Anonymous reads of three fixed server-only paths were denied, and the database still had zero root collections after verification. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) deploys password-required email/password Auth from exact merged source and proves it with disposable API and browser sign-in/sign-out checks. Readback shows improved email privacy, only the two staging domains, no other provider, billing disabled, and zero users/records after cleanup. This remains an **ENGINEERING STAGING SITE ONLY**. It has no trusted Functions, App Check, outside-provider sandbox, protected automatic release, release marker, tested predecessor rollback, complete security-header policy, custom domain, or officer publish control. Officers do not sign in, enter data, run commands, or treat narrow Auth proof as a usable member backend. Netlify still answers `runmprc.com`; production Firebase Hosting remains empty, and no DNS, GitHub Pages, Netlify, production Firebase, production data, or live website behavior changed. The optional profile-photo and officer People-finder functions are still **NOT AVAILABLE YET**. #621 makes the frontend default an inert preview: My Account shows the future photo and separate finder-choice controls disabled, while the People finder stays behind the administrator guard and shows its name field and Search button disabled. The preview reads no saved photo or setting, accepts or uploads no photo, searches no name, and saves nothing; it shows no people or sample results. #623 published exactly that disabled interface as deploy `6a7e072f8f346b0008510d29`. Officers inspect the protected layouts only in synthetic local artifacts. The completed signed-out production review proved only the exact revision, normal sign-in and administrator guards, and absence of a member-directory network request. Do not sign in to production, choose a real photo, enter a real name, or treat the preview as a directory. #623 changed no Firebase, provider configuration, account, sign-in, or production data. #507 must later prove the privacy, authorization, staging, backend-first deployment, and readback gates before a separate reviewed source change may connect it. Follow the preview and source-review procedure in [Events, shop, members, and money](./docs/officers/EVENTS_SHOP_MEMBERS.md). diff --git a/OPERATIONS_RUNBOOK.md b/OPERATIONS_RUNBOOK.md index 29704a6..315e65d 100644 --- a/OPERATIONS_RUNBOOK.md +++ b/OPERATIONS_RUNBOOK.md @@ -63,7 +63,7 @@ Maintain an internal inventory with project/account IDs and console links: | --- | --- | --- | --- | --- | --- | | Local source runtime | `demo-mprc-local` emulators | Providers remain separately gated | `localhost:3000` | None | Available for synthetic Firebase work after all three loopback emulators report ready | | CI | Separate named demo/emulator projects | Fixtures/test only | None | CI | Frontend, Functions, Rules, SPA, and commerce-journal checks run; broader gates remain partial | -| Staging | `run-mprc-staging` | Empty Firestore Rules/index boundary plus an email/password-only Auth source contract that is not deployed; no Functions, App Check, or provider sandbox | `run-mprc-staging.web.app`; `dev.runmprc.com` not configured | `staging`: two reviewers, exact `main`, read-only OIDC verifier | Static signed-out Hosting, protected project-identity proof, empty delete-protected Firestore, and reviewed Auth source are available; usable backend/provider staging remains a launch blocker | +| Staging | `run-mprc-staging` | Empty Firestore Rules/index boundary plus deployed password-required email/password Auth; no Functions, App Check, or provider sandbox | `run-mprc-staging.web.app`; `dev.runmprc.com` not configured | `staging`: two reviewers, exact `main`, read-only OIDC verifier | Static Hosting, protected project-identity proof, empty delete-protected Firestore, and disposable Auth proof are available; usable backend/provider staging remains a launch blocker | | Production | `mid-peninsula-running-club` (verify) | Live + unique endpoint | `runmprc.com` | `production` | Informational site only until gates close | WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) created and provider-read back `run-mprc-staging`, one web app, and Hosting version `3ffadcf2ac8cc760` from source `a614c68d9a1a2be631a3be874a686d61e5d170a0` on 2026-08-26. Always name that project explicitly; `.firebaserc` still defaults to the demo namespace. The static host is not complete environment isolation. @@ -72,7 +72,9 @@ CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) adds CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) provisioned only the staging `(default)` Firestore database and deployed exact Rules/indexes from source `ee16bd16220ab58bd3a2add80dd2f39a1d514dd7`. Readback on 2026-08-26 showed Native mode, Standard edition, `us-west2`, delete protection enabled, PITR disabled, Rules SHA-256 `fe3f53302db76df5febf7e9d242d82a6b6bec0c0b574ecc8253f1034f1a77dba`, four matching composite indexes, 28 matching field overrides, and zero root collections. Anonymous reads of fixed nonexistent `mail`, `stripeEvents`, and `auditEvents` documents returned `403`. The Rules emulator suite passed 418/418 before provider mutation. No application record, Auth provider/test user, Function, App Check setting, Storage data, outside provider, Hosting version, production Firebase surface, or website changed. -CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) first adds the source contract for standard Firebase Authentication: only `emailPassword: true`, with no anonymous, Google, or phone provider in source. `npm run deploy:staging-auth` is fixed to Firebase CLI 15.24.0, `--only auth`, and `run-mprc-staging`; its lifecycle guard also requires that exact cloud/quota project, the declared `runmprc@gmail.com` account, a short-lived `FIREBASE_TOKEN`, no ADC file override, and the unchanged demo default alias. Do not run that command from a branch. Merge and verify the exact source first. The source phase does not initialize Auth, configure a provider, create a user, send email, change billing, or authorize sign-in. +CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) first adds the source contract for Firebase Authentication: only `emailPassword: true`, with no anonymous, Google, or phone provider in source. `npm run deploy:staging-auth` is fixed to Firebase CLI 15.24.0, `--only auth`, and `run-mprc-staging`; its lifecycle guard also requires that exact cloud/quota project, the declared `runmprc@gmail.com` account, a short-lived `FIREBASE_TOKEN`, no ADC file override, and the unchanged demo default alias. Do not run that command from a branch. Merge and verify the exact source first. + +The bounded provider phase ran on 2026-08-26 from exact merged source `42542303d043f87a8f1a04be2f0b4f2a88e0318c` after all five required jobs in CI run `33011780449` passed. Live readback showed the instrumentless `IDENTITY_PLATFORM` subtype with billing disabled; password-required email/password and improved email privacy were enabled; authorized domains were exactly `run-mprc-staging.firebaseapp.com` and `run-mprc-staging.web.app`; and anonymous, phone, native federated, OIDC, and SAML providers were absent. A disposable reserved-domain user passed API create/sign-in, generic invalid-credential, anonymous-denial, and browser sign-in/sign-out checks. No out-of-band email or SMS was requested. Cleanup returned Auth to zero users and Firestore to zero root collections. Hosting remained version `3ffadcf2ac8cc760`; Functions and App Check remained unavailable; production was untouched. This evidence is not a reusable officer deployment control. The repository's only `.firebaserc` default is now `demo-mprc-local`, a deliberately non-deployable local namespace. It is an accidental-deploy brake, not staging. Every future deployment must still pass one exact privately approved project explicitly. Do not infer backend/provider isolation or release authority from the static host; #113/#133 must protect, map, and verify those remaining boundaries. @@ -101,7 +103,7 @@ REACT_APP_STRAVA_CLIENT_ID The Firebase web configuration is public application configuration. It must still be environment-specific and paired with Auth restrictions, Firestore rules, and App Check. WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) makes controlled optimized builds choose `staging` or `production`; staging project IDs must include a distinct `staging` segment and the complete artifact check rejects known production identities. Production accepts only the exact reviewed public values. These values are not server credentials, but do not paste provider-console screenshots, private links, tokens, or any server credential into source or an issue. -`firebase.json` has a Hosting block for `build/` and missing-path SPA rewrites. Its predeploy chain rejects a Firebase CLI project that differs from the selected browser project, then rebuilds and scans executable JavaScript before upload. It also has the #671 email/password-only Auth source block; that block is configuration intent, not provider evidence. **Static engineering staging, a protected read-only authority check, an empty Rules-protected Firestore boundary, and the reviewed Auth source contract are available; a usable backend and production publication are NOT AVAILABLE YET.** #665 used the Hosting chain for the first `run-mprc-staging` release. #667's WIF identity can read only the project identity; it cannot deploy. #669 was a separate bounded database/Rules/index operation and did not grant reusable authority. #671 provider deployment must wait for exact-main source and use its guarded Auth-only command. No protected Firebase deploy role, deployed Auth proof, Function, App Check enforcement, provider sandbox, production authority, custom domain, release marker, tested rollback, production release, or DNS/TLS change exists. +`firebase.json` has a Hosting block for `build/` and missing-path SPA rewrites. Its predeploy chain rejects a Firebase CLI project that differs from the selected browser project, then rebuilds and scans executable JavaScript before upload. It also has the #671 email/password-only Auth source block; source remains configuration intent, while the separate provider evidence proves the live narrow Auth boundary. **Static engineering staging, a protected read-only authority check, an empty Rules-protected Firestore boundary, and disposable email/password Auth proof are available; a usable backend and production publication are NOT AVAILABLE YET.** #665 used the Hosting chain for the first `run-mprc-staging` release. #667's WIF identity can read only the project identity; it cannot deploy. #669 and #671 were separate bounded provider operations and did not grant reusable authority. No protected Firebase deploy role, Function, App Check enforcement, provider sandbox, production authority, custom domain, release marker, tested rollback, production release, or DNS/TLS change exists. ### App Check release state — NOT AVAILABLE YET diff --git a/README.md b/README.md index daadfe0..3cf316a 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ Historical developer/content/LLM guides remain under [`docs/`](./docs/README.md) **Deployment reality checked 2026-08-14:** merges run CI but do not start the manual release workflow. The protected gate accepts one exact current merged commit, rechecks its newest CI run after approval, uses one fixed Firebase target set, fails when protected authority/configuration is missing, verifies Firebase before publishing GitHub Pages, and gives no server credential to website preparation or publication. Ordinary Git-triggered Netlify production builds are paused. WEB-002D [#659](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/659) completed one bounded accessibility release: exact merge `46e23647d8e0bf9fa3a574ea5c5f993be10a419d` published deploy `6a7ece87c5ca4d0007c1a3fc` from source `7496fe0881fb52908c4ff2f40f488df09c94c908`, tree `ccac4c189c195db8ab594e0eefe256ea9fa04996`, 62 files, and artifact digest `e4c26e6f0fbcd086663d86238675f0be228fb649a00628c1c97d1166612f49c7`. Signed-out desktop and phone route-focus/menu checks passed. Repause merge `3138a00c1c48e1d5d1dcda0b44722b09a2194ff7` passed exact-main CI run `31783808994`; attempt `6a7ed0ddb00a46000818878d` published nothing, deploy `6a7ece87c5ca4d0007c1a3fc` remained live, and the manifest is inactive. #623 deploy `6a7e072f8f346b0008510d29` remains rollback history and its inert directory interface is unchanged beneath the accessibility delta. No Firebase, Rules, Functions, indexes, provider configuration, account, sign-in state, role, member data, payment, or connected directory backend changed. The prior bounded #473 deploy `6a6dc9ea588b0c0008036312` remains older history. The source stops adding a Pages `CNAME`, but GitHub Pages currently still claims `runmprc.com` and its default URL redirects there; only a controlled #136/WEB-001 publication and provider readback can clear that conflict. Reusable protected publication to the live Netlify-served `runmprc.com` is not configured yet. Treat GitHub Pages, Netlify, `runmprc.com`, Firebase, and outside providers as separate states. -**Owned staging checked 2026-08-26:** WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) created the isolated `run-mprc-staging` Firebase project under the club account and published exact source `a614c68d9a1a2be631a3be874a686d61e5d170a0` as Hosting version `3ffadcf2ac8cc760` at [run-mprc-staging.web.app](https://run-mprc-staging.web.app). Signed-out desktop, phone, and direct `/events` checks passed. CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) adds a protected staging-only OIDC verifier with two named reviewers and a keyless principal that can read only the exact project identity. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds the empty delete-protected `(default)` Firestore database in `us-west2` and deploys exact Rules/indexes from source `ee16bd16220ab58bd3a2add80dd2f39a1d514dd7`; provider definitions matched, fixed anonymous server-only reads were denied, and the root collection count remained zero. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) adds a source-controlled email/password-only Auth contract and a staging/account/scope guard, but this source phase does not initialize Auth or create a user. This is still incomplete engineering staging: Auth provider deployment and synthetic proof, Functions, App Check enforcement, outside-provider sandboxes, reusable Firebase deployment authority, application security headers, a release marker, and a tested predecessor rollback are not configured. Do not sign in or use real data there. Production Firebase Hosting remains empty and `runmprc.com` remains on its existing Netlify deployment. +**Owned staging checked 2026-08-26:** WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) created the isolated `run-mprc-staging` Firebase project under the club account and published exact source `a614c68d9a1a2be631a3be874a686d61e5d170a0` as Hosting version `3ffadcf2ac8cc760` at [run-mprc-staging.web.app](https://run-mprc-staging.web.app). Signed-out desktop, phone, and direct `/events` checks passed. CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) adds a protected staging-only OIDC verifier with two named reviewers and a keyless principal that can read only the exact project identity. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds the empty delete-protected `(default)` Firestore database in `us-west2` and deploys exact Rules/indexes from source `ee16bd16220ab58bd3a2add80dd2f39a1d514dd7`; provider definitions matched, fixed anonymous server-only reads were denied, and the root collection count remained zero. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) deployed exact merged source `42542303d043f87a8f1a04be2f0b4f2a88e0318c` to Auth only. Live readback shows instrumentless Firebase Authentication with Identity Platform, billing disabled, password-required email/password, improved email privacy, only the two staging authorized domains, and no anonymous, phone, native federated, OIDC, or SAML provider. Disposable API and browser sign-in/sign-out checks passed, both identities were removed, no email or SMS was requested, and the final user and Firestore root-collection counts were zero. This remains incomplete engineering staging: trusted Functions, App Check enforcement, outside-provider sandboxes, reusable Firebase deployment authority, application security headers, a release marker, and a tested predecessor rollback are not configured. Do not use real data or treat staging sign-in as an operational member system. Production Firebase Hosting remains empty and `runmprc.com` remains on its existing Netlify deployment. ## Local setup status @@ -68,7 +68,7 @@ npm start Open only `http://localhost:3000`. Stop if Firebase traffic uses a non-loopback host. Use synthetic records only. This does **not** make checkout, refunds, email, Strava, or other outside-provider calls safe; follow [OPERATIONS_RUNBOOK.md](./OPERATIONS_RUNBOOK.md) before any provider test. -Do not use a Netlify preview, locally served optimized `build/`, or `run-mprc-staging` for sign-in, private pages, admin work, or provider testing. WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) makes optimized builds choose `staging` or `production` explicitly. WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) verifies the owned static stage, CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) verifies only its empty Firestore Rules/index boundary, and CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) initially supplies only the reviewed Auth source contract. Auth provider behavior, Functions, App Check, and outside providers are still not isolated for end-to-end use. +Do not use a Netlify preview, locally served optimized `build/`, or `run-mprc-staging` with real identities, private/member records, admin work, or outside-provider actions. WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) makes optimized builds choose `staging` or `production` explicitly. WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) verifies the owned static stage, CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) verifies its empty Firestore Rules/index boundary, and CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) proves only bounded disposable email/password Auth behavior. Functions, App Check, and outside providers are still not isolated for end-to-end use. ## Verification @@ -91,7 +91,7 @@ npx --no-install react-scripts build node scripts/firebase-hosting-contract.js verify build ``` -Rules and commerce-emulator tests require Java 21. The repository pins Firebase CLI 15.24.0; use only that lockfile copy with Node 20 and explicit `demo-*` projects. The synthetic values above authorize no provider call or deployment. The direct `react-scripts build` command avoids regenerating `public/sitemap.xml`; the following verifier proves that executable JavaScript selected the synthetic staging project and contains no known production Firebase identity. The normal `npm run build` validates its selected hosted environment and runs the sitemap generator. Hosted CI runs the frontend Jest suite under [#124](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/124), the SPA callback suite under [#126](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/126), and the release-gate source tests under [#135](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/135). #667 supplies a separate protected staging project-identity check only. #669 proves the exact Rules/index files on an empty staging database, but grants no reusable deploy authority and proves no signed-in behavior. #671 adds a focused source test and an Auth-only deploy guard; source and CI do not prove that staging Auth is initialized. Parent [#133](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/133) still owns Firebase deployment roles and production protection; [#136](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/136) owns the actual staged profile-recovery release. Required branch checks, complete backend/provider isolation, protected publication, security headers, rollback proof, and hosting consolidation remain open under [#105](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/105) and their atomic children. +Rules and commerce-emulator tests require Java 21. The repository pins Firebase CLI 15.24.0; use only that lockfile copy with Node 20 and explicit `demo-*` projects. The synthetic values above authorize no provider call or deployment. The direct `react-scripts build` command avoids regenerating `public/sitemap.xml`; the following verifier proves that executable JavaScript selected the synthetic staging project and contains no known production Firebase identity. The normal `npm run build` validates its selected hosted environment and runs the sitemap generator. Hosted CI runs the frontend Jest suite under [#124](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/124), the SPA callback suite under [#126](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/126), and the release-gate source tests under [#135](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/135). #667 supplies a separate protected staging project-identity check only. #669 proves the exact Rules/index files on an empty staging database but grants no reusable deploy authority. #671 adds a focused source test and an Auth-only deploy guard; its separate exact-main provider evidence proves the live narrow Auth configuration and disposable sign-in cleanup, while source and CI alone still prove neither fact. Parent [#133](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/133) still owns Firebase deployment roles and production protection; [#136](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/136) owns the actual staged profile-recovery release. Required branch checks, complete backend/provider isolation, protected publication, security headers, rollback proof, and hosting consolidation remain open under [#105](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/105) and their atomic children. These safety changes do not repair a missing member profile or prove deployed Firebase Rules/Functions. The reported profile-save failure remains [#118](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/118). @@ -107,4 +107,4 @@ Business owners—not coding agents—must approve legal text, waiver/insurance ## Deployment warning -Pushing to `main` runs CI and does not start `.github/workflows/deploy.yml`. #667's separate manual verifier proves only short-lived staging project-identity access. #669's one-time bounded operation proves only the empty staging Firestore Rules/index boundary; it is not a release button. The backend release workflow remains **NOT AVAILABLE YET** until #133 grants only the reviewed deployment roles and protects production. Ordinary Git-triggered Netlify production builds are paused. The completed #623 web-only exception is inactive and not reusable; it published no Firebase or provider change. The older #473 exception is retained only as rollback history. A reusable protected live-Netlify publication path is still **NOT AVAILABLE YET**. Production changes still require protected approval, a compatible backend-first rollout, separate live-host proof, a named observer, and the runbook's post-deploy/reconciliation steps. +Pushing to `main` runs CI and does not start `.github/workflows/deploy.yml`. #667's separate manual verifier proves only short-lived staging project-identity access. #669's one-time bounded operation proves only the empty staging Firestore Rules/index boundary, and #671's one-time bounded operation proves only staging Auth; neither is a release button. The backend release workflow remains **NOT AVAILABLE YET** until #133 grants only the reviewed deployment roles and protects production. Ordinary Git-triggered Netlify production builds are paused. The completed #623 web-only exception is inactive and not reusable; it published no Firebase or provider change. The older #473 exception is retained only as rollback history. A reusable protected live-Netlify publication path is still **NOT AVAILABLE YET**. Production changes still require protected approval, a compatible backend-first rollout, separate live-host proof, a named observer, and the runbook's post-deploy/reconciliation steps. diff --git a/SECURITY.md b/SECURITY.md index fbb2196..a563946 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -47,7 +47,7 @@ The findings below describe the repository at the start of the 2026-07-12 assess | RISK-007 | Repository source rejects unverified targets at the two existing role-grant endpoints. AUTH-001B [#196](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/196) adds exact verified-email checks to role-based Firestore Rules, and AUTH-001C [#209](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/209) tracks the matching gate at current Functions role consumers. Firebase deployment, verification-mirror refresh, revocation, authoritative membership, scoped capability/recent-auth controls, and replacement of the legacy static-key endpoint remain unproven. | Older deployed code or a remaining role-only server guard can let an unverified known-email account use member/admin authority. CSV export also retains separate minimization, recent-auth, and audit risks. | Deploy and verify the exact Rules/Functions through #105, complete the remaining AUTH-001 mirror/revocation work, require authoritative membership and scoped privileged access, harden roster export under #116, and retire the static-key endpoint. | | RISK-008 | `requireAppCheck` is controlled by optional `ENFORCE_APP_CHECK`; repository/deployment config does not prove it is true. Missing site key also disables client App Check. | Public callable functions may be scripted directly, enabling abuse and cloud/Stripe cost amplification. | Use Firebase runtime `enforceAppCheck: true` for sensitive callables, reCAPTCHA Enterprise, staged metrics, and no environment fail-open. | | RISK-009 | #99 source preserves and validates the complete same-origin Pages callback route, applies `strict-origin` before subresources, and suppresses initial callback App Check/telemetry startup; #126 adds that standalone suite as a blocking hosted CI step. #443 adds only the source/test Strava same-document handoff after the native and Router callback locations are clean. No production Stripe/Strava callback, provider-backed App Check token behavior, or live custom-domain handoff has been rehearsed, and the live custom domain uses a different host. | Hosting, provider, configuration, or release drift can still break return links or the App Check handoff even when source tests pass. Enforcing a callback callable without its matching released client handoff and staged provider evidence can also break confirmation or Strava exchange. | Keep the hosted callback gate blocking; keep `lookupRegistration`/`lookupOrder` deferred until DATA-001A; keep native enforcement for `stravaExchangeCode` deferred to ABUSE-001A2 after the exact #443 website source and provider-backed Enterprise token behavior are proven in protected staging; verify test-mode callbacks only after provider gates; consolidate hosting under WEB-001. | -| RISK-010 | Development/test use synthetic loopback Auth, Firestore, and Functions. WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) binds controlled Hosting builds to an explicit environment, and WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) supplies owned static staging. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds an empty delete-protected Firestore database with exact Rules/indexes. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) adds email/password-only Auth source and a narrow staging deployment guard, but its source phase does not initialize Auth. App Check, deployed Auth proof, Functions, Storage data, provider sandboxes, protected Firebase deployment authority, and a release marker remain absent; emulated Functions can still call outside providers. | A partially provisioned stage, bypassed build path, or provider-capable emulator can be mistaken for complete staging and affect production/provider systems. | Keep private actions out of previews; preserve the fixed project, exact Rules, and Auth-only source guard; complete #671 provider proof plus #113/#133/#136 Functions, App Check, short-lived deploy authority, and provider isolation; prove test keys, sinks, exact marker readback, and rollback before end-to-end flows. | +| RISK-010 | Development/test use synthetic loopback Auth, Firestore, and Functions. WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) binds controlled Hosting builds to an explicit environment, and WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) supplies owned static staging. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds an empty delete-protected Firestore database with exact Rules/indexes. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) deploys and verifies password-required email/password Auth with improved email privacy, but the project still has no Functions or App Check. Storage data, provider sandboxes, protected Firebase deployment authority, and a release marker remain absent; emulated Functions can still call outside providers. | A partially provisioned stage, bypassed build path, or provider-capable emulator can be mistaken for complete staging and affect production/provider systems. | Keep real identities and private actions out of previews; preserve the fixed project, exact Rules, and Auth-only guard/evidence; complete #113/#133/#136 Functions, App Check, short-lived deploy authority, and provider isolation; prove test keys, sinks, exact marker readback, and rollback before end-to-end flows. | | RISK-011 | Local cancellation only changes Firestore; it does not expire the active Stripe Session. The webhook can later move a cancelled record back to paid. | Customers can pay a supposedly cancelled registration/order; capacity/inventory and support state diverge. | Add explicit cancellation saga with Stripe Session expiry and allowed-state transitions. | | RISK-012 | Repository source now denies every admitted positive late-registration amount before identifier/token allocation, registration writes, Stripe construction, or Product/Price/Payment Link calls, and the Admin screen exposes only the exact-zero compatibility path. Firebase deployment is unproven, and legacy reusable Payment Links may still exist. | Older deployed code or an existing link can still create unreconciled or repeated charges/Sessions for one logical registration. The exact-zero local record is also marked paid without Stripe and is not payment, free, comp, or membership authority. | Keep paid late registration unavailable; inventory, deactivate, and reconcile legacy links privately; then replace them with one-off idempotent Checkout Sessions through the normal registration/payment lifecycle. | | RISK-013 | The assessment baseline permitted Stripe promotions while Firestore stored base price. Repository source now disables promotion entry and automatic tax, requires a complete adjustment breakdown, and quarantines unknown or nonzero discount/tax/shipping amounts; deployment and provider state are unproven. | An older open Session, provider drift, skipped backend release, or later guard regression could still make reporting, refunds, and local payment confirmation disagree. | Privately inventory pre-change Sessions/provider settings, release through the protected gate, verify Firebase and Stripe separately, and keep every adjustment disabled until an approved authoritative model exists. | @@ -330,7 +330,7 @@ CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) estab CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) used only the club account and an explicitly named staging project for the one-time database provision and bounded Rules/index deploy. Firebase CLI 15.24.0 JSON account diagnostics can include token-bearing account objects; never run `firebase login:list --json` in CI, a captured terminal, an issue, or an AI transcript. Use non-token identity checks, revoke any accidentally exposed OAuth grant immediately, and prefer the protected keyless deployment path once #133 grants the exact reviewed staging roles. -CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) source permits only email/password Auth, keeps the unqualified Firebase alias in `demo-mprc-local`, and pins the provider command to `--only auth --project run-mprc-staging`. Its predeploy guard requires the exact quota project, declared club account, and a short-lived Firebase token while rejecting an ADC file override. This source and its CI test grant no authority and make no provider change; provider initialization must use exact merged source and must clean the disposable identity back to zero users. +CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) source permits only email/password Auth, keeps the unqualified Firebase alias in `demo-mprc-local`, and pins the provider command to `--only auth --project run-mprc-staging`. Its predeploy guard requires the exact quota project, declared club account, and a short-lived Firebase token while rejecting an ADC file override. The separate provider phase used exact merged source `42542303d043f87a8f1a04be2f0b4f2a88e0318c` and only `runmprc@gmail.com`. Readback proved password-required email/password, improved email privacy, only the two staging domains, no other provider, and instrumentless billing-disabled state. Disposable API and browser checks passed and cleaned Auth back to zero users without requesting email or SMS. This is not reusable deployment authority and does not prove Functions, App Check, role claims, private records, or production. ## 10. Incident response diff --git a/SYSTEM_DESIGN.md b/SYSTEM_DESIGN.md index 299a6eb..4c30e86 100644 --- a/SYSTEM_DESIGN.md +++ b/SYSTEM_DESIGN.md @@ -261,21 +261,23 @@ flowchart LR Text alternative: exact reviewed Rules and indexes pass the emulator suite before a staging-only deploy; active Rules deny anonymous server-only reads, and the protected staging database remains empty. -**CI-001D2 staging Auth source boundary — not deployed:** [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) adds a reviewable provider and deploy contract before any Auth provider mutation. +**CI-001D2 staging Auth boundary — available after exact-main deploy:** [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) adds a reviewable provider/deploy contract and records the separate live provider proof from exact merged source `42542303d043f87a8f1a04be2f0b4f2a88e0318c`. ```mermaid flowchart LR Source["Exact main firebase.json\nemail/password only"] --> Guard["Staging project, club account,\nshort-lived token, Auth-only scope"] - Guard --> Future["Future exact-main Auth deploy"] + Guard --> Deploy["Exact-main Auth-only deploy"] + Deploy --> Readback["Provider/domain/privacy readback"] + Readback --> Synthetic["Disposable API + browser proof\nthen zero users"] Broader["Anonymous, Google, phone,\nproduction, ADC, or broad scope"] --> Stop["Reject"] - Guard -. "source phase only" .-> Stop + Synthetic -. "No Functions, App Check, or real data" .-> Stop ``` -Text alternative: the source permits only email/password Auth and a guarded future Auth-only deployment to the exact staging project; broader providers, production, ADC, or a broad deploy reject, and this source phase changes no provider. +Text alternative: exact reviewed source permits only a guarded Auth deployment to staging; live readback proves password-required email/password, improved email privacy, only staging domains, no other provider, and zero users after disposable API and browser checks. Functions, App Check, production, and real data remain outside the boundary. ## 4. Target deployment topology -The target keeps React, Firebase, and Stripe, but places stronger boundaries around them. Migrating the frontend from GitHub Pages/Netlify to Firebase Hosting is recommended before live commerce because it supports controlled SPA rewrites, preview channels, and security headers. #663 supplies the fail-closed build selector and inert Hosting rewrite configuration. #665 owns the isolated static staging host. CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) adds only a protected, read-only staging identity proof; it grants no Firebase deployment permission. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds only the empty staging Firestore database and exact Rules/index boundary. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) initially adds only the email/password Auth source and guarded staging-only command; provider configuration remains uninitialized until the exact-main deployment phase. Backend Functions, Auth provider proof, deployment authority, automatic exact-commit release, full readback, rollback, headers, production protection, outside-provider isolation, and DNS/TLS cutover remain separate work under #113/#133/#136/#460. The migration is not live merely because one staging layer exists. +The target keeps React, Firebase, and Stripe, but places stronger boundaries around them. Migrating the frontend from GitHub Pages/Netlify to Firebase Hosting is recommended before live commerce because it supports controlled SPA rewrites, preview channels, and security headers. #663 supplies the fail-closed build selector and inert Hosting rewrite configuration. #665 owns the isolated static staging host. CI-001C1 [#667](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/667) adds only a protected, read-only staging identity proof; it grants no Firebase deployment permission. CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds only the empty staging Firestore database and exact Rules/index boundary. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) deploys and verifies the narrow email/password Auth configuration from exact merged source. The instrumentless project reports the `IDENTITY_PLATFORM` subtype and remains unlinked from billing; its current no-cost ceiling is an operational limit, not authorization to add enterprise providers. Backend Functions, App Check, reusable deployment authority, automatic exact-commit release, full backend readback, rollback, headers, production protection, outside-provider isolation, and DNS/TLS cutover remain separate work under #113/#133/#136/#460. The migration is not live merely because several staging layers exist. ```mermaid flowchart TB @@ -1760,7 +1762,7 @@ Returning a `2xx` response to Stripe means the event has been durably accepted o | --- | --- | --- | --- | --- | | Local source runtime | Firebase Emulator Suite under `demo-mprc-local` | Not safe by Firebase emulation alone | `localhost:3000` | Synthetic data only; browser Firebase traffic is loopback-only | | CI | Ephemeral emulators and mocks | Stripe fixtures/signature tests; optional isolated test account | None | Synthetic data, no production secrets | -| Staging | `run-mprc-staging`; static Hosting, one web app, protected read-only OIDC proof, empty delete-protected Firestore with exact Rules/indexes, and an email/password-only Auth source contract not yet deployed | Not configured; no provider testing authorized | `run-mprc-staging.web.app`; `dev.runmprc.com` not configured | Signed-out public visual review and fixed anonymous denial checks only; no sign-in or real data | +| Staging | `run-mprc-staging`; static Hosting, one web app, protected read-only OIDC proof, empty delete-protected Firestore with exact Rules/indexes, and deployed/verified password-required email Auth | Not configured; no outside-provider testing authorized | `run-mprc-staging.web.app`; `dev.runmprc.com` not configured | Public signed-out review plus issue-scoped disposable synthetic Auth checks; no real identity or data | | Production | Dedicated production Firebase project | Live restricted keys and production webhook secret | `runmprc.com` | Real data under documented retention and access policies | ```mermaid @@ -1781,9 +1783,9 @@ Text alternative: the local browser uses only the three loopback Firebase emulat #99 source selects a fully synthetic Firebase configuration for development/test, connects Auth, Firestore, and Functions to the loopback ports above, stops startup when connection setup fails, and leaves App Check, Analytics, and Sentry off locally. #139 additionally keeps Firebase Analytics off in every source environment and removes the direct Waiver SDK bypass pending an approved #110 policy. The Firebase CLI must still report all three emulators ready before the app is opened. Mocked endpoint tests alone do not prove listening processes, website publication, provider behavior, or deletion of earlier provider data/cookies. -Optimized builds must select `staging` or `production` explicitly. WEB-001A1 #663 rejects missing, local, incomplete, or cross-environment Firebase web configuration, and its artifact check rejects known production identities from a staging executable. Ordinary Netlify deploy previews receive and scan only the reserved synthetic configuration; `run-mprc-staging.web.app` receives and scans the real isolated staging web-app identity; the pinned release builder receives and scans the exact reviewed public production web configuration. The owned staging project now has an empty Rules-protected Firestore boundary and #671 source describes email/password-only Auth, but Auth remains uninitialized until exact-main provider deployment and disposable proof finish. It still lacks Functions, App Check, and outside-provider isolation. Both preview types remain restricted to public, signed-out, read-only visual review until #105/CONFIG supplies complete backend/provider evidence. Do not sign in, open private/admin pages, or test Firebase/provider actions in those previews. +Optimized builds must select `staging` or `production` explicitly. WEB-001A1 #663 rejects missing, local, incomplete, or cross-environment Firebase web configuration, and its artifact check rejects known production identities from a staging executable. Ordinary Netlify deploy previews receive and scan only the reserved synthetic configuration; `run-mprc-staging.web.app` receives and scans the real isolated staging web-app identity; the pinned release builder receives and scans the exact reviewed public production web configuration. The owned staging project now has an empty Rules-protected Firestore boundary and verified password-required email/password Auth with improved email privacy. #671's disposable API and browser checks returned the project to zero users and records. It still lacks Functions, App Check, and outside-provider isolation. Netlify previews remain public, signed-out, read-only visual review only; the Firebase staging host permits only issue-scoped disposable engineering checks until #105/CONFIG supplies complete backend/provider evidence. Never use a real identity, private/admin record, or outside-provider action there. -`SITE_ORIGIN`, Firebase project IDs, App Check keys, Stripe keys, webhook endpoints, Sentry environments, and email providers must be environment-scoped. Live and test webhook secrets are never interchangeable. `run-mprc-staging` now supplies the public web-app, Hosting, empty Firestore Rules/index boundary, and Auth source contract; end-to-end rollout still needs deployed and verified Auth, Functions, App Check, deployment authority, and outside-provider configuration and evidence. +`SITE_ORIGIN`, Firebase project IDs, App Check keys, Stripe keys, webhook endpoints, Sentry environments, and email providers must be environment-scoped. Live and test webhook secrets are never interchangeable. `run-mprc-staging` now supplies the public web app, Hosting, empty Firestore Rules/index boundary, and deployed/verified narrow Auth boundary; end-to-end rollout still needs Functions, App Check, deployment authority, and outside-provider configuration and evidence. CONFIG-001A [#149](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/149) adds the source boundary for current commerce and confirmation-mail Functions: local is exact loopback, tests use HTTPS `.test`, staging is exactly `https://dev.runmprc.com`, and production is exactly `https://runmprc.com`. Test/live expected mode must match the server-key marker on the four key-bound Functions. Webhook and mail receive no Stripe API key, and invalid settings stop before rate-limit, business, mail, event-ledger, or Stripe writes. This source boundary does not create staging, configure Secret Manager or Stripe, deploy Firebase, enable commerce, or prove live behavior. diff --git a/docs/officers/PUBLISH_AND_CHECK.md b/docs/officers/PUBLISH_AND_CHECK.md index 0ef3718..d76b804 100644 --- a/docs/officers/PUBLISH_AND_CHECK.md +++ b/docs/officers/PUBLISH_AND_CHECK.md @@ -10,7 +10,7 @@ **Protected release status:** **NOT AVAILABLE YET.** Issue #135 provides the fail-closed source gate. Issue #133 must still configure protected `staging` and `production` environments, their named reviewers, and a short-lived cloud identity. Public browser build values must be named repository or organization variables because artifact preparation has no protected-environment access; #133/#136 must record and verify them separately. Do not add a long-lived Firebase key as a shortcut. -**Firebase staging status:** **STATIC HOSTING AND EMPTY FIRESTORE BOUNDARY AVAILABLE; OFFICER AND PRODUCTION RELEASE NOT AVAILABLE YET.** WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) requires controlled optimized builds to name staging or production and scans executable JavaScript for environment identity. WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) created the club-owned `run-mprc-staging` project and published exact merged source `a614c68d9a1a2be631a3be874a686d61e5d170a0` to [run-mprc-staging.web.app](https://run-mprc-staging.web.app). CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds an empty delete-protected Firestore database and exact reviewed Rules/indexes; fixed anonymous server-only reads were denied and the root collection count remained zero. The site is still for signed-out public visual review only. It has no Auth test setup, Functions, App Check, provider sandbox, protected short-lived publication, release marker, tested predecessor rollback, complete security headers, custom domain, or DNS/TLS change. Officers do not sign in, enter information, or use the site as a publish control. Production Firebase Hosting remains empty, and Netlify still serves `runmprc.com`. +**Firebase staging status:** **STATIC HOSTING, EMPTY FIRESTORE, AND DISPOSABLE EMAIL/PASSWORD AUTH PROOF AVAILABLE; OFFICER AND PRODUCTION RELEASE NOT AVAILABLE YET.** WEB-001A1 [#663](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/663) requires controlled optimized builds to name staging or production and scans executable JavaScript for environment identity. WEB-001A2 [#665](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/665) created the club-owned `run-mprc-staging` project and published exact merged source `a614c68d9a1a2be631a3be874a686d61e5d170a0` to [run-mprc-staging.web.app](https://run-mprc-staging.web.app). CI-001D1 [#669](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/669) adds an empty delete-protected Firestore database and exact reviewed Rules/indexes; fixed anonymous server-only reads were denied and the root collection count remained zero. CI-001D2 [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) deploys password-required email/password Auth from exact merged source, verifies provider/privacy/domain settings, passes disposable API/browser sign-in checks, and returns the project to zero users and records. The site still has no Functions, App Check, provider sandbox, protected short-lived publication, release marker, tested predecessor rollback, complete security headers, custom domain, or DNS/TLS change. Officers do not sign in, enter information, or use the site as a publish control. Production Firebase Hosting remains empty, and Netlify still serves `runmprc.com`. **Live Netlify publication status:** a reusable protected release is **NOT AVAILABLE YET**. Ordinary Git-triggered production builds are paused by repository configuration. An overbroad #473 artifact was published and then rolled back on 2026-08-01; bounded #473 deploy `6a6dc9ea588b0c0008036312` is older history. #623 completed the inert-directory predecessor and remains the immediate rollback as deploy `6a7e072f8f346b0008510d29`, source `c2d87d1f69f15e128a0bc9b1b9f915b7c8417aec`. #659 completed one separate exact-artifact accessibility release. Deploy `6a7ece87c5ca4d0007c1a3fc`, source `7496fe0881fb52908c4ff2f40f488df09c94c908`, is production now. Its exact marker/artifact and signed-out route-focus/menu checks passed. The manifest is inactive, temporary refs are absent, and the rollback ref remains. Shop is the static catalog; Events and Calendar show a fixed retry-later notice; the directory remains inert. Event records remain unavailable because this did not deploy Firebase. GitHub Pages currently still claims the same custom domain; future source omits that claim, but #136/WEB-001 must publish and verify its removal. @@ -488,43 +488,45 @@ Text alternative: exact reviewed Rules and indexes protect the empty staging dat **Escalation:** platform owner first, security owner second. Use the private incident path for unexpected records, access, or credential output. -## Review the staging Auth source contract — SOURCE ONLY, NOT DEPLOYED +## Review the staging Auth boundary — AVAILABLE AFTER #671 -**Purpose:** let a backup officer confirm that the reviewed source permits only a narrow future staging Auth change, without signing in, creating an account, running a command, or treating source as provider proof. +**Purpose:** let a backup officer confirm that staging has only the reviewed email/password Auth boundary and that disposable proof left no user or application record, without signing in, running a command, or handling a credential. **Approver:** platform owner plus the named security reviewer for #671. -**Prerequisites:** the #671 source pull request is merged, its exact-main CI is green, and the provider phase is still recorded separately as not run. +**Prerequisites:** source PR [#672](https://github.com/Run-MPRC/Run-MPRC.github.io/pull/672) is merged as exact commit `42542303d043f87a8f1a04be2f0b4f2a88e0318c`; exact-main CI run `33011780449` is green; and the redacted [provider evidence](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671#issuecomment-5431051876) is available. ```mermaid flowchart LR - Source["firebase.json\nemail/password only"] --> Guard["Exact staging project, club account,\nshort-lived token, Auth-only scope"] - Guard --> Future["Future reviewed provider step"] - Broad["Anonymous, Google, phone, production,\nADC, or broad deploy"] --> Stop["Stop"] - Future -. "not performed by source" .-> Stop + Source["Exact merged source\nemail/password only"] --> Guard["Exact staging project, club account,\nshort-lived token, Auth-only scope"] + Guard --> Live["Live provider, privacy,\nand domain readback"] + Live --> Proof["Disposable API + browser sign-in"] + Proof --> Empty["Sign out, delete,\nzero users and records"] + Broad["Other provider, billing, production,\nADC, broad deploy, or real data"] --> Stop["Stop"] ``` -Text alternative: reviewed source allows only email/password and a future Auth-only staging operation; broader providers, production, ADC, or broader deployment stop, and no provider change occurs from source or merge. +Text alternative: exact reviewed source and a narrow club-account Auth operation produce the live email/password staging boundary; provider readback and disposable API/browser checks end with zero users and records, while broader providers, billing, production, ADC, broad deployment, and real data stop. -1. Open issue [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671) and its source pull request. -2. Confirm the pull request says `Officer impact`, `Officer documentation`, and `Deployment evidence` separately. -3. Confirm the source names only email/password and does not name anonymous, Google, or phone sign-in as enabled. -4. Confirm the unqualified Firebase project remains the local demo project. -5. Confirm the future command names only Auth and `run-mprc-staging`. -6. Confirm the guard requires the club account declaration, exact staging and quota project, short-lived token path, and no ADC file override. -7. Confirm the five focused source tests and all five hosted CI jobs passed on the exact merge. -8. Confirm provider deployment, a test user, email, billing, Functions, App Check, Hosting, production Firebase, production data, and `runmprc.com` are each recorded as not changed. -9. Record the issue, pull request, exact merge, check date, approver, and provider status. Do not paste a token, console response, account record, or private screenshot. +1. Open issue [#671](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/671), source PR [#672](https://github.com/Run-MPRC/Run-MPRC.github.io/pull/672), and the linked redacted provider evidence. +2. Confirm the source merge is exactly `42542303d043f87a8f1a04be2f0b4f2a88e0318c` and all five jobs in exact-main CI run `33011780449` passed before deployment. +3. Confirm the operation names only `run-mprc-staging`, `runmprc@gmail.com`, Auth scope, and Firebase CLI 15.24.0. +4. Confirm live readback says email/password is enabled and password-required, improved email privacy is enabled, and authorized domains are only `run-mprc-staging.firebaseapp.com` and `run-mprc-staging.web.app`. +5. Confirm anonymous, phone, native federated, OIDC, and SAML providers are absent; multi-tenancy and blocking triggers are absent; and MFA is disabled. +6. Confirm the instrumentless Identity Platform subtype has billing disabled. Treat its no-cost daily limit as a ceiling, not approval to attach billing or add enterprise providers. +7. Confirm disposable API signup/sign-in, anonymous denial, generic invalid-credential behavior, and browser sign-in/sign-out passed without requesting email or SMS. +8. Confirm the final Auth user count and Firestore root collection count are both zero, and Hosting remains version `3ffadcf2ac8cc760`. +9. Confirm Functions, App Check, outside providers, production Firebase, production data, DNS, Netlify, and `runmprc.com` are recorded separately as unchanged or unavailable. +10. Record the issue, pull requests, exact commits, check date, approver, and any mismatch. Do not paste a token, account record, console response, or private screenshot. -**Expected result:** a backup officer can distinguish a narrow reviewed Auth source contract from initialized or usable staging Auth. The staging site remains signed-out engineering review only. +**Expected result:** a backup officer can confirm narrow staging Auth works for disposable engineering checks and can distinguish it from a usable member backend. Functions, App Check, roles, profiles, real identities, provider integrations, and production remain unavailable. -**Stop conditions:** stop if source enables another provider, changes the demo default, permits another project or deployment scope, accepts ADC, lacks the focused test, claims provider success from source/CI, or asks an officer to sign in, create a user, run a command, handle a credential, or inspect an account. +**Stop conditions:** stop if a provider, domain, project, account, commit, billing state, user count, record count, Hosting version, or remaining-gap statement differs; if evidence relies only on source or CI; or if anyone asks an officer to sign in, create a user, run a command, handle a credential, or inspect an account. -**Success proof:** keep the #671 and pull-request links, exact merge, green focused/hosted tests, reviewed source summary, approver, date, and explicit provider-not-deployed statement. +**Success proof:** keep the #671, #672, evidence-comment, and CI links; exact merge; live configuration summary; disposable test/cleanup results; zero counts; unchanged-surface list; approver; and check date. -**Undo:** before provider deployment, use one reviewed revert or safe roll-forward pull request. Do not edit Firebase Console, delete a Firebase project, or create an account as an undo test. +**Undo:** stop all staging sign-in use and open one urgent reviewed security issue for a platform maintainer to apply an Auth-only disable or safe roll-forward from exact source. Do not edit Firebase Console, delete the project or users, attach billing, or improvise a provider change. -**Escalation:** platform owner first, security owner second. Use the private incident path if credential-shaped output or an unexpected account/provider appears. +**Escalation:** platform owner first, security owner second. Use the private incident path if a real or unexpected account, provider, billing link, record, or credential-shaped output appears. ## Before a protected release — NOT AVAILABLE YET diff --git a/docs/officers/README.md b/docs/officers/README.md index de1c783..10a8c57 100644 --- a/docs/officers/README.md +++ b/docs/officers/README.md @@ -69,7 +69,7 @@ WEB-002D [#659](https://github.com/Run-MPRC/Run-MPRC.github.io/issues/659) compl The general protected GitHub release is still **NOT AVAILABLE YET**. #667 configures only a separate staging read-only identity check: Dave Liu or Jeff Chang reviews exact `main`, and a keyless five-minute identity may read only the staging project identity. It cannot deploy Firebase or publish a website. #133 still owns backend deployment roles and production protection. Missing authority stops the release with a red failure before Firebase or website publication. -The empty staging Firestore boundary is available after #669. Project `run-mprc-staging` has a delete-protected empty database with the exact reviewed Rules and indexes. Fixed signed-out requests to server-only paths were denied, and the final root collection count was zero. #671 first adds only a reviewed email/password Auth source contract and a staging-only deployment guard; it does not initialize Auth or create a user. This is not a usable backend: deployed Auth proof, Functions, App Check, provider sandboxes, reusable deployment authority, and signed-in testing remain **NOT AVAILABLE YET**. Officers do not sign in, enter records, run commands, edit the database, or deploy Auth. Use the no-terminal [staging Firestore review](./PUBLISH_AND_CHECK.md#review-the-empty-staging-firestore-boundary--available-after-669) and [Auth source review](./PUBLISH_AND_CHECK.md#review-the-staging-auth-source-contract--source-only-not-deployed). +The empty staging Firestore boundary is available after #669. Project `run-mprc-staging` has a delete-protected empty database with the exact reviewed Rules and indexes. Fixed signed-out requests to server-only paths were denied, and the final root collection count was zero. #671 deploys and verifies password-required email/password Auth from exact merged source. Improved email privacy is on; only the two staging domains are authorized; every other provider is absent; billing is disabled; disposable API/browser checks passed; and cleanup returned Auth and Firestore to zero users/records. This is not a usable member backend: Functions, App Check, provider sandboxes, reusable deployment authority, role/private-data proof, and officer operation remain **NOT AVAILABLE YET**. Officers do not sign in, enter records, run commands, edit the database, or deploy Auth. Use the no-terminal [staging Firestore review](./PUBLISH_AND_CHECK.md#review-the-empty-staging-firestore-boundary--available-after-669) and [staging Auth review](./PUBLISH_AND_CHECK.md#review-the-staging-auth-boundary--available-after-671). GitHub Pages currently still claims `runmprc.com`, so its normal address redirects to the Netlify-served name. The source stops adding that claim, but #136/WEB-001 must publish and verify the provider setting before officers call Pages an independent copy. diff --git a/docs/officers/SYSTEM_MAPS.md b/docs/officers/SYSTEM_MAPS.md index b4c679d..c16a639 100644 --- a/docs/officers/SYSTEM_MAPS.md +++ b/docs/officers/SYSTEM_MAPS.md @@ -88,9 +88,10 @@ flowchart TD Main -. "Ordinary Git production build paused" .-> Netlify Main --> HostingSource["#663 Firebase Hosting source checks"] HostingSource --> StagingHosting["run-mprc-staging.web.app\nengineering staging only"] - Main --> AuthSource["#671 email/password Auth source\nnot deployed"] - AuthSource --> FutureAuth["Future exact-main staging Auth-only deploy"] - FutureAuth -. "not run; no test user" .-> Stop + Main --> AuthSource["#671 exact-main email/password Auth source"] + AuthSource --> StagingAuth["Staging Auth-only deploy\nprovider readback"] + StagingAuth --> AuthProof["Disposable API + browser sign-in\ncleanup to zero users"] + AuthProof -. "No Functions, App Check, real identity, or records" .-> Stop StagingHosting -. "No complete backend/provider test estate, protected deploy authority, marker, or rollback" .-> Stop HostingSource -. "Production branch, headers, authority, and cutover missing" .-> FutureHosting["Production Firebase Hosting — NOT AVAILABLE YET"] Main -. "Completed #659 exact release; manifest inactive" .-> WebGate{"Temporary authority active?"} @@ -101,7 +102,7 @@ flowchart TD Dev["dev — legacy branch"] -. "do not use for new release work" .-> PR ``` -In words: merge, release request, and protected approval are separate; #663 supplies the build checks, #665 publishes only the club-owned signed-out engineering staging site, and #671 first supplies only an email/password Auth source contract. Neither source nor the staging site initializes Auth, creates a user, releases production, or authorizes backend/provider testing. Ordinary merges cannot publish Netlify and the completed #659 exception is inactive; its deploy `6a7ece87c5ca4d0007c1a3fc` remains live while completed #623 deploy `6a7e072f8f346b0008510d29` is the immediate rollback and completed #473 deploy `6a6dc9ea588b0c0008036312` is older history; the future Pages branch must stop claiming the Netlify domain, and every host still needs separate proof. +In words: merge, release request, and protected approval are separate; #663 supplies build checks, #665 publishes the club-owned engineering staging site, and #671 deploys only narrow email/password Auth after exact-main review. Provider and browser proof used disposable identities and returned the project to zero users/records. It does not supply Functions, App Check, real identity or private-data testing, production release, or reusable authority. Ordinary merges cannot publish Netlify and the completed #659 exception is inactive; its deploy `6a7ece87c5ca4d0007c1a3fc` remains live while completed #623 deploy `6a7e072f8f346b0008510d29` is the immediate rollback and completed #473 deploy `6a6dc9ea588b0c0008036312` is older history; the future Pages branch must stop claiming the Netlify domain, and every host still needs separate proof. ## Account and permission ownership