Update SKILL.md

skills/boss/SKILL.md

@@ -67,34 +67,7 @@ mode. This skill does not restate them.
 
 ### Step 1 — Read the queue
 
-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 feature` / `bug` / `idea` filters by
-semantic class. Unlabelled issues are the default "just do it"
-bucket.
-Big chunks live as Gitea **milestone containers** — list via
-`tea milestones ls --repo Brummel/AILang`. Read a candidate
-issue body with `tea issues <N> --repo Brummel/AILang`.
-
-**`BLOCKER` always takes precedence.** Before any other pick,
-run `tea issues ls --repo Brummel/AILang --labels BLOCKER
---state open`. If even one open `BLOCKER` exists, that is the
-next dispatch — preempting current iter, audit, fieldtest,
-anything. Hand off to `skills/debug` for RED-first TDD per the
-universal bug-fix rule. A `BLOCKER` mid-session preempts the
-current step; finish the running agent call first (don't
-strand a working-tree mid-edit), then redirect. Only after the
-`BLOCKER` queue is empty does ordinary pickup resume.
-
-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 an unlabelled issue or a `feature` that
-unblocks something, then opening a new Gitea milestone
-container (which is itself a bounce-back per §"Direction
-freedom"). `idea` is "may be cut" and should rarely be picked
-autonomously.
+The Gitea issue backlog is the forward queue. 
 
 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