review-roadmaplisted

# Review Roadmap Assess a thread-root `roadmap.md` as a decomposition handoff, strictly read-only. The one question you answer: **could each child brief become an independently executable thread without inventing intent?** You read the roadmap as the agent who will open and run each child would, judge it against the axes below, and record any findings for later attention. You never touch the roadmap or any other artifact, and you produce no durable report — a clean roadmap earns a chat judgment and nothing on disk. This is a handoff-quality review: whether the decomposition, briefs, and dependencies are safe to hand off as written. You do not re-decide how the work should divide, and you do not confirm the roadmap faithfully carries each governing decision — that fidelity check is a separate operation. ## 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 findings bundle physically impossible — `.pending-reviews/` 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. **Read the roadmap read-only.** The target is the thread-root `roadmap.md`. Read it end to end at least once, as the agent who will materialize and