devrites-debug-recoverylisted

# devrites-debug-recovery: fix the root cause, not the symptom Use a reproducible recovery loop. **NO shotgun edits, NO blanket retries.** ## When to invoke Loaded by Build/Prove when a test, build, typecheck, runtime, or browser failure has no clear next move. ## The seven-step cycle 1. **Build the feedback loop:** create a fast, deterministic, agent-runnable pass/fail signal. Spend most of the investigation here. See [build-the-loop.md](reference/build-the-loop.md). 2. **Reproduce:** run the loop. Confirm the failure matches the user's report (not a nearby failure); capture the **exact error text**; confirm reproducibility (or a high enough repro rate for flaky bugs). Do not proceed without reproduction. 3. **Ranked hypotheses (3-5, falsifiable):** generate the list before testing any of them. Each must state a prediction. **Completion:** 3-5 distinct hypotheses each state an observable prediction. See [hypotheses.md](reference/hypotheses.md). 4. **Trace when ambiguous:** if the cause is unclear, flaky, causal, or one fix already failed, run the competing-hypothesis trace branch before editing. Completion: top hypothesis has evidence for/against plus one discriminating probe. See [trace.md](reference/trace.md). 5. **Instrument:** debugger > logs > "log everything and grep". One variable at a time. Tagged debug-log prefixes. **Completion:** one discriminating signal is captured for the top hypothesis. See [instrumentation.md](re