Heads-up: agentic triage labelling starting Friday

[heavygee]

From Friday Jun 19, I'll start applying a more structured label taxonomy to the issue queue. Right now the tracker only uses the stock GitHub default labels (bug, enhancement, etc.) and almost nothing actually carries a label - of the 28 most recent open issues sampled, only 6 are labeled at all, and most of those came from the issue template's auto-tag.

Disclosure: this is an agentic process, and this post itself is part of it. A meta watcher agent will be applying the taxonomy below to new issues, with periodic backfill of the existing open queue. I'm the accountable human behind it - the per-issue labelling is done by the agent, but every decision traces back to me.

The taxonomy was derived from a baseline review of those 28 issues. It's additive - no existing label is renamed, recolored, or removed.

Proposed prefixes (~22 labels total):

• area: web | hub | cli | docs | build
• agent: claude | codex | cursor | opencode
• platform: windows | mobile | macos (no label = linux / cross-platform)
• type: adds performance, regression, rfc alongside the existing bug / enhancement
• status: needs-triage | needs-repro | needs-info | confirmed | pr-open | blocked-upstream
• community-pr flag for incoming non-collaborator PRs

Cadence:

• Daily-ish sweep of new issues. Apply prefixes confidently when clear, defer when not.
• Followup pass to update status when reporters reply or PRs get filed.
• Roll out gradually - new issues first, backfill the open queue over a few weeks.

What the agent won't do:

• Close issues or apply wontfix / invalid / duplicate - those are editorial calls.
• Rename, recolor, or delete any existing label.
• Touch issues already in active hands.

Additions, edits, or pushback on the taxonomy or cadence are welcome - reply before Friday and they'll be folded in. This is a starting baseline, designed to adapt.

Cheers.