[Bug] reasoning_content "invalid_request" on follow-up messages with OpenCodeZen DeepSeek-V4-Flash in thinking mode

Description
When using OpenCodeZen's DeepSeek-V4-Flash with thinking mode enabled, sending a follow-up message within the same session intermittently fails with:
Error from provider (Console): Upstream request failed: [invalid_request_error]
The reasoning_content in the thinking mode must be passed back to the API.
The error breaks tool invocations and upstream requests, interrupting the conversation until the session is restarted.
Steps to reproduce

1. Create a new session with OpenCodeZen's DeepSeek-V4-Flash with thinking mode enabled.
2. First message works fine.
3. Send a second (follow-up) message in the same session while reasoning output is present in the history.
4. The error triggers and the conversation is interrupted.
   Expected vs actual

• Expected: reasoning_content from history is passed back to the API correctly, or the client omits stale/empty reasoning fields.
• Actual: Request rejected with invalid_request_error; upstream request fails.
  Environment
• Provider: OpenCodeZen (configured via auth.json)
• Model: DeepSeek-V4-Flash (thinking mode)
• Error type: [invalid_request_error]
  Additional notes
• Official DeepSeek API does NOT exhibit this issue with the same model — the problem appears specific to the OpenCodeZen gateway's handling of reasoning_content.
• Restarting the session temporarily resolves it, but it reproduces again afterward.