Aborted response error block renders out of order relative to subsequent prompt

[shellicar]

Current behaviour

When a request is aborted mid-stream and the user sends a follow-up, the error block ([error: Request was aborted.]) renders above the new prompt. Visually it appears as though the error is a response to the follow-up message rather than the previous query.

Expected order: prompt → error → next prompt → next response
Actual order: error → next prompt (swapped)

Reproduction

1. Send a query
2. Abort mid-stream
3. Type and send a follow-up message
4. Observe: error block and subsequent prompt appear in the wrong order