debugging-diagnosislisted

# Debugging Diagnosis ## Goal Find the smallest proven cause of a bug, fix it, and leave regression coverage or clear validation evidence. ## When to use - The user reports a bug, failing test, runtime error, broken workflow, or flaky behavior. - A prior fix was speculative and needs a reproducible diagnosis. - The task needs root cause analysis before a code change. ## When not to use - The user asks for a pure design plan with no failing behavior. - The task is a known mechanical edit with an obvious validation command. - The user asks for a broad repo audit rather than a specific failure. ## Inputs to inspect - Exact error text, logs, screenshots, failing test output, or reproduction steps. - Recent diffs and `git status --short`. - Relevant package scripts, test commands, CI workflow, issue context, and domain docs if present. - Existing tests around the failing behavior. ## Workflow 1. Establish the failure in the current environment or state what cannot be reproduced. 2. Minimize the reproduction to the smallest command, input, route, component, or test case. 3. Form one or more falsifiable hypotheses and inspect only the files needed to test them. 4. Add temporary instrumentation only when it answers a specific question; remove it before completion. 5. Fix the smallest cause that explains the reproduction. 6. Add or update regression coverage at the observable behavior boundary. 7. Re-run the reproduction and the smallest relevant validation command. ## Safe