[Gastown] Triage dispatch loop: patrol creates triage beads for non-triage-role poles, infinite retry with no back-off #4147

What happened?

Problem

Patrol creates gt:triage beads every ~90 seconds and dispatches them to polecat agents (Maple, Birch, Clover, Ember). Polecats lack the triage role and cannot call gt_triage_resolve, so every dispatch fails with a 403 permission error. The patrol ignores the failure, marks the bead failed, and spawns a new one 90 seconds later — creating an infinite loop.

Symptom

• 50+ failed gt:triage beads have accumulated on rig 0474caf3-2480-400f-8d1a-37f00fbcf5ef since 2026-06-22 ~06:40
• New bead appears every ~90 seconds with the same title "Triage batch: N request(s)"
• Each fails within ~60 seconds of creation
• All created by patrol, assigned to Maple/Birch/Clover/Ember (all role=polecat)
• All have dispatch_attempts: 0 (the patrol assigns but never successfully dispatches)

Expected

One of:

1. Patrol should not create triage beads for rigs that have no triage-role agents (back-off on repeated failures)
2. Patrol should check agent roles before dispatching and skip if no triage agent available
3. The rig should be configured with at least one triage-role agent

Town Context

• Town: 253c591d-96d9-48ce-8bb2-358f9182c149
• Rig: 0474caf3-2480-400f-8d1a-37f00fbcf5ef (glaucus-app/game)
• Triggering source: PR Cloud Agent: prompt autocomplete (ghost text) #5 (Rework: Fix workflow syntax and add testing documentation) on branch gt/clover/a6d193eb

Impact

• Noisy failed bead spam filling rig bead list
• Mayor/agents are overwhelmed by triage escalation notifications
• Real work items and progress tracking are obscured
• The patrol loop cannot self-heal without external intervention

Area

Agent Dispatch / Scheduling

Context

• Town ID: 253c591d-96d9-48ce-8bb2-358f9182c149
• Agent: Mayor (a19c902e-c60a-4b22-851d-244bac34f676)
• Rig ID: 0474caf3-2480-400f-8d1a-37f00fbcf5ef

Recent Errors

Escalation from Maple: "this agent (role: polecat) does not have permission to resolve triage requests. Only agents assigned the triage role can call gt_triage_resolve."
Escalation from Toast: "Cannot push psychology implementation - git auth failure" (resolved)
Pattern: patrol creates triage bead → dispatches to polecat → 403 → fails → retry 90s later → infinite loop

Filed automatically by the Mayor via gt_report_bug.