reconcile-speclisted

# Reconcile Spec Make the thread-root `spec.md` a lossless, additive-free expression of the decisions that govern it. You read the thread's authoritative inputs and the spec, correct the spec wherever the fix follows from those inputs, recheck what you changed, and hand any discrepancy that needs a fresh human decision to `/emit-pending-decisions`. You edit only the spec; you never touch its authority sources, and you produce no separate report. Writing the corrected spec is where you stop — do not stage, commit, or push. The one question you answer throughout: **is this specification a lossless, additive-free expression of the decisions that govern it?** A lossless spec carries every governing decision and adds none of its own. ## Procedure 1. **Resolve the thread.** Work inside one thread root at `docs/threads/<YYMMDDHHMMSSZ-slug>/`. If `cwd` already sits inside a thread root, that is the thread. Two situations make a pending bundle physically impossible — `.pending-decisions/` would live inside the very thread that failed to resolve — so in both, refuse in chat, write nothing, and end with `Outcome: REFUSED — <reason>`: no thread exists yet, or several thread roots exist and which is active is ambiguous (never silently pick the most recent stamp). 2. **Load the authority.** Read the thread's `decisions.md` (what has been settled), `seed.md` (why the thread exists), and the relevant upstream artifacts the spec was built from (for example `proposal.md`), plus any artifa