fix(codex): recover null-output Responses turns

[blackduckai]

Summary

• recover Codex Responses turns that return null output by falling back through the existing create-stream path
• gate encrypted reasoning replay/include behavior to reasoning-capable models
• add Grok 4.3 context metadata and regression coverage for Codex/XAI provider parity

Test Plan

• python -m pytest tests/run_agent/test_codex_xai_oauth_recovery.py tests/run_agent/test_provider_parity.py -v --tb=short -o 'addopts='

🤖 Generated with Hermes Agent

[alt-glitch]

Late duplicate of merged #32963 (canonical Codex null-output fix). The null-output TypeError guard in run_codex_stream and run_codex_create_stream_fallback is already handled by #32963. The reasoning-gating additions in model_metadata.py are new but should be a separate PR. See also #33279 (same late duplicate pattern).

[teknium1]

Thanks for this — closing as already fixed on main.

The Codex null-output crash (response.completed with output: null from the chatgpt.com backend → TypeError: 'NoneType' object is not iterable → surfaced as "non-retryable HTTP None") is resolved by commits already on main:

• cb38ce28c — drop the SDK responses.stream() helper and consume events directly, rebuilding output from response.output_item.done events so the null terminal-event output is never iterated (refactor(codex): drop SDK responses.stream() helper; consume events directly #33042).
• 43a3f119f — recover Codex streams with null output.
• dc9d677d5 — classify TypeError('NoneType … not iterable') as a retryable provider-shape error so retry/fallback runs instead of killing the turn.

Your fix targets the same path that's now hardened upstream, so there's nothing left to merge here. Your authorship is preserved in your branch; I'm crediting your report in the umbrella issue #33932 (now closed). Appreciate the contribution.