DO-NOT-MERGE · Scrub internal tracker IDs from shipped source + CI workflow, and tighten the sweep#222
Open
Antawari wants to merge 1 commit into
Conversation
This is a public tree, so internal tracker IDs must never ship in source or CI. Three surfaces are cleaned and the leak gate is tightened so the leak cannot recur: - src/bonfire/analysis/models.py: rewrite the seven tracker-bearing docstrings/comments into neutral descriptive prose. Comments and docstrings only — no identifiers, field names, defaults, validators, or executable code changed; model behavior is byte-identical (35 analysis-model tests still pass). - .github/workflows/smoke.yml: drop tracker IDs and internal milestone scaffolding from the workflow comments; the gate steps are unchanged. - tests/unit/test_no_bon_ref_in_src_sweep.py: set the allowlist to an empty frozenset so any future tracker ID in src/ fails the sweep instead of being permitted, and scrub the tracker refs and workshop vocabulary from the test's own docstrings and comments. Gates from inside the worktree: sweep + analysis-model suites green, ruff check + ruff format --check clean, smoke.yml valid YAML, and a grep for the tracker-ID shape across src/, the CI workflow, and the sweep test finds nothing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
This is a public tree, yet internal tracker IDs (
BON-NNN) had leaked into shipped code and CI, and the existing leak-sweep test allowlisted them rather than forbidding them. This PR cleans all three surfaces and tightens the gate so the leak cannot recur.src/bonfire/analysis/models.py— rewrote the seven tracker-bearing docstrings/comments into neutral descriptive prose (e.g.Frozen budget of Cartographer tunables (BON-226 §5).->Frozen budget of Cartographer tunables.;Gzip-compressed JSON — BON-231 Wave 2b cache seam.->Gzip-compressed JSON cache seam.). Comments/docstrings only — no identifiers, field names, defaults, validators, or executable code changed. Model behavior is byte-identical..github/workflows/smoke.yml— dropped tracker IDs + internal milestone scaffolding (scout report, comment hash) from workflow comments. The gate steps themselves are unchanged; still valid YAML.tests/unit/test_no_bon_ref_in_src_sweep.py— set_ALLOWLIST = frozenset()so any futureBON-NNNinsrc/fails the sweep instead of being permitted, and scrubbed the tracker refs + workshop vocabulary from the test's own docstrings/comments.docs/is intentionally out of scope for this unit (it is the larger separate decision).Why
A public repo must never ship internal tracker IDs. The previous allowlist made the leak a permanent fixture; emptying it converts the sweep from a recorder of known leaks into a true gate.
How to verify (exact commands)
TDD trail: with the allowlist emptied and
models.pystill dirty, the sweep went RED (7 offenders); after the scrub it is GREEN.Honest gate results (run inside the worktree)
test_no_bon_ref_in_src_sweep.py— 2 passed (test_allowlist_entries_still_resolvepasses trivially on the empty allowlist).test_analysis_models+test_analysis_schema+test_analysis_fingerprint) — 35 passed (behavior byte-identical).ruff check src/ tests/— All checks passed.ruff format --check src/ tests/— 311 files already formatted.smoke.yml— valid YAML (PyYAMLsafe_load, jobsmoke).grep -rnE 'BON-[0-9]'over src/ + smoke.yml + the sweep test — no matches (clean).Note: the broader
tests/unitsuite has pre-existing collection errors in this minimal venv (missing runtime deps unrelated to this change); the targeted suites above run clean.Closes BON-1624
operator merges — do not auto-merge