debug

# debug ## Purpose Root cause analysis ONLY. Debug investigates — it does NOT fix. It traces errors through code, analyzes stack traces, forms and tests hypotheses, and identifies the exact cause before handing off to rune:fix. <HARD-GATE> Do NOT fix the code. Debug investigates only. Any code change is out of scope. If root cause cannot be identified after 3 hypothesis cycles: - Emit `agent.stuck` signal — `scout` zoom-out mode surfaces broader module map (structural pivot); `adversary` oracle-mode dispatches a stateless second-model pass (semantic pivot); both fire in parallel - If `oracle.response` arrives with confidence=high and cites file:line, treat as new hypothesis H_oracle and test directly (skip 3-cycle gate — it's externally validated) - Otherwise, escalate to `rune:problem-solver` for structured 5-Whys or Fishbone analysis - Or escalate to `rune:sequential-thinking` for multi-variable analysis - Report escalation in the Debug Report with all evidence gathered so far </HARD-GATE> ## Triggers - Called by `cook` when implementation hits unexpected errors - Called by `test` when a test fails with unclear reason - Called by `fix` when root cause is unclear before fixing - `/rune debug <issue>` — manual debugging - Auto-trigger: when error output contains stack trace or error code ## Calls (outbound) - `scout` (L2): find related code, trace imports, identify affected modules - `fix` (L2): when root cause found, hand off with diagnosis for fix application - `brai...