ce-debuglisted

# Debug **Invocation input:** Failing feature, test, verdict, error, or misbehaving component: $ARGUMENTS Diagnose why something is failing and route the fix — without fixing it here. `/ce-debug` is invoked on a **failure or a symptom**: a red `auto` test, a failed acceptance criterion or broken journey from `/ce-verify`, a `Fail` / `Blocked` verdict, a correctness finding from `/ce-review`, a task that has hit `/ce-implement`'s `~3-attempt` limit, a pasted error / stack trace — **or** a live component making no progress: a consumer that stopped, a worker that went silent, a job that never fires. It **reproduces or investigates**, **localizes** the cause, and **routes** a targeted fix to the layer that owns it. It writes one artifact and mutates nothing else. It runs in one of **two auto-detected modes**, chosen by a Stage-0 probe of plan state — you never have to know which: - **Planned mode** — a `docs/plans/<slug>/specs/<id>/ce-spec.md` owns the failing feature. The spec is the **contract**: reproduce → localize to one `file:line` root cause → classify (`bug` / `spec-gap` / `structural`) → route one fix. - **Plan-free mode** — no plan/spec owns the target (the rest of the world's code). Reproduction may be impossible at the desk, so the tool maps the mechanism, generates hypotheses from a curated failure bank, grades each against the evidence available, and produces a **discrimination plan** — the cheapest observations that settle what static reading cann