Design follow-up: tool result streaming semantics for client-connected sessions

[deathbyknowledge]

Background

While continuing the async refactor, I confirmed there are two pending tool route modes:

• (initiated by agent loop)
• (initiated by connected UI client request)

Current behavior surfaces tool-call errors/results back to client only for route via websocket response.

Question / follow-up

Should a client currently connected to a session receive live updates for tool execution results while the session run is still ongoing (e.g., to stream tool calls/results), or is waiting for session completion acceptable for now?

Proposed

• Open an issue to decide and track separately from this refactor.
• If streaming is desired, implement a dedicated event channel for tool-call progress and session lifecycle notifications.