Repository navigation
chore(ci): stage trust for exact policy check repair - #198
Merged
Merged
Conversation
intel352
marked this pull request as ready for review
October 6, 2026 22:36
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.
Repair the verifier/check-name contract through the reviewed three-PR trust migration. Live protection requires strict
policyfrom GitHub Actions App 15368.This is 01-stage-trust. The exact five-path scope is bound to approved manifest SHA-256
5d127cdabf8881e1287fabfe17e71297616eb6be3884902caa764a93d3ebe47a. The root CI inventory baseline changes only its expected digest/comment/diagnostic; count 46, hashing, symlink rejection and negative tests remain intact. Owner approval expressly covers this exact recovery-baseline migration.Stage 1 retains old active trust and adds only the future CI context. Stage 2 repairs verifier/fixtures/provisioning docs and the descriptive CI step label. Stage 3 removes old CI authority and promotes the staged context. No command, action, trigger, permission, runner or release changes are included.
Static independent review reproduces scope and inventory hashes. Actual head CI and fresh independent review remain required before merge. No failed check is waived. Each separately bounded approval-count window must be restored immediately and all other settings preserved.