Refactor CLAUDE.md and skills/boss/SKILL.md

Consolidate Gitea issue tracking information into CLAUDE.md and simplify
its references in skills/boss/SKILL.md. The Gitea issue tracker section
was removed from CLAUDE.md as it was redundant and the information is
now more clearly presented in skills/boss/SKILL.md.

CLAUDE.md

@@ -223,27 +223,6 @@ not retroactively renamed.
   that close a backlog issue reference it via `closes #N` in the
   body; Gitea auto-closes the issue on push.
 
-- **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 (precedence order
-  matters): `BLOCKER` (core functionality broken — preempts
-  everything, /boss handles it before any other queue item;
-  typically also carries `bug`), `feature` (substantive
-  addition, no full spec), `bug` (observable misbehaviour —
-  surface inconsistency, false positive, wrong output), `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
-  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
   plan or code work for the milestone.