re0-work

1Restart a project or artifact at v0, carrying forward only what the previous cycle proved.
2 
3## Goal
4 
5Restart from what the previous cycle proved. Keep the proven contracts, schemas, vocabulary, real-surface tests, quality gates and negative corpus. Leave behind accidental architecture, scaffold, explanatory UI, debug panels, shallow generated content, and code whose only value was learning what not to do. Reach for it when the foundation is wrong, accumulated code is misleading progress, or a new pass should learn from the old one without inheriting its accidental architecture.
6 
7## Workflow
8 
91. Read the `re0-memo` of the cycle being replaced, then the current plan, local domain notes, QA evidence, and the user complaint that triggered the restart, if any. A restart with no memo measuring where the old cycle stands stops here and asks for one, since a restart aimed without that measurement repeats the old plan's picture of itself.
10…