debug-mode

# Debug Mode Use the **evidence loop** when the root cause is not proven. Avoid plausible fixes that only pass once. ## Activation boundary Reach for this skill — including autonomously, without waiting for the user to name it — when the user explicitly says `diagnose`/`debug`, **or** when a normal reproduction or inspection has *not* revealed the cause, especially for flaky, environment-specific, or production-only bugs. Do **not** enter debug-mode for a compiler/type/lint/test error whose cause is directly in the output, a review finding that already specifies both cause and fix, an already-proven root cause, or when debug-mode is already active. Never re-invoke debug-mode from inside an active debug-mode run — continue the existing evidence loop. Respect the user's verb: a `diagnose`-only request ends before the **Fix** step and applies no code change. A `debug` request, or an ordinary bug report with no explicit verb, continues through the **Fix** step as usual — do not withhold the fix just because the task didn't separately say "fix" or "correct". ## Workflow 1. **Understand.** Done when symptoms, affected surface, expected behavior, actual behavior, and smallest reproduction path are known. 2. **Feedback command.** Done when, where practical, one command — a failing test, a curl script, a CLI run on a fixture, a headless-browser script, a replayed trace — has been run once and shown red on this bug's exact symptom: red-capable (asserts the symptom, n...