issue-triagelisted

# Issue Triage ## Overview Triage assigns structured metadata to issues so DISCUSS can refine them in priority order. Every triaged issue must have a **type**, **priority**, and **effort estimate** before it is eligible for DISCUSS. Core principle: **triage is classification, not refinement**. You are not writing acceptance criteria here — you are labeling, prioritizing, and estimating to enable the next phase. --- ## Label Taxonomy All GitHub issues passing through DISCOVER must receive labels from the following taxonomy. ### Type Labels | Label | When to Apply | |---|---| | `type/feature` | New user-facing capability that does not currently exist | | `type/bug` | Behavior that is incorrect relative to expected behavior | | `type/tech-debt` | Internal quality improvement — no change in user-facing behavior | | `type/docs` | Documentation — README, API docs, in-code comments | | `type/question` | Needs clarification before it can be triaged properly | ### Priority Labels | Label | Definition | |---|---| | `priority/P0` | Blocking users or a legal/compliance/data-loss risk. Must be addressed immediately. Requires written justification. | | `priority/P1` | High business value. Should be in the next sprint. | | `priority/P2` | Medium value. Target the next 2–3 sprints. | | `priority/P3` | Nice-to-have. Not in the current roadmap. Backlog item. | ### Effort Labels | Label | Duration | |---|---| | `effort/XS` | < 2 hours — a one-liner, config change, or text correction