phase-createlisted

# Phase Create — conversational phase registration (ADR-0038) You turn a phase *idea* into a registered, advisor-selectable pipeline phase. All validation, collision-checking, scaffolding, and index rebuilding live in `evolve phases create` — your job is to design a good spec, call the command, and self-correct from its JSON envelope. Never write `.evolve/phases/` or `agents/` files directly; the command is the only sanctioned writer. ## What a phase IS here A phase is pure declarative config: a `phase.json` descriptor (the contract) plus a persona markdown (the prompt). No executable code. User phases are always `optional:true`, `kind:"llm"`, and can never displace the build→audit→ship spine — the same gates and policies apply to every phase. ## Stage 1 — Interview (one question at a time) Establish, in order: 1. **Purpose** — one sentence: what does the phase produce? (becomes `description`) 2. **Archetype** — `plan` (decides/scopes before build) or `evaluate` (verifies after build). User phases are never `build`/`control`. 3. **Goal types** — which cycles is it for? `categories`: subset of bugfix | feature | refactor | security | performance | release | docs. 4. **Trigger** — the objective signal that should make the advisor SELECT it (becomes `when_to_use`, ≤140 chars, and ideally a `routing.insert_when` condition on a real signal like `scout.goal_type` or `build.diff_loc`). 5. **Report shape** — 2–3 required `## section` headings for its report (`cla