Re-Plan Remaining Work

When To Run

• after a batch changes the blocker set materially
• after a batch changes proof ownership materially
• after scope re-interview
• after a restored contract owner proves the current plan under-shot or over-claimed reality

Hard Rules

• do not let remaining work collapse to browser/input only while corpus, claim-width, or example parity work is still open
• do not let “avoid rewrite” become a planning value
• do not let “support packages next” survive after the user has chosen the perfect redesign as the live doctrine
• if a kept row requires rewrite, plan the rewrite
• if a v2 north-star row is missing, keep it visible as a blocker instead of softening it into value-add

Refresh Afterward

• master-roadmap.md
• release-readiness-decision.md
• release-file-review-ledger.md
• true-slate-rc-proof-ledger.md
• references/pr-description.md