work-items/triage: canonicalize raw-intake marker axis across SKILL, evals, reference docs

[kyle-sexton]

This was generated by AI during triage.

The live raw-intake marker is priority: needs-triage, but SKILL.md, evals, and reference docs snapshot the concept as status: needs-triage — a priority-axis label documented as a status-axis label. This is the underlying axis-canonicalization question (distinct from the pure doc-sync in the sibling item): the docs must commit to which axis is canonical and bring evals + reference docs in line.

Decision defaulted: adopt the dual-axis raw marker (priority:needs-triage OR status:needs-triage, whichever axis a consuming repo files under) as canonical, matching PR #802's already-merged Scope-section wording — veto before merge. This keeps consuming repos free to file on either axis and is consistent with the marker definition already shipped in #802. Maintainer-vetoable alternative: pick a single canonical axis and migrate all docs/evals/live labels to it.

Acceptance: SKILL.md, the triage evals, and reference docs describe the raw-intake marker with one consistent axis treatment (dual-axis per the resolution unless vetoed); no remaining doc describes it as status-only where the live label is priority-axis.

Sweep-converted from #657.

[kyle-sexton]

This was generated by AI during triage.

Partial landing by work-items 0.18.1 (plugin reloaded 2026-07-21) — re-scope before working. The 0.18.1 triage SKILL.md now canonicalizes the raw-intake marker as dual-axis (status:needs-triage / priority:needs-triage, "whichever axis the repo files it under") across its Scope, state-table, and closing-invariant sections — the SKILL portion of this issue appears DONE.

Residual: verify the triage evals (evals.json) and any reference docs still treat the marker as status-only; if 0.18.1 already updated those too, this is fully already-implemented (maintainer close — this lane cannot close). Informational only — labels unchanged.

[kyle-sexton]