triagelisted

Move issues on team `CAN` through a small state machine of triage roles, and file each one so the dispatcher can read it. **This body is self-sufficient — run it without reading anything else.** The pointers name where an argument lives, for when a step surprises you. The roles are owned by `docs/agents/triage-labels.md`, the tracker by `docs/agents/issue-tracker.md`. **Every path named here is relative to the CanonCore repository root.** In CanonCore that is the working directory. In a Provider repository this skill arrived as a Claude Code plugin, so the root is `${CLAUDE_PLUGIN_ROOT}` — and `${CLAUDE_PLUGIN_ROOT}/CLAUDE.md` and `${CLAUDE_PLUGIN_ROOT}/CONTEXT.md` are the documents to work to, because neither is in the repository you are working in. **`--workspace ad2669ec-93a5-4ce1-97fa-c7d9247a1452` goes on every `orca linear` call.** Orca is connected to three workspaces, does not infer one from the directory, and picks one silently. **Every command below carries it inline rather than relying on the guard**: the `PreToolUse` hook that refuses an unpinned call is declared in CanonCore's own `.claude/settings.json`, and `.claude-plugin/plugin.json` publishes the skills directory and nothing else — so in a Provider repository there is no hook, and an elided flag is an unpinned call with nothing to catch it. **Every comment or issue this skill posts opens with the disclaimer:** ``` > *This was generated by AI during triage.* ``` ## The roles **Two category roles**, whi