check-planlisted

# Check Plan Check one plan folder against the thread's spec and correct it in place, end to end. You gather the thread's context, walk the plan task by task against the spec, fix every fault whose fix follows from the spec, hand what the spec does not settle to a pending-decision bundle, and report what you changed. You work from the gathered inputs alone, without walking the user fault-by-fault. Editing the plan folder is where you stop — do not stage, commit, or push. ## Inputs Gather all of these before checking; everything below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the plan. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - The thread's **`spec.md`** — the sole authority for every correction you make. A fault is a fault only because the spec says so, and a fix is available only because the spec settles it. Required: the check does not run on a thread that holds no spec. - **The plan folder to check** — the edit target, in one of two accepted forms. When the invocation **names a folder** under `plans/`, that folder is the form. Otherwise the form is the **newest folder under `plans/` by stamp**. Read everything in it: its index `plan.md`, and the task briefs under `plan-tasks/` when the plan is strict. - The thread's `adr/` and `glossary.md` — the thread's delta of the project layer, which inside the thread takes precedence over th