debuglisted

# Debug Systematically debug the problem described in `$ARGUMENTS`. Do not guess. Do not fix without reproducing first. ## Step 1: Understand and categorize the problem Parse `$ARGUMENTS` for: - What is the observed behavior? - What is the expected behavior? - Is there an error message or stack trace? - When did this start? After what change? If critical information is missing, ask for it before proceeding. **Categorize the issue type** — the investigation strategy depends on this: - **Runtime error** — exception, crash, panic, unhandled promise rejection - **Logic error** — wrong output, incorrect calculation, unexpected state - **Performance** — slow response, high CPU/memory, timeout - **Intermittent** — flaky, race condition, timing-dependent - **Environment-specific** — works locally, fails in CI/staging/production - **Build/type error** — compilation failure, type mismatch, import error ## Step 2: Investigate — spawn the `debugger` agent Spawn the `debugger` agent to investigate in isolation. This keeps debug artifacts out of the main context and uses the agent's systematic root cause methodology. Pass the following as the agent task: ``` Bug report: <observed behavior from Step 1> Expected behavior: <expected behavior from Step 1> Issue category: <category from Step 1> Error/stack trace (if any): <paste here> Reproduce with: <failing test command or steps> ``` The `debugger` agent will return: - Root cause with evidence and location (`file:function:line`) - Pr