execution-debugging

<debugging_methodology> <scope_constraint> These steps apply ONLY to diagnosing the failing check. Do not expand beyond the files touched in the original execution. Do not redesign, refactor, or improve code outside the failure path. </scope_constraint>

When a test or build fails during stabilization, follow this sequence:

1. READ the full error output — not just the last line. Stack traces, assertion messages, and build logs contain the diagnosis.

2. REPRODUCE the failure in isolation before changing anything.

   • Run the specific failing test or build step alone.
   • If it passes in isolation but fails in the suite, the problem is shared state or ordering.

3. HYPOTHESIZE explicitly before each change.

   • State what you believe is wrong and what evidence supports that belief.
   • Do not change code "to see if it helps."