chore: remove historical tier-1 dogfood bundles#137
Merged
Conversation
Drop the 30 date-stamped project-history bundles already classified as historical in CATALOG.md (week 1-7 milestone reviews, week6/7 phased rollout evidence, nerd-font investigations) plus the legacy generate-week3-bundles.sh helper. Update CATALOG.md, dogfood/README.md, and AGENTS.md to match. Bundles remain available in git history.
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.
What
Removes the 30 date-stamped historical dogfood bundles that
dogfood/CATALOG.mdalready classified as project-history rather than reviewer-facing references, plus the legacygenerate-week3-bundles.shhelper:20260319-*,20260320-*,20260321-*)20260322-*week4*,20260322-global-cli-context,20260322-dogfood-week4-features)20260323-week5-render-*,-review-helper,-platform-closure)20260325-week6-*,20260325-week7-*)20260326-*nerd-font*)Net effect:
dogfood/shrinks from 52 MB / 66 entries / 1465 files to 41 MB / 36 entries / 884 files (584 files, ~30k lines removed). The bundles remain available in git history.Why
The dogfood directory had accumulated one-off build-out evidence that made it hard to find the canonical, release-gate, and recovery bundles a new reviewer actually needs. This keeps the curated surface (canonical scenarios, validation/release gates, recovery bundles) intact and drops only what the catalog itself called historical.
Behavior changes
20260326-week9-release-readiness,20260325-week8-contract-locks,run-command,agent-uses-agent-ttyare untouched).dogfood/CATALOG.md: removed rows for deleted bundles; replaced the historical-bundles list with a git-history pointer.dogfood/README.md: dropped the legacy-helper-scripts section.AGENTS.md: removed thegenerate-week3-bundles.shexample.Validation
npx vitest run test/unit/tools/validate-bundle.test.ts test/unit/tools/validate-canonical-bundles.test.ts test/unit/tools/review-bundle.test.ts— 43 tests pass.npx tsx src/tools/validate-canonical-bundles.ts— all 4 canonical bundles pass; catalog parity passes (every CATALOG.md entry resolves to a directory).mise run ci— 160 test files / 1619 tests, build, and install smoke all green.Follow-up (not in this PR): a second tier of superseded one-off proof bundles (~10 MB) was identified and can be removed later if desired.
Generated with
mux• Model:anthropic:claude-fable-5• Thinking:high