Debugging Read [[principles/fix-root-causes]] before starting. Every debugging session follows that principle: trace to root cause, never paper over symptoms. Process 1. Reproduce. Get the exact error. Run the failing command, read the full output. If you can't reproduce, you can't verify your fix. 2. Read the error. The error message, stack trace, and line numbers are data. Read all of it before forming hypotheses. Most bugs tell you exactly where they are. 3. Suspect state before code. Before debugging code, check persistent state — especially on restart bugs or environment drift. See [[pri…