huntlisted

# Hunt: Diagnose Before You Fix Prefix your first line with 🥷 inline, not as its own paragraph. A patch applied to a symptom creates a new bug somewhere else. ## Outcome Contract - Outcome: the root cause is identified before any fix is applied. - Done when: one sentence explains the cause, every observed symptom fits it, and the fix or handoff is verified against a reproducible check. - Evidence: source trace, repro command or UI path, logs or state, targeted test/build output, and runtime evidence for UI or native defects. - Output: root cause, fix or handoff, verification result, and any unswept sibling risks. **Do not touch code until you can state the root cause in one sentence:** > "I believe the root cause is [X] because [evidence]." Name a specific file, function, line, or condition. "A state management issue" is not testable. "Stale cache in `useUser` at `src/hooks/user.ts:42` because the dependency array is missing `userId`" is testable. If you cannot be that specific, you do not have a hypothesis yet. ## Diagnosis Signals Hypothesis quality gate: the hypothesis must explain every observable symptom, not just the one reported first; partial coverage is a symptom-level guess, not a root cause. For timing-dependent issues (flicker, intermittent failure, race), reproduce reliably before diagnosing. Rationalization smells: "I'll just try this" = no hypothesis, write it first. "I'm confident" = run the instrument that proves it. "Probably the same issue" = re-r