reconcilelisted

# Reconcile The `errata` skill catches what a session trips over. Nobody trips over the rest: `.genius/DECIDED.md`, `CONTEXT.md`, `DESIGN.md`, the pinned verify commands, the contracts of work still in flight. Those are read as authoritative by every fresh session precisely because nothing in the flow reads them adversarially — a decision's constraint the code stopped having, a term the code renamed, a command that no longer exists. Each one keeps being obeyed until something expensive happens. The concept: **the binding documents are claims about a repo that has moved. Go check them against it.** ## When to run it The user types it, and the moments worth typing it are the moments the answer changes something: before designing against settled ground in unfamiliar territory, after a refactor or dependency change large enough to have moved the ground, when a session has just cited a doc that turned out to be wrong, or when work resumes after weeks away. Not on a schedule. **A scan with nothing to find will find something** — sent looking, a model produces findings, and a manufactured drift correcting a document that was right is worse than the drift it invented. ## What gets checked Every line, against the repo — never against what you remember of it. With an argument, only that slug or that doc. - **`.genius/DECIDED.md`** — does each decision's constraint still exist in the code, and does its link still reach the fight that settled it? - **`CONTEXT.md`** — does the cod