debug

# Debug Diagnose efficiently and safely. Debugging produces evidence and a root-cause hypothesis; `/fix` turns that into a regression-tested patch. ## Planner Entry Perform triage, evidence gathering, and diagnosis directly in the primary conversation. Keep production edits out of the diagnostic phase, then proceed through `/fix` when code changes are needed. ## First: Create The Pipeline Create a visible task list: 1. **Triage** - classify the bug and choose the cheapest faithful path 2. **Gather evidence** - targeted test, source-selectable diagnostic bundle, browser state, or instrumentation 3. **Diagnose** - trace the failure to root cause 4. **Report** - summarize evidence and choose `/fix` when code changes are needed 5. **Clean up** - remove temporary logs, throwaway repro tests, isolated instances, and browser sessions ## Triage Gate Pick one path before launching anything: | Class | Signals | Reference | |---|---|---| | Backend logic | validation, dedup, data shaping, workflow routing, API/service behavior | `references/backend-repro.md` | | Live instance | user has a running instance already misbehaving and you need read-only state/logs | `references/instance.md` | | UI/browser | layout, focus, click flow, WS-driven UI, console/network behavior | `references/browser.md` plus `references/instance.md` | | Needs logs | current evidence is insufficient and instrumentation is needed | `references/instrumentation.md` | Rules: - Triage before launching anything. ...