[Gastown] Interrupted sub-agent task session persists as default view on every UI refresh

[kilo-code-bot]

What happened?

When a sub-agent task (launched via the Task tool, e.g. a 'general' agent) is interrupted/aborted mid-execution, its incomplete conversation session persists and is displayed as the default/active view every time the user refreshes the Gastown web UI. The user must manually click "Parent Up" to dismiss the interrupted sub-agent output and return to the parent (mayor) conversation.

Reproduction:

1. Launch a task via the Task tool (e.g. general sub-agent for bulk bead deletion)
2. Interrupt/abort the task mid-execution (e.g. quota exhaustion, or manual abort)
3. Refresh the Gastown web UI
4. The interrupted sub-agent's output (e.g. a series of gt_bead_delete calls ending in "Tool execution aborted" / "interrupted") is displayed as the current view
5. User must click "Parent Up" to get back to the mayor conversation

Expected behavior: An interrupted/aborted sub-agent session should either auto-resolve (close) or NOT be loaded as the default view on refresh. The UI should default to the parent (mayor) conversation, with interrupted sub-agent sessions accessible but not blocking.

Town: b1d2b62b-b236-48c0-8558-3b32057470be. The interrupted session was a general sub-agent doing bulk gt_bead_delete calls on rig bf5ad67d-50f9-4360-ba01-fcb41ce0ab6c.

Area

Terminal UI

Context

• Town ID: b1d2b62b-b236-48c0-8558-3b32057470be
• Agent: Mayor (d0f9f7a6-3442-4cd2-bc2f-e6acf48d536a)

Filed automatically by the Mayor via gt_report_bug.