Debug

Use this when the goal is to understand and resolve incorrect behavior without guessing.

debug is part of the execution cluster, but its job is diagnosis before repair. A bug investigation without a durable record only solves the current incident and wastes the next one. debug is callable directly when no GitHub issue exists; bug-class issue resolve invokes the same RCA substrate through ../issue/references/causal-review.md Lens 1. Do not run critique before the facts needed for diagnosis exist. Once a debug slice closes repo work, hands off a fix, or authorizes repair, record the required critique before closeout so the next move does not inherit an untested repair story.

Bootstrap

Resolve the adapter first, then read the current debugging context.

Resolve $SKILL_DIR per ../../shared/references/bootstrap-resolution.md, then run: