Triaging issues

An issue needs triage when it has no board card, regardless of who filed it. That is the whole test, and it is deliberately about state, not authorship. The milestone is not part of the test; it decides where the card lands (milestoned → Todo, unmilestoned → Incoming), so an approved-but-unboarded issue is still swept in rather than skipped (Copilot). An outside reporter has no board access, so their issue necessarily lands this way, but so does a maintainer's, whenever they open one by hand instead of through the /issue-create flow. Write access makes the board reachable, not automatic. What puts an issue in Todo is somebody performing the approval, and an issue nobody did that for has not been approved, whoever's name is on it.

"Triage new issues" means running pass 1 over every unboarded open issue, then the board audit. Pass 2 is a human judgment call and is never done unprompted.

Pass 1, sweep them onto the board (no approval implied)

For each open issue with no card:

1. Apply the version label (v2 unless it's a fix for released v1 behavior) and the type label (bug / enhancement / documentation / chore / question, see /issue-create for the table). An outside reporter cannot set either, so both are applied here.
2. Add it to the board for that version, v2 → #28, v1 → #11.
3. Set Status to Incoming.
4. Set Priority with the rubric below (v2 only), and record the score in a comment. This is an assessment, not an approval, it's how the queue gets ordered for the maintainer who reviews it next.
5. Leave the milestone unset. Nobody has committed to shipping it yet, and an empty milestone is precisely what marks it as awaiting review.