reconcile-roadmaplisted

# Reconcile Roadmap Make the thread-root `roadmap.md` and its decomposition a faithful expression of the decisions that govern the thread. You read the thread's authoritative inputs and the roadmap, correct the roadmap wherever the fix follows from those inputs, recheck what you changed, and hand any decomposition change that would alter human intent to `/emit-pending-decisions`. You edit only the roadmap; you never touch its authority sources, and you produce no separate report. Writing the corrected roadmap is where you stop — do not stage, commit, or push. The question you answer throughout: **does this roadmap, and the way it divides the initiative into children, follow from the decisions that govern the thread?** A faithful roadmap carries every governing decision, contradicts none, invents no commitment, and hands off children complete enough to open. ## 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