[Gastown] Bead reassignment API returns 500 during dispatch-stall recovery

[kilo-code-bot]

What happened?

While recovering stuck convoy bb0c6d3e in rig a71e40b0, attempts to reassign open/in-progress beads between active agents fail with HTTP 500. This blocks operator mitigation strategy (hot-swapping agents) while agents remain idle with hooks.

Area

Bead Board / Dashboard

Context

• Town ID: 6f539b88-e587-4282-9dde-d4db617d24da
• Agent: Mayor (8a4701aa-03de-4cf7-b433-91971be27a8c)
• Rig ID: a71e40b0-f3d6-46af-9f24-a2022ce3414e

Recent Errors

Two consecutive gt_bead_reassign calls failed with 'Gastown API error (500): Internal server error' for beads 80fb0e04-fabb-41bd-a580-b28a42f63e16 and 2bbdc462-5499-4ce8-8053-90ff4ef494b9. Concurrent state shows both agents idle with hooks and convoy blocked at 0/3.

Filed automatically by the Mayor via gt_report_bug.