[w1ne]

What

Stops tracking regenerable demo intermediates under artifacts/catalog-demos/:

• */frames/ (all files): the PNG slides each bundle's capture script encodes into its MP4.
• */video-review/ generated images (decoded frames, contact sheets, sampled frames) and the script-written video-inspection.json / review.json, for every bundle whose own script writes that directory.

1,233 files removed. MP4s, posters, bundle READMEs, generator/inspect scripts and all other evidence stay.

Size

Tracked blob sizes (git ls-tree -r -l):

	bytes	files
before (cdcf94d)	617,492,030	15,583
after	485,385,147	14,350

That is 132.1 MB and 1,233 files fewer in the working tree. History is not rewritten: the old blobs remain in git history, so clone size is unchanged.

Kept tracked on purpose

• Hand-written review notes in video-review/ (visual-review.md, inspection-notes.md, inspection.json): not produced by any script.
• video-review/ contents of 21 bundles whose scripts do not write that directory (ad-hoc ffmpeg sampling; about 12 MB incl. the notes above). Without a committed generator they are not regenerable, so they stay.
• frames.ffconcat / frames.txt list files at bundle root (small, rewritten by the capture scripts, contain absolute paths from the original machine).

Regeneration

Each affected bundle README gets an "Untracked generated outputs" section naming its capture and inspect commands. Ignore rules in .gitignore cover frames/, video-review/**/*.png, video-review/video-inspection.json, video-review/review.json, so regenerated output does not show up in git status (the capture scripts still re-encode the tracked MP4 and poster).

Dangling references

• 26 Markdown links to removed files were replaced with plain text plus the path marked "not tracked".
• JSON files that record video-review/contact-sheet.png or frames/... as strings (video-inspection.json, verification.json, settings.json) are left as written: the scripts emit those strings, and nothing reads them back.
• Link check over all tracked Markdown (relative links, including <a>/<img> and reference definitions): 111 dangling links before, 111 after, none introduced (the 111 pre-existing ones are untouched; 11 are under or into artifacts/).
• Nothing in src, tests, scripts, .github, vite configs or package.json reads these paths; npm pack --dry-run includes no artifacts/ file. catalog/kits/*/README.md links only point at bundle READMEs and scripts, which still exist.

Verified

• npm run typecheck, npm run qc:lint (lint + cookbook validate): pass.
• vitest: scripts/repoHygieneAudit.test.ts, tests/integration/catalog/catalogIndex.test.ts (index drift), tests/unit/architecture: 12 tests pass.
• Regeneration end to end for airfield-wave-20261102 and marine-wave-20261102: removed frames/ and video-review/, ran the capture then inspect script, which recreated 8 frames and 10 review files per bundle (same counts as the removed ones). Generated files stayed untracked/ignored; I reverted the re-encoded MP4/poster.

Not verified

• Full qc:build and the full unit suite were not run locally; only the files-enumerating checks above.
• The other 97 bundles' scripts were not executed, only checked statically (script writes the directory and the file-name pattern).
• The two test bundles were rendered with a substitute font because DejaVu is not installed on the test machine, so the frames differ slightly from the removed ones.

🤖 Generated with Claude Code