Network interruption corrupts conversation state: reasoning encrypted_content was not issued to this caller

When a temporary network interruption occurs during a stream/response, subsequent messages sent in the same conversation thread fail persistently with an upstream provider error. The thread becomes permanently unusable.

OpenCode returned an error: Error from provider (Console): Upstream request failed: [invalid_request_error] reasoning encrypted_content was not issued to this caller

Steps to Reproduce
Start an active chat/session that uses reasoning/thinking content from the upstream provider.

Trigger an interrupted connection or drop network connectivity while a response is being generated/streamed.

Once reconnected, attempt to continue the conversation by sending a new message.

Expected Behavior
The client should either:

Safely prune or omit corrupted/unverified incomplete reasoning payloads from the message history before re-sending upstream.

Offer an option to retry the interrupted turn without sending invalid cached tokens/signatures.

Actual Behavior
The previous turn saves an incomplete or invalid encrypted_content token in the context history. All subsequent calls pass this bad state back to the provider, causing the upstream API to reject the request and completely locking the user out of the thread.