debuglisted

# debug Find the cause first, fix it never. `debug` investigates and routes; it does not touch code. It drives one closed loop — **reproduce** (Phase 1) → confirm by cited evidence (Phases 2–3) → hand `/fix` a regression test that re-runs the repro and must pass (**verify**). The minimal repro is the anchor that closes the loop; code changes belong to `/fix`. ## Pre-flight Read these, or STOP and surface the gap — never guess a log path, trace tool, or test runner: - `<project-root>/.codearbiter/tech-stack.md` — log paths, trace tooling, test runner conventions. The evidence sources. - `<project-root>/.codearbiter/CONTEXT.md` — domain vocabulary, system structure, and the `stage:` frontmatter (the maturity value; higher demands more rigorous evidence before exit). - `<project-root>/.codearbiter/security-controls.md` — only when the symptom touches a security boundary (auth, crypto, secrets). Optional; absent on most defects. The user MUST supply at least a one-sentence symptom. If absent, ask for one — do not guess the symptom. ## Phase 1 — Symptom capture · gate: BLOCK Record the symptom with enough fidelity that another operator reproduces it without further questions: - **Observed** — one sentence: what the system did. Not the suspected cause; causes belong to Phase 2. - **Expected** — one sentence. If the user cannot state expected behavior, that itself may be a design/behavior ambiguity — flag it for Phase 4. - **Minimal repro** — exact command/request/action, re