Repository navigation
docs: verified staging profiles, low-cost controls and cleanup - #704
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
Officer handoff review complete: clear staging-only outcome and dated native source/run/results; procedure preserves normal approval, stop conditions, limited same-scope recovery and Dave/specialist escalation, with no officer terminal, secret or data-edit step. Historical source-only anchors preserved. All six jobs passed in 38179103409. Documentation-only diff; Functions remain from2843388 with unchanged verified bundle. Website release manifest inactive/public marker41a9ae4. #701 is ready to close after this documentation merge; #113/#133/#136 stay open. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related #701. Documentation-only handoff of the verified two-Function staging outcome.
Protected run 38176811598 deployed createMemberOnSignUp and ensureMemberProfile from 2843388 after exact-main six-job CI 38176576872. Normal daliu approval was delegated by Dave; admin bypass disabled. Both native downloaded source archives match SHA256 5dd349869630b3ff8af9ef3c26a116275d0cd0132f039a82675261187247685c (76,628 bytes). Node22/min0/max2/256MB/30s, explicit identities, Auth/Firestore App Check ENFORCED and callable-only public transport verified.
Hosted: fresh signup (~6.5s) created pending profile and preserved claims; normal Account UI repaired failed signup; 12 real-attestation callable tests passed (7 denials, 5 successful calls including burst), self200/cross403, existing profile fields/claims unchanged. Three simultaneous missing-profile recoveries all200/one pending profile (~1.1–1.4s). Background replay preserved canonical fields and update time. Two exact owned accounts and two exact owned profiles were deleted after sign-out; aggregate Auth0/empty collection metadata restored. No emails, payments or production records tested.
Records initial partial release and narrow #703 corrections honestly; no permission/dependency/profile-logic widening. Trial alerts are not a cap or invoice proof. Production/website/payment rollout and #113/#133/#136 remain open. No code, rule, provider or deployment action is included in this documentation PR.
Officer impact: distinguish verified staging profiles from still-unavailable production/member/payment operations, understand limits and specialist recovery.
Officer documentation: OFFICER_START_HERE.md; docs/officers/{LOW_COST_COMMUNITY,README,PUBLISH_AND_CHECK,SYSTEM_MAPS}.md; relevant root design/security/implementation/operations/issue records. Preserves the old attestation link anchor.
Deployment evidence: exact protected run, source archives, provider readback, hosted allow/deny/concurrency/preservation/UI and cleanup above. This PR publishes no website or Firebase revision.
Backup-officer procedure review: no terminal, key, token or member-record step is assigned to an officer; dated run/source checks and observation are usable. Provider setup, release/rollback and identity revocation still need Dave/platform specialist; no backup owner has been appointed.