workflow: drop kind:/state: prefixes from Gitea labels

Labels renamed in Gitea (Tea propagated the rename to all 24
issues automatically):

- kind:milestone   → milestone
- kind:feature     → feature
- kind:todo        → todo
- kind:idea        → idea
- state:in-progress → in-progress

Five live labels total; no semantic ambiguity since milestone,
feature, todo, idea are all "class" and in-progress is the only
"state" — the prefixes were carrying zero distinguishing weight.

In-tree changes:

- CLAUDE.md: Gitea-issues bullet uses the bare label names.
- skills/boss/SKILL.md: Step 1 filter snippets + direction-
  freedom new-milestone trigger drop the prefixes.
- skills/brainstorm/SKILL.md: Step 7.5 tea-issues-create
  template drops the prefix on the --labels argument.

Verification: cargo test --workspace 647/0/2, architect_sweeps
exit 0, zero residual `kind:*` / `state:*` refs outside
docs/specs/ and docs/plans/.

CLAUDE.md

@@ -226,16 +226,16 @@ 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: `kind:{milestone,
-  feature,todo,idea}` (semantic class) and `state:in-progress`
+  issues ls --repo Brummel/AILang`. Labels: `milestone`,
+  `feature`, `todo`, `idea` (semantic class) and `in-progress`
   (work has started). Big chunks that get their own
   `docs/specs/` entry live as Gitea **milestones** (containers);
   smaller items are standalone issues. No formal priority axis —
   "what's next" is an orchestrator judgement call per session,
-  not a pre-set label. `kind:idea` is the "may be cut" marker.
-  The orchestrator owns the backlog: opening new issues,
-  retagging, closing on completion (typically via the
-  `closes #N` commit-body trailer).
+  not a pre-set label. `idea` is the "may be cut" marker. The
+  orchestrator owns the backlog: opening new issues, retagging,
+  closing on completion (typically via the `closes #N` commit-
+  body trailer).
 
 - **`docs/specs/<milestone>.md`** (since 2026-05-09): per-milestone
   design spec produced by `skills/brainstorm`. Hard-gate before any

skills/boss/SKILL.md

@@ -70,17 +70,17 @@ mode. This skill does not restate them.
 The Gitea issue backlog is the forward queue. Browse:
 http://192.168.178.103:3000/Brummel/AILang/issues. CLI:
 `tea issues ls --repo Brummel/AILang --state open` lists every
-open issue; `--labels kind:milestone` / `kind:feature` /
-`kind:todo` / `kind:idea` filters by semantic class. Read a
-candidate body with `tea issues <N> --repo Brummel/AILang`.
+open issue; `--labels milestone` / `feature` / `todo` / `idea`
+filters by semantic class. Read a candidate body with
+`tea issues <N> --repo Brummel/AILang`.
 
 There is no formal priority axis (`prio:*` labels were retired
 2026-05-20). Pick the next item by orchestrator judgement:
 typically the simplest in-flight follow-up to the just-closed
-milestone, then a `kind:todo` or `kind:feature` that unblocks
-something, then `kind:milestone` (which is itself a bounce-back
-per §"Direction freedom"). `kind:idea` is "may be cut" and
-should rarely be picked autonomously.
+milestone, then a `todo` or `feature` that unblocks something,
+then `milestone` (which is itself a bounce-back per §"Direction
+freedom"). `idea` is "may be cut" and should rarely be picked
+autonomously.
 
 If the entire open backlog is empty: skip to Step 5 (done-state).
 Do not invent work; an empty queue is a real signal that the
@@ -159,7 +159,7 @@ Bounce back to the user only when:
   dependency failure, a discovered invariant violation).
 - The user has explicitly asked for a checkpoint.
 - **The next item on the queue is a new milestone** — i.e. a
-  backlog issue (typically `kind:milestone`) that has no
+  backlog issue (typically labelled `milestone`) that has no
   `docs/specs/` file yet and would require dispatching `brainstorm`
   to even begin. Continuing an open milestone (next iter, audit,
   fieldtest, post-audit tidy) is autonomous; *starting* a new one

skills/brainstorm/SKILL.md

@@ -248,7 +248,7 @@ interpretation:
    ```bash
    tea issues create --repo Brummel/AILang \
      --title "<idea title>" \
-     --labels "kind:<milestone|feature|todo|idea>" \
+     --labels "<milestone|feature|todo|idea>" \
      --description "<one-line description>
 
    **context:** <why this is deferred>