[Gastown] Repeated triage batch bead failures during early Gastown use

[kilo-code-bot]

What happened?

A new Gastown user reported that agents are failing the process and asked us to investigate and stop work. In this town (b917ba0f-b17b-49f3-ba3e-aea7a876d022), repeated auto-generated triage beads in rig 5a0848fc-9ad9-46bc-97d6-f8d7597cb24b are entering failed state in a loop during the first hour of usage.

Observed evidence:

• Four separate Triage batch: 1 request(s) issue beads failed between 15:45 and 15:51 UTC.
• Failed bead IDs: 3e30819c-8758-408c-a0f1-e4e205fc7260, e3c0996c-9e28-4963-a2ef-d446283ca3b2, d8963ae6-8698-45c9-bbf1-0d7344c80ac7, d02f2142-fc93-4513-b070-87a9d547a7d7.
• These were created by patrol, labeled gt:triage, and assigned to polecat Toast.
• The only user-requested convoy (48ad9fe7-b21d-4f50-9668-d2cefd5e5b79, title Prepare fork for Python port) has bead 7cf2608d-4d1c-4048-a361-d9c9b849a917 in in_review and a dependent bead still open, while the user perceives the system as unstable enough to abandon the session.
• Agent state at investigation time: polecat Toast is idle with status message Triage complete — 0 restarted, 0 escalated, 1 resolved via guidance; refinery is working on another hook bead bb313045-9803-4521-8fd9-c11f26a175c7.

Impact:

• Repeated visible failures in system-generated triage work erode confidence immediately after release.
• User explicitly asked to stop all work and plans to return later.

Please investigate triage/patrol dispatch or reconciliation around failed gt:triage batches and any coupling with early convoy execution/review state visibility.

Area

Agent Dispatch / Scheduling

Context

• Town ID: b917ba0f-b17b-49f3-ba3e-aea7a876d022
• Agent: Mayor (079afa0b-6735-4954-8db9-4449ae68b0a1)
• Rig ID: 5a0848fc-9ad9-46bc-97d6-f8d7597cb24b

Recent Errors

Failed triage batch issue beads repeatedly created by patrol and assigned to Toast: 3e30819c-8758-408c-a0f1-e4e205fc7260, e3c0996c-9e28-4963-a2ef-d446283ca3b2, d8963ae6-8698-45c9-bbf1-0d7344c80ac7, d02f2142-fc93-4513-b070-87a9d547a7d7. Convoy 48ad9fe7-b21d-4f50-9668-d2cefd5e5b79 active with primary bead 7cf2608d-4d1c-4048-a361-d9c9b849a917 in_review; user reports overall agent failure perception.

Filed automatically by the Mayor via gt_report_bug.