Debug Broken Behavior With Systematic Root-Cause Investigation

Debugs broken things methodically. /investigate traces the data flow from input through the failing code, tests hypotheses about where the break occurred, and stops after 3 failed fix attempts to avoid infinite loops. It produces a detailed investigation report with decision logs so learnings persist.

1. Describe what's broken (error message, unexpected behavior, flow that fails). 2. /investigate freezes edits to the affected module, traces data flow from entry point to the error, and writes a hypothesis. 3. It tests the hypothesis by adding logs, reading outputs, or running a reproduction. 4. If the hypothesis fails, it revises and tests again. 5. After 3 failed hypotheses, it stops to avoid loops. Output: a detailed investigation report with data flow diagram, root cause, and (if found) a fix.

/investigateuses/freezeto restrict edits to the affected module. Learnings log viagstack-learnings-log. Investigation reports save to ~/.gstack/projects/{slug}/`. The Iron Law (no fixes without investigation) prevents fix loops by capping hypothesis tests at 3 failures per investigation.