Propagate chat completion model to Codex provider

[Backlisted]

Fixes /v1/chat/completions dropping request.model before Codex agent creation. Required for SafeHouse real-provider strict JSON proof.

[alt-glitch]

Duplicate of #10773 — same per-request model routing fix for /v1/chat/completions. See also #25552 (already flagged as dup of #10773), #24008, #16403, #18549, #5862.

[Backlisted]

Many thanks — understood. This PR came from a SafeHouse integration proof where `/v1/chat/completions` received a non-empty request model but the Codex provider path fell back to an empty/default model before agent creation. I’ll compare against #10773 and close this as duplicate if that PR fully covers the same routing path. If there is a preferred branch/commit to pin against for downstream integration testing, please point me to it.

…

________________________________ From: Siddharth Balyan ***@***.***> Sent: Saturday, 23 May 2026 3:43 PM To: NousResearch/hermes-agent ***@***.***> Cc: Justin Cussel ***@***.***>; Author ***@***.***> Subject: Re: [NousResearch/hermes-agent] Propagate chat completion model to Codex provider (PR #30767) [https://avatars.githubusercontent.com/u/52913345?s=20&v=4]alt-glitch left a comment (NousResearch/hermes-agent#30767)<#30767 (comment)> Duplicate of #10773<#10773> — same per-request model routing fix for /v1/chat/completions. See also #25552<#25552> (already flagged as dup of #10773<#10773>), #24008<#24008>, #16403<#16403>, #18549<#18549>, #5862<#5862>. — Reply to this email directly, view it on GitHub<#30767 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHA7L4NGBZ4GACMVFXBQ5YL44E3BRAVCNFSM6AAAAACZKC22CKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMRUGMYTAMZYGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[Backlisted]

Closing as duplicate of #10773 per maintainer guidance. SafeHouse will keep using the local patched Hermes worktree/Docker runtime until #10773 or an equivalent request-model routing fix lands upstream and SafeHouse strict eval is rerun successfully.