Two independent bugs made Qoder turns hang or fail outright.
1. The SSE read loop never terminated on the sentinel. `data: [DONE]`
broke only the inner line loop, so the outer loop kept awaiting
reader.read() until the socket closed. Qoder's gateway holds the body
open after the sentinel, so a reply that had already streamed in full
produced no `done` event: the agent sat there with the complete answer
buffered and no error, until something else timed the connection out.
The sentinel also arrives wrapped in an envelope (`body: "[DONE]"`),
which likewise only did `continue`, so both forms now end the loop.
The reader is cancelled once the reply is complete instead of being
left holding the connection.
2. Aborting a turn produced an invalid request. Assistant messages with
stopReason error/aborted are skipped, but the tool result that followed
was still emitted, leaving a `tool` message whose tool_call_id had no
matching tool_calls entry. Upstreams reject that with "tool must follow
a message with tool_calls" -- the same failure the null-content
workaround above it already guards against -- so after one cancelled
tool call, every later request in that session failed. Tool calls
belonging to a dropped turn are now recorded and their results dropped
with them.
Both fixes are covered by regression tests that fail on the current code:
the two stream tests time out at the 8s limit, and the transform tests
produce an orphaned tool message.