Repository navigation
CI-001C3: Scoped staging profile authority and protected no-op check - #700
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Outcome
Prepare a separate keyless staging profile-release identity and read-only protected authority check. Restore administrator bypass per Dave's direct instruction; preserve daliu/main and the existing #667 read-only authority.
Refs #699. This is a bounded child of #133, not production rollout or a complete backend.
Scope
Validation
Officer impact: Dave can approve a focused staging authority check without another owner or handling a key; it is not membership/payment operation.
Officer documentation: OPERATIONS_RUNBOOK.md, SECURITY.md, GITHUB_ISSUES.md, OFFICER_START_HERE.md, docs/officers/README.md, ACCESS_CONTINUITY.md, PUBLISH_AND_CHECK.md; separate flow/text alternative and stop/proof/undo/escalation. Procedure remains unavailable until #699 records protected proof.
Deployment evidence: GitHub environment and staging IAM configuration only; no Firebase backend or website published. Provider activation/no-op proof and remaining parent release gates are distinct. Dave's standing sole-maintainer source-review override and latest focused release approval apply.
CI integration correction
Initial run 38172680173 correctly rejected the new YAML parser/test command because the artifact-safety suite keeps an exact independent command allowlist. Updated only that expected allowlist and added negative omission cases for the new verifier parse and test. Existing skip/swallow/privilege guards remain. Final full workflow-safety command passes 146/146 locally, zero skips/failures. Federation remains disabled pending fresh exact-head PR/main checks. This correction adds one test file to the reviewed diff, not a deployment permission or runtime change.