Skip to content

[Gastown] Patrol repeatedly assigns gt:triage batches to polecat agents #3785

@kilo-code-bot

Description

@kilo-code-bot

What happened?

Recurring issue in town 2f754117-0135-4231-a687-1118e68ee8f2, rig 1836da20-66b5-4496-a0e7-336783b2c739: patrol continues to create gt:triage issue beads and assign/hook them to polecat agents, which cannot resolve triage batches. This is a recurrence after prior bug #3780. Latest example: high escalation d2c04f91-60ba-485d-be72-8c5685071b75 at 2026-06-07T06:32:13Z, caused by triage batch bead 83d41177-2ede-4ce2-982c-ab7d91e37c10 assigned to Toast polecat c5d20ccc-1160-4f37-9913-1ad43f02e845. Maple also showed stale 'Triage blocked - role mismatch, escalated' status with no hook. Mayor intervention closed the triage bead, reset Toast and Maple, and acknowledged escalation. Expected behavior: patrol should not route gt:triage batches to polecats; these should be handled by a triage-capable role/control-plane path or not created if no such agent exists.

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 d2c04f91-60ba-485d-be72-8c5685071b75 high severity. Triage batch 83d41177-2ede-4ce2-982c-ab7d91e37c10 assigned to Toast polecat. Repeated failed triage batches also present from patrol around 06:17-06:30Z.

Filed automatically by the Mayor via gt_report_bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions