Cleaner errors when a stream is interrupted

If something goes wrong mid-stream, you now get a single, clean error instead of raw internal noise dumped into your output. Streaming responses simply end with a short “upstream error — the request could not be completed” and stop, so your client and your agents see a tidy, predictable signal. Normal streaming — content, tool calls, reasoning, and usage — is unchanged.