PR #158 · Repository Cleanup
chore(repo): isolate benchmark bulk and preserve architecture work
What
Removes generated benchmark bulk from source control, preserves architecture-review HTML/PDF, and adds reproducibility guards and handoff docs.
Why now
bench/harness-bakeoff contained .venv, .zenith, node_modules, and run results. This slowed clones and obscured real source.
What changed
Benchmark bulk moved to memory archives; architecture docs preserved under deploy/pages-architecture/; .gitignore guards for generated artifacts; skills-lock.json for reproducible installs; implementation handoff + destructive cleanup inventory.
Risk / trade-off
Low risk. No source code changes. Original files archived on disk; repository records their location.
Money & ops
Smaller repo, faster CI, cleaner diffs, preserved institutional knowledge, and a documented AWS cleanup backlog.
CEO decision
Approve. Safe cleanup PR. No deploy needed.