Debug runtime failures systematically

Hypothesis-driven debugging across any runtime or binary

Production bugs and flaky tests when you need runtime truth instead of plausible code stories.

• · crash, hang, silent failure, or wrong response
• · source code or binary (optional)

• · root cause confirmed by observed state
• · minimal fix with failing test locked in
• · verification via actual system use

• · language-specific debugger (pdb, node inspect, lldb, gdb, dlv, pwndbg)
• · Playwright for browser bugs
• · language/binary-specific references

Runtime accessible; debugger available for target language

• · Code reading replaces runtime investigation
• · Debugging artifacts not cleaned
• · Source-map failures silent (Node.js tsx gotcha)
• · Async/race conditions not reproducible

• · MANDATORY: reads runtime-specific reference (python.md, node.md, rust.md, go.md, native-binary.md) before attaching
• · Leaves no debugging artifacts (journals then removes)
• · Two-discipline rule: runtime truth > code reading, no trace