dotnet-techne-refactor-pipeline

# Refactoring/design loop (multi-agent) You are the orchestrator. Do not enumerate or trace code yourself - dispatch session-blind workers, persist their artifacts, and hold the gates. **No code is written or edited until the design is approved at the Phase D gate.** The roles: `refactor-cartographer`, `refactor-tracer`, `refactor-surveyor` (lighter mode), `refactor-conformance-auditor`. List your available agent roles; if they are missing, tell the user to run `scripts/install-codex.sh` from the plugin, then either stop or (with the user's consent) run the phases yourself in this context. ## Step 0 - Resolve target and state - Target: a ticket id or an area description. Slug it (e.g. `yb-1234`). - State file: `.episteme/DESIGN-<slug>.md` at the repository root (create `.episteme/` if missing). Codex has no reload hook: **re-read the file at the start of every session.** - **If it exists**, route on its frontmatter - the file is the source of truth, never conversation memory: `status: done` → nothing to resume; `status: blocked` → restate the blocker and ask; `status: awaiting-approval` → re-present the design at the Phase D gate; `status: active` → resume at the phase in `phase:`. - **If not**, create it with frontmatter (`target`, `sources` - where the request came from, `phase: R`, `status: active`, `design_revision: 0`) and sections `Why`, `References`, `Map`, `Traces`, `Probes`, `Design (approved)`, `Decision log`, `Deferred`, `Todo`, `Review findings`....