cm-debugginglisted

# Systematic Debugging ## TL;DR - **Use when** any bug, test failure, or unexpected behavior surfaces - **Process**: reproduce → isolate → diagnose root cause → fix - **Defense in depth**: also add a test that locks the bug - **Next**: cm-tdd → cm-quality-gate ## Overview Random fixes waste time and create new bugs. Quick patches mask underlying issues. **Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure. **Violating the letter of this process is violating the spirit of debugging.** ## The Iron Law ``` NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST ``` If you haven't completed Phase 1, you cannot propose fixes. ## When to Use Use for ANY technical issue: - Test failures - Bugs in production - Unexpected behavior - Performance problems - Build failures - Integration issues **Use this ESPECIALLY when:** - Under time pressure (emergencies make guessing tempting) - "Just one quick fix" seems obvious - You've already tried multiple fixes - Previous fix didn't work - You don't fully understand the issue **Don't skip when:** - Issue seems simple (simple bugs have root causes too) - You're in a hurry (rushing guarantees rework) - Manager wants it fixed NOW (systematic is faster than thrashing) ## The Four Phases You MUST complete each phase before proceeding to the next. ### Phase 0.5: Memory Integrity Check (BEFORE blaming code) > **BEFORE blaming code, ASK: "Could memory be causing this bug?"** 1. **SUSPECT** — Identify re