docs(triage): retire the eight-seat role labels for Core Roster v2 #1237

Merged

coilysiren merged 1 commit from aos/claude/label-taxonomy-role-rename into main

2026-08-25 18:45:08 +00:00

coilyco-ops commented

2026-08-25 18:38:55 +00:00

Member

Step 5 of coilyco-flight-deck/agent-compose#342. Docs-only.

Why now

label-taxonomy.md carries its own rule: "Change the labels, the matchers, and these docs in one batch." The labels change in infrastructure#933. There are no matchers for role/*. This is the docs third.

What changed

The value list, the rename history, and two additions worth calling out.

This page now says it describes rather than defines. The taxonomy is declared in infrastructure's config/forgejo-label-taxonomy.yaml and converged from there. The authority used to be live Forgejo org state in one org, which a script copied outward, so a label change was an API call with no diff and no commit, and this page sat describing a set that had moved with nothing able to notice. Naming where the definition lives fixes the class rather than the instance.

The breaking-change warning is now scoped. It is load-bearing for priority/* and autonomy/*, which are matched by string in a dispatch gate, a doc-content test, two AGENTS files, a worklog, and a migration script. It does not reach role/*, which is matched nowhere outside this page. That distinction is what made this rename cheap, and reading the warning as uniform is what would have made it look expensive.

Do not merge this before the labels exist

Holding the merge deliberately, against this repo's usual merge-your-own-PR lane.

If this lands before Kai runs just forgejo-label-taxonomy with an owner token, the page names role/platform while the org still carries role/engineer. An agent following the page would apply a label that does not exist, and per the note in sirens-echo's AGENTS.md a wrong label name silently applies nothing rather than erroring.

The window hurts equally in both directions, which is exactly why the batch rule exists. Correct order:

Merge infrastructure#933.
Kai runs the apply with an owner token.
Merge this.

I will merge on confirmation that step 2 ran.

Refs coilyco-flight-deck/agent-compose#342

Step 5 of coilyco-flight-deck/agent-compose#342. Docs-only. ## Why now `label-taxonomy.md` carries its own rule: "Change the labels, the matchers, and these docs in one batch." The labels change in [infrastructure#933](https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/pulls/933). There are no matchers for `role/*`. This is the docs third. ## What changed The value list, the rename history, and two additions worth calling out. **This page now says it describes rather than defines.** The taxonomy is declared in infrastructure's `config/forgejo-label-taxonomy.yaml` and converged from there. The authority used to be live Forgejo org state in one org, which a script copied outward, so a label change was an API call with no diff and no commit, and this page sat describing a set that had moved with nothing able to notice. Naming where the definition lives fixes the class rather than the instance. **The breaking-change warning is now scoped.** It is load-bearing for `priority/*` and `autonomy/*`, which are matched by string in a dispatch gate, a doc-content test, two AGENTS files, a worklog, and a migration script. It does not reach `role/*`, which is matched nowhere outside this page. That distinction is what made this rename cheap, and reading the warning as uniform is what would have made it look expensive. ## Do not merge this before the labels exist **Holding the merge deliberately**, against this repo's usual merge-your-own-PR lane. If this lands before Kai runs `just forgejo-label-taxonomy` with an owner token, the page names `role/platform` while the org still carries `role/engineer`. An agent following the page would apply a label that does not exist, and per the note in sirens-echo's AGENTS.md a wrong label name **silently applies nothing** rather than erroring. The window hurts equally in both directions, which is exactly why the batch rule exists. Correct order: 1. Merge infrastructure#933. 2. Kai runs the apply with an owner token. 3. Merge this. I will merge on confirmation that step 2 ran. Refs coilyco-flight-deck/agent-compose#342

coilyco-ops added 1 commit

2026-08-25 18:38:55 +00:00

docs(triage): retire the eight-seat role labels for Core Roster v2

ci / aos-cli-tests (pull_request) Successful in 30s

Details

ci / aos-eval-tests (pull_request) Successful in 7s

Details

ci / ward-doctor (pull_request) Successful in 7s

Details

ci / gate (pull_request) Successful in 50s

Details

48628ad9b0

The role axis named the roster Core Roster v2 replaced, so no label existed for
any of the seven seats that do exist. The seats moved and the labels did not,
and nothing reported it.

Records the 2026-08-25 rename, all six mappings plus the new role/gamedev and
the two retirements, and notes that every rename was an edit in place so all
770 issues kept the label they already carried.

Two additions beyond the value list.

This page now says it describes rather than defines. The taxonomy is declared in
infrastructure's config/forgejo-label-taxonomy.yaml and converged from there.
The authority used to be live Forgejo org state in one org, copied outward by a
script, so a label change was an API call with no diff and no commit and this
page sat describing a set that had moved. Naming where the definition lives is
the fix for the class rather than the instance.

And the breaking-change warning is now scoped. It is load-bearing for priority/*
and autonomy/*, which are matched by string in a dispatch gate, a doc-content
test, two AGENTS files, a worklog, and a migration script. It does not reach
role/*, which is matched nowhere outside this page, and that is what made this
rename cheap. Reading the warning as uniform is what would have made it look
expensive.

Refs coilyco-flight-deck/agent-compose#342

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: tpm