Keep distribution staging owner-only - #10
Merged
Merged
Conversation
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.
What changed
Security result
Extended CodeQL opened seven high-severity overly-permissive-file findings on main. The PR merge ref now has zero open code-scanning alerts, with no dismissals.
Reproducible evidence
Run 31384813643 recaptured the full 28-file evidence bundle and verified the drift allowlist before uploading artifact 9061461067 without repository write permission. Independent review checked all 39 source hashes, every artifact byte count and SHA-256, image/SVG structure, modes, paths, and secret/host markers.
Only three candidate files differ: the real quality-gate transcript now reports 317 passing tests, its actual PNG render is updated, and the manifest advances those identities plus the four changed source/test hashes. All other 25 evidence files are byte-identical to the branch.
This PR does not choose a license or publish a release; that separate rights-owner decision remains tracked in issue #9.