bug-triage-classificationlisted

# Bug triage & classification Triage answers three questions and stops: **does it reproduce, how bad is it, what is the ready task?** It never fixes and never writes queue state — the `forge:queue` skill (invoked by the triage command) owns all writes. Triage hands back a draft; the command persists it. **Boundary vs `forge:queue` capture:** a report with repro intent — "this is broken," "X is failing," a stack trace, unexpected behavior — routes through triage first, here. A task-shaped TODO with no defect behind it — "we should add X," "let's track doing Y later" — has nothing to reproduce or classify; it goes straight to `forge:queue` as a plain task, not through this skill. ## 1. Reproduce first — minimal repro or bust Before classifying anything, reduce the report to the **smallest sequence of steps that reliably triggers the defect** on a stated environment. Strip unrelated setup; confirm the failing behavior appears and disappears when the trigger is present/absent. - A bug that reproduces gets steps + a severity classification (below). - A bug that does NOT reproduce stays **`state: backlog`** with a note recording what was tried, the environment used, and the missing information needed to reproduce. The triage output records **`REPRODUCED: no`**. Route it back for more detail; do not invent a severity to make the report look actionable. ## 2. Classify — severity × likelihood decision table Severity is the blast radius of one occurrence; likelihood is h