[Gastown] Patrol assigned gt:triage batch to polecat instead of triage-capable agent

[kilo-code-bot]

What happened?

In town 2f754117-0135-4231-a687-1118e68ee8f2, rig 1836da20-66b5-4496-a0e7-336783b2c739, patrol created issue bead 992d97db-09c7-4e6b-a818-36ab8e783762 titled "Triage batch: 2 request(s)" with label gt:triage and assigned/hooked it to Maple, a polecat agent (38f96c0c-413c-410a-b8eb-19dc70db8e8d). This triggered high escalation b6c50fde-b395-4193-8621-0384337fcc56: "Triage agent permissions issue - polecat assigned to triage task". Mayor intervention: acknowledged the escalation, reset Maple, closed the misassigned triage bead with reason:wrong-agent-role, and reset Birch after it showed stale "Triaging 1 request" status despite being a polecat with no current hook. Expected behavior: gt:triage batches should only be dispatched to a triage-capable agent or handled by the control plane, never to polecats lacking triage permissions.

Area

Agent Dispatch / Scheduling

Context

• Town ID: 2f754117-0135-4231-a687-1118e68ee8f2
• Agent: Mayor (3b1518a2-1be0-42e0-bda9-d1c95aa8b83c)
• Rig ID: 1836da20-66b5-4496-a0e7-336783b2c739

Recent Errors

Escalation b6c50fde-b395-4193-8621-0384337fcc56 high severity. Misassigned triage batch bead 992d97db-09c7-4e6b-a818-36ab8e783762 created by patrol and assigned to Maple polecat. Birch later displayed stale agent_status_message "Triaging 1 request" with no hook.

Filed automatically by the Mayor via gt_report_bug.