debug-mode

To reproduce and fix flaky race conditions, create a committed failing reproduction script, instrument suspect paths with tagged logs, capture output to a file, and analyze the logs to isolate the root cause. Apply a minimal fix and verify with a regression test.

The best way to debug unit test failures is using a hypothesis-driven triage approach. Generate ranked theories with evidence requirements, add targeted instrumentation logs, grep the captured debug file to confirm the hypothesis, and apply a minimal root-cause fix.

To safely add and remove debugging logs for API errors, commit a failing repro script first, add hypothesis-tagged logs on an isolated git branch, then use git restore to cleanly remove all instrumentation after analyzing the captured logs.

Yes, this debugging workflow requires an isolated git branch and stashes. It uses commit-first reproduction to safely add and remove instrumentation logs, ensuring runtime data capture remains isolated and code cleanup via git restore is verifiable.

To verify a bug fix and prevent regressions, perform mandatory red-to-green verification. Run the committed failing reproduction script or test, implement the minimal fix, and confirm the test passes from a failing red state to a green passing state.