[codex] Report all public hygiene leak labels#153
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
1 participant
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.
Summary
Why
Community feedback called out local folder exposure in public AGENTS-style material. The scanner already blocked the file, but the generic Windows-path label could hide the more actionable pasted-context labels. This makes the failure report useful enough to fix the real source of trust damage.
Validation
bun test scripts/public-artifact-hygiene.test.tsfailed because onlywindows-user-pathwas reportedbun test scripts/public-artifact-hygiene.test.ts-> 31 pass, 0 failbun run product:public-artifact-hygiene-> PASS, 641 files scannedbun test scripts/public-repo-readiness.test.ts scripts/product-github-remote-surface-audit.test.ts-> 39 pass, 0 failbun run verify:privacy-> PASSbun run typecheck --pretty false-> PASSgit diff --check-> PASSClaim Boundary
This improves configured public artifact hygiene diagnostics only. It does not claim full-history secret cleanliness, GitHub secret-scanning alert status, release readiness, production readiness, or external validation.