Brummel
19321d85ca
New label for "core functionality broken" — the only category with a hard precedence rule baked into the skill system, not a judgement call. No issues carry it today; the label and the skills must know about it so that the first time one is filed, the orchestrator handles it without a one-off "what now?" exchange. In-tree changes: - CLAUDE.md: Gitea-issues bullet introduces a "precedence order matters" note and lists `BLOCKER` first. - skills/boss/SKILL.md: Step 1 gains a dedicated `BLOCKER` precedence paragraph — every queue read starts with `tea issues ls --labels BLOCKER --state open`; if hit, it's the next dispatch (RED-first via skills/debug), preempting whatever else is in flight. The "finish the current agent call first, don't strand a working tree mid-edit" caveat is written in. - skills/brainstorm/SKILL.md: Step 7.5 tea-create template flags that BLOCKER can stack on top of the kind label. Universal bug-fix mechanics (RED-first TDD via skills/debug) are unchanged — BLOCKER is a precedence tag, not a new workflow. The /boss "Direction freedom" section continues to gate cross-milestone hops; BLOCKER is an in-milestone preempt that doesn't bounce back to the user (it has the orchestrator's implicit authority by definition). Verification: cargo test --workspace 647/0/2, architect_sweeps exit 0.