GLOSSARY.md: "Triage role" example names ready-for-afk, which has never been a triage label (actual role: ready-for-agent)

## What's wrong `GLOSSARY.md` line 19 defines: > **Triage role**: A canonical state-machine label applied to an **Issue** during triage (e.g. `needs-triage`, `ready-for-afk`). `ready-for-afk` is not one of the five canonical roles. The actual role is `ready-for-agent`: - `skills/engineering/triage/SKILL.md` line 35: `ready-for-agent`: fully specified, ready for an AFK agent - `skills/engineering/triage/SKILL.md` line 45, state transitions list - `skills/engineering/setup-matt-pocock-skills/SKILL.md` Section B (the five defaults) - `skills/engineering/setup-matt-pocock-skills/triage-labels.md` and `docs/agents/triage-labels.md` - this repo's actual labels: `ready-for-agent` exists; `ready-for-afk` does not I checked the full git history: `ready-for-afk` appears only in this file (and its `CONTEXT.md` predecessor) — it has never been a real label. ## Why it matters The glossary is the domain-language source of truth that skills are told to follow verbatim, and this entry is self-contradicting: it points at `docs/agents/triage-labels.md` for the label mapping, and that file says `ready-for-agent`. Label strings are load-bearing — an agent (or a maintainer) taking the glossary example at face value could `gh label create ready-for-afk`, splitting one triage role across two labels, or `--add-label ready-for-afk` and get a "label not found" error. ## Fix One word: `(e.g. \`needs-triage\`, \`ready-for-agent\`)`.