Update triage taxonomy with agent: primary types and agent:priority-high

.agents/skills/triage-issue-local/SKILL.md

@@ -24,14 +24,27 @@ marks as overridable.
 - When the issue includes screenshots, videos, logs, stack traces, or command output, use them as primary evidence and ask follow-up questions only for missing details that cannot be inferred from that evidence.
 - Before asking any follow-up questions, check the Warp documentation and the repository's existing feature set to determine whether the desired behavior the reporter is describing is already supported. If an existing feature, setting, or workflow satisfies the request, recommend it to the reporter instead of treating the issue as a bug or feature gap.
 - If the report is about billing (pricing, plans, subscriptions, payments, refunds, invoices, AI request quotas, charges) or about appeals (account suspensions, bans, takedowns, abuse decisions, or other account-status disputes), do not attempt to triage it as an actionable bug or feature request. Instead, notify the reporter that these requests must go through Warp's support channels (https://docs.warp.dev/support-and-community/troubleshooting-and-support/sending-us-feedback) and direct them there for resolution. Apply the relevant `area:billing` or `area:auth` label as appropriate so the issue is still routed correctly.
+- Classify issues into at least one primary agent type (`agent:bug`, `agent:feature`, `agent:security`, `agent:documentation`), except billing or appeals reports which route to support via `warp:needs-support`. Explicitly bias towards tagging regressions ("broke in recent version", "worked in previous build"), panics/crashes, and security reports with `agent:priority-high`.
 
 ## Follow-up question limit
 
 Ask **at most 2 follow-up questions** per triage response. Each question must be high-value: it should meaningfully change the label assignment, owner routing, or reproduction confidence if answered. Do not ask questions whose answers can be inferred from existing evidence, and do not bundle multiple sub-questions into a single bullet. If more than 2 unknowns exist, prioritize the two that are most likely to unblock triage.
 
 ## Label taxonomy
 
-The label taxonomy for this repository is managed in `.github/issue-triage/config.json`. Prefer labels from that configuration, especially the `area:*`, `os:*`, `repro:*`, `accessibility`, `needs-info`, `duplicate`, and primary issue-type labels. Do not invent new labels unless the prompt explicitly allows it.
+The label taxonomy for this repository is managed in `.github/issue-triage/config.json`. Prefer labels from that configuration, especially the `area:*`, `os:*`, `repro:*`, `accessibility`, `needs-info`, `duplicate`, `agent:priority-high`, and primary agent issue-type labels (`agent:bug`, `agent:feature`, `agent:security`, `agent:documentation`). Do not invent new labels unless the prompt explicitly allows it.
+
+### Primary issue types
+
+Every issue should be classified with at least one primary agent type label:
+- `agent:bug`: Bugs/regressions. Assigned by Warp triage agent.
+- `agent:feature`: This issue is a feature request, not a bug report. Assigned by Warp triage agent.
+- `agent:security`: Security issues/vulnerabilities that are immediately escalated. Assigned by Warp triage agent.
+- `agent:documentation`: Missing documentation. Assigned by Warp triage agent.
+
+### Priority
+
+- `agent:priority-high`: High-priority issues that are immediately escalated. Assigned by Warp triage agent. Tag issues with `agent:priority-high` when there is evidence of a regression ("broke in recent version", "worked in previous build"), panic or crash, data loss, or a security vulnerability.
 
 Evaluate `ready-to-implement` during triage instead of relying on issue-template defaults. For bug reports, apply `ready-to-implement` only when the issue is reproducible from the provided evidence or straightforward local verification and the likely fix appears narrow enough to implement without a product spec, design mocks, or substantial investigation. If the bug is not reproducible, lacks a clear fix path, requires product/design decisions, or needs deeper technical discovery, omit `ready-to-implement` and prefer `needs-info`, `ready-to-spec`, `needs-mocks`, or the appropriate `repro:*` label.
 

.github/issue-triage/config.json

@@ -4,14 +4,26 @@
       "color": "d73a4a",
       "description": "Something isn't working."
     },
+    "agent:bug": {
+      "color": "8ff8fd",
+      "description": "Bugs/regressions. Assigned by Warp triage agent."
+    },
+    "agent:feature": {
+      "color": "f47f64",
+      "description": "This issue is a feature request, not a bug report. Assigned by Warp triage agent."
+    },
+    "agent:security": {
+      "color": "a0ce9f",
+      "description": "Security issues/vulnerabilities that are immediately escalated. Assigned by Warp triage agent."
+    },
+    "agent:documentation": {
+      "color": "5f966f",
+      "description": "Missing documentation. Assigned by Warp triage agent."
+    },
     "enhancement": {
       "color": "a2eeef",
       "description": "New feature or request."
     },
-    "documentation": {
-      "color": "0075ca",
-      "description": "Improvements or additions to documentation."
-    },
     "duplicate": {
       "color": "cfd3d7",
       "description": "This issue or pull request already exists."
@@ -36,6 +48,10 @@
       "color": "0e8a16",
       "description": "The issue is ready for implementation work."
     },
+    "agent:priority-high": {
+      "color": "b60205",
+      "description": "High-priority issues that are immediately escalated. Assigned by Warp triage agent."
+    },
     "repro:high": {
       "color": "b60205",
       "description": "The report includes enough evidence that the issue appears highly reproducible."