Fix stale UI after aborting a running message

[IgorWarzocha]

Problem

After aborting an in-flight message, the underlying session can keep running, but the UI no longer follows or reconnects to it. From the user's perspective the session is still doing work in the background while the visible conversation state is stale.

Scope

• Ensure aborting/cancelling an in-flight message leaves the UI and runtime session lifecycle in sync.
• If the session continues after abort, the UI should reattach to live updates instead of freezing on the aborted state.
• If abort is intended to stop the session, the runtime should actually stop and the UI should reflect that terminal state.

Acceptance criteria

• Repro: start a message, abort it, and verify the UI does not remain stale while the runtime continues producing work.
• The visible session state matches the actual runtime state after abort/cancel.
• Reopening or revisiting the session shows the current session output/status rather than the stale pre-abort view.
• Add coverage or a deterministic regression check for the abort/reconnect lifecycle if feasible.

Original issue text

report an issue - we dont seem to be picking up the session after aborting the message, it keeps on running but ui is stale