Issue 1: Azure encrypted content verification fails

Summary
Requests sometimes fail with invalid_encrypted_content and message The encrypted content ... could not be verified.

Error

{
  "error": {
    "message": "The encrypted content gAAA...5IEt could not be verified.",
    "type": "invalid_request_error",
    "param": null,
    "code": "invalid_encrypted_content"
  }
}

Impact
Chat fails for affected requests.

Steps to Reproduce

1. Start a chat request.
2. Observe intermittent failure with invalid_encrypted_content.

Expected
Encrypted content is accepted and chat completes. Or at a minimum, Codex automatically continues from where it was with all of the previous turn context present.

Actual
Request fails with invalid_encrypted_content.

Issue 2: Stream disconnects before completion

Summary
Streaming responses are cut off with: stream disconnected before completion: stream closed before response.completed.

Error

stream disconnected before completion: stream closed before response.completed

Impact
Streaming chat responses fail or truncate.

Steps to Reproduce

1. Start a streaming chat request.
2. Observe stream terminates early with the error above.

Expected
Stream completes and returns response.completed. Or at a minimum, Codex automatically continues from where it was with all of the previous turn context present.

Actual
Stream disconnects early.