After the role rename, role/gamedev starts empty while its issues sit on role/platform #345

New issue

Open

opened 2026-08-25 18:32:27 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-25 18:32:27 +00:00

Member

What this carries

#342 renames role/engineer to role/platform, carrying all 414 of its issues. That is correct as a rename and it is the only affordable way to move them, since a rename is an edit in place and costs no per-issue work.

It also creates a known misrouting. role/gamedev is a new seat with no predecessor label, so it is created empty. Game and mod work filed before Core Roster v2 existed wears role/engineer, because that was the only build seat at the time, and the rename will deposit all of it on role/platform.

A rename cannot fix this. It maps one name to one name and cannot know which of 414 issues belong to a seat that did not exist when they were filed.

Concrete instance

coilyco-gaming/eco-mods#19, "Tailoring and animal husbandry level 3 perks do not apply at mod benches", carries role/engineer and c#. That is Eco mod work and belongs to role/gamedev. It surfaced while preparing #342 step 4 and is one of sixteen issues read, so the true count across the coilyco-gaming repositories is unknown and larger.

Why this is cheap

The correction is additive. role/* is deliberately non-exclusive, so adding role/gamedev to an issue that also carries role/platform is legitimate rather than a conflict, and nothing has to be removed for the issue to become findable in the right queue. Nothing here needs an org owner token, because issue-label writes are repo-scoped rather than org-scoped.

Deciding whether to also drop role/platform from a pure-gamedev issue is a separate and smaller question, and it can be answered per issue after the sweep has shown the population.

What to do

Sweep the coilyco-gaming repositories for issues carrying role/platform after the rename: eco-app, eco-mods, eco-ops, factorio-mods, factory-game-v3, galaxy-gen, steam-ops, sirens-echo.
Judge per issue whether the work is game or mod work rather than platform work. eco-mods and factorio-mods are likely wholesale; eco-app is a service and likely stays platform.
Add role/gamedev where it belongs.
Decide, per issue, whether role/platform should also come off.
Report the count found, so role/gamedev starting empty is a recorded state rather than an assumed one.

Note

Nothing outside coilyco-gaming is in scope. A gamedev issue in another org is possible but unlikely enough that a fleet-wide sweep is not worth it until one turns up.

Blocked by

Blocked by #342 step 2, since role/gamedev and role/platform do not exist until the rename lands.

## What this carries #342 renames `role/engineer` to `role/platform`, carrying all 414 of its issues. That is correct as a rename and it is the only affordable way to move them, since a rename is an edit in place and costs no per-issue work. It also creates a known misrouting. `role/gamedev` is a new seat with no predecessor label, so it is created empty. Game and mod work filed before Core Roster v2 existed wears `role/engineer`, because that was the only build seat at the time, and the rename will deposit all of it on `role/platform`. A rename cannot fix this. It maps one name to one name and cannot know which of 414 issues belong to a seat that did not exist when they were filed. ## Concrete instance `coilyco-gaming/eco-mods#19`, "Tailoring and animal husbandry level 3 perks do not apply at mod benches", carries `role/engineer` and `c#`. That is Eco mod work and belongs to `role/gamedev`. It surfaced while preparing #342 step 4 and is one of sixteen issues read, so the true count across the `coilyco-gaming` repositories is unknown and larger. ## Why this is cheap The correction is **additive**. `role/*` is deliberately non-exclusive, so adding `role/gamedev` to an issue that also carries `role/platform` is legitimate rather than a conflict, and nothing has to be removed for the issue to become findable in the right queue. Nothing here needs an org owner token, because issue-label writes are repo-scoped rather than org-scoped. Deciding whether to also drop `role/platform` from a pure-gamedev issue is a separate and smaller question, and it can be answered per issue after the sweep has shown the population. ## What to do - [ ] Sweep the `coilyco-gaming` repositories for issues carrying `role/platform` after the rename: `eco-app`, `eco-mods`, `eco-ops`, `factorio-mods`, `factory-game-v3`, `galaxy-gen`, `steam-ops`, `sirens-echo`. - [ ] Judge per issue whether the work is game or mod work rather than platform work. `eco-mods` and `factorio-mods` are likely wholesale; `eco-app` is a service and likely stays platform. - [ ] Add `role/gamedev` where it belongs. - [ ] Decide, per issue, whether `role/platform` should also come off. - [ ] Report the count found, so `role/gamedev` starting empty is a recorded state rather than an assumed one. ## Note Nothing outside `coilyco-gaming` is in scope. A gamedev issue in another org is possible but unlikely enough that a fleet-wide sweep is not worth it until one turns up. ## Blocked by - Blocked by #342 step 2, since `role/gamedev` and `role/platform` do not exist until the rename lands.

coilyco-ops added the

priority

autonomy

headless

labels

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

coilyco-ops referenced this issue

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

Make the label taxonomy declarative, then rename role/* onto the current roster #342

coilyco-ops referenced this issue

2026-08-25 20:38:13 +00:00

Make the label taxonomy declarative, then rename role/* onto the current roster #342