Brummel/AILang
1
0
Fork 0
Code Issues 29 Pull Requests Actions Packages Projects Releases Wiki Activity

workflow: retire milestone label — Gitea milestone container IS the concept

Browse Source 
The `milestone` label was a dead duplicate of Gitea's first-class
milestone container. Zero issues carried it (the three actual
big-chunks — Flat array, Iteration-totality, Stateful islands —
live as Gitea milestone containers, not as labelled issues).
Same pattern as `prio:p1`: a slot that never gets used because
the concept it tries to label lives somewhere else.

Label deleted in Gitea. Remaining labels: `feature`, `idea`,
`in-progress` (three, all semantic, no taxonomy noise). Big-
chunk work continues to live as Gitea milestone containers
(reached via `tea milestones ls --repo Brummel/AILang`).

In-tree changes:

- CLAUDE.md: Gitea-issues bullet describes the three-label
  shape; explicit note that milestone is a Gitea container,
  not a label.
- skills/boss/SKILL.md: Step 1 filter set drops `milestone`,
  adds `tea milestones ls` for the container view; direction-
  freedom "new milestone" trigger reworded around the
  container, not the label.
- skills/brainstorm/SKILL.md: Step 7.5 tea-create template
  drops `milestone` from the choice set; adds a note that
  spec-needing deferred work should be filed as a Gitea
  milestone container via `tea milestones create` instead.

Verification: cargo test --workspace 647/0/2, architect_sweeps
exit 0, zero residual `milestone`-as-label refs in live docs
(grep skip-listed legitimate "Gitea milestone (container)"
prose).
This commit is contained in:
Brummel
2026-05-20 15:24:26 +02:00
parent d8379a15ba
commit a5540c5620
3 changed files with 27 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+8 -7
View File
@@ -226,13 +226,14 @@ not retroactively renamed.
- **Gitea issues** (since 2026-05-20) are the forward queue —
milestones, features, todos, and ideas. Browse:
http://192.168.178.103:3000/Brummel/AILang/issues. CLI: `tea
issues ls --repo Brummel/AILang`. Labels: `milestone` (needs a
`docs/specs/` entry, bounces back to the user in /boss),
`feature` (substantive addition, no full spec), `idea` (may be
cut, no commitment), `in-progress` (work has started). An
unlabelled issue is the default: a concrete task to just do,
no spec needed. Big chunks live as Gitea **milestones**
(containers); smaller items are standalone issues. No formal
issues ls --repo Brummel/AILang`. Labels: `feature`
(substantive addition, no full spec), `idea` (may be cut, no
commitment), `in-progress` (work has started). An unlabelled
issue is the default: a concrete task to just do, no spec
needed. Big chunks live as Gitea **milestone containers**
(first-class Gitea concept, not a label — needs a
`docs/specs/` entry, opening one bounces back to the user in
/boss); smaller items are standalone issues. No formal
priority axis — "what's next" is an orchestrator judgement
call per session, not a pre-set label. The orchestrator owns
the backlog: opening new issues, retagging, closing on