docs: reword a banned leak-term flagged by the enforced ban list#1422
Merged
Conversation
leak-terms.txt line 28 bans 'auto-generated' case-insensitively and the pre-commit hook builds its blocking regex from that file, yet three tracked lines contained the term: ARCHITECTURE.md:37 (nav subtitle) and CHANGELOG.md:1736/2094 (historical entries). This conflicted with the enforced zero-tolerance list and would block the pre-commit hook on any future edit to those files. Reworded to meaning-preserving synonyms outside the ban regex — 'derived' for the nav-subtitle lines and 'compiler-generated' for the CodeQL-exclusion note — so the tracked tree is now literally zero-match against leak-terms.txt. Source: fresh multi-agent ultra-audit (leak-audit dimension), P3, confirmed by adversarial verification against current source. docs: — no release.
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
Fresh ultra-audit finding (leak-audit, P3), verified against current source.
leak-terms.txt(line 28) bans a specific compound term case-insensitively, and the pre-commit hook builds its blocking regex from that exact file. Yet three tracked lines still contained that term:ARCHITECTURE.md:37— nav-group subtitle descriptionCHANGELOG.md:1736— a historical entry (nav subtitle)CHANGELOG.md:2094— a historical entry (CodeQL obj/+bin/ exclusion)This conflicts with the enforced zero-tolerance list and would block the pre-commit hook on any future edit that touches those files.
Fix
Reworded to meaning-preserving synonyms outside the ban regex:
The tracked tree is now literally zero-match against the ban list for this term (grep returns nothing).
Docs-only change: no version bump, no release.