materialize-roadmap-threadslisted

# Materialize Roadmap Threads Read a parent thread's `roadmap.md` child briefs and open the child threads they describe. You create one thread per brief that has no thread yet, delegate the normalized folder-and-file creation to `/allocate-thread`, and record each created thread's reference back into its brief. This is a repeatable operation: running it again after a partial run finishes the remaining briefs and touches nothing already done. ## Inputs This operation runs a complete read-only preflight before any substantive execution — before it allocates any child thread or writes anything. Every preflight failure writes nothing, creates no child, emits no bundle, and ends `Outcome: REFUSED — <reason and how to re-invoke>`. Resolving the parent is the first preflight gate: work inside one parent thread root at `docs/threads/<YYMMDDHHMMSSZ-slug>/` that contains a `roadmap.md`. If `cwd` already sits inside such a thread, that is the parent. Refuse when no such thread exists, or several exist and which is active is ambiguous (never silently pick the most recent stamp). If the resolved thread has no `roadmap.md`, there is nothing to materialize: end with `Outcome: REFUSED — no roadmap.md to materialize`. Read the parent's `roadmap.md` and locate its `### CB<N>:` child briefs. Each brief carries a title, `Outcome`, `Context`, `Scope and boundaries`, `Dependencies`, and `Relevant shared constraints`, and may carry a `Materialized thread:` line. ## Preflight every brief before