Debug Mode

Use this skill to run a disciplined runtime debugging loop. Do not jump directly to a fix. The value of this skill is the stop-and-reproduce checkpoint after targeted instrumentation.

Use normal debugging instead for straightforward build errors, type errors, lint failures, obvious failing unit tests, or bugs already explained by existing logs. In those cases, mention runtime-debug only if runtime instrumentation would materially help.

Workflow

Read the relevant code and repro details.
List 2-5 ranked, falsifiable hypotheses with IDs such as H1, H2, and H3. Each hypothesis must predict what a runtime probe will show.
Start the local log collector. Make the loopback host explicit:
```
node <skill-dir>/scripts/log-server.mjs --dir .runtime-debug/logs --session <session_id> --host 127.0.0.1 --port 0
```
In unrestricted environments, run it normally. In managed sandboxes that block local port listeners, request the agent's normal escalation/approval for this collector on the first attempt instead of trying once, failing, and retrying. Do not tell the user the sandbox blocked the collector unless a sandboxed attempt actually failed. Use a narrow approval reason such as "Start the loopback-only runtime debug collector"; if the tool supports reusable approvals, scope the prefix to node <absolute-skill-dir>/scripts/log-server.mjs, not broad node or shell execution.