dredgelisted

Not every problem is a bug. Not every bug needs debugging. Diagnose the failure first, then prescribe the response — two separate steps, never swapped. ## Context Contract **Required:** the user's failure description · once diagnosed, the implicated file/function. **Conditional:** an already resolved Banka classification, only in the Hard Reset path, to determine how to phrase the next-session handoff · wider codebase context, only if a first fix fails and re-diagnosis is needed. **Excluded by default:** the codebase beyond what the diagnosis implicates · no upfront state-resolution matrix — dredge doesn't run one. **Outputs:** a diagnosed failure mode with reasoning, plus a mode-specific proposal held for confirmation — or, when reproduction itself can't be confirmed, an `[OPEN — needs verification]` flag and a stop instead of a proposal. **Write authority:** none. ## Step 1 — Describe What Went Wrong ``` Describe what is wrong. Be specific: - What did you expect to happen? - What happened instead? - How many times have you tried to fix it already? ``` The number of fix attempts matters — it distinguishes a fresh problem from a session that's already gone wrong. ## Step 2 — Identify the Failure Mode **Mode 0 — Cannot reproduce.** The report describes a real interaction, but a genuine attempt to trigger it — following the same steps — does not produce the described behavior. → Not yet confirmed as any of the three modes below; diagnose the gap itself first. **Respo