feat(models): add Codex gpt-daybreak-blue-latest slot

[WaldemarFech]

What

Adds the missing Codex slot gpt-daybreak-blue-latest to the codex-pro bucket of models.json (entry cloned from gpt-5.6-luna).

Evidence

• The slug is real: it appears in the official Codex CLI client cache (models_cache.json, CLI 0.143.0) alongside gpt-reserve.
• Upstream accepts it: verified end-to-end through CLIProxyAPI with a Pro OAuth account — chat completion returned HTTP 200; function-calling and SSE streaming unaffected (the entry mirrors gpt-5.6-luna capabilities).
• Without this entry, users cannot route this model: the proxy router rejects ids outside its catalog with unknown provider for model ....

Scope notes

• Only the codex-pro bucket was touched; availability on free/plus/team tiers was not tested, so no entries were added there.
• codex_client_models.json intentionally left untouched - it appears to be generated material (see cmd/fetch_codex_models) containing large per-model base instructions; happy to mirror there as a follow-up if wanted.

[Copilot]

Pull request overview

Adds a missing Codex catalog model slot (gpt-daybreak-blue-latest) to the codex-pro section of models.json so the proxy router can recognize and route requests for it.

Changes:

• Added a new codex-pro model entry for gpt-daybreak-blue-latest.
• Included capability metadata (thinking levels, tool support, modalities) and a Codex client header override consistent with nearby entries.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[WaldemarFech]

Extra verification of this exact branch content through the production loader:

I temporarily pointed the CLIProxyAPI remote-updater URLs at this branch's raw files (uncommitted working-tree bend, no code change), built an otherwise unmodified binary, and started it WITHOUT -local-model.

Startup log:

startup model refresh completed from https://raw.githubusercontent.com/WaldemarFech/models/add-codex-daybreak-blue-latest/models.json, changes detected for providers: [codex]

Result:

• GET /v1/models includes gpt-daybreak-blue-latest (fed purely by remote fetch against branch content)
• chat completion on that slot returned HTTP 200 (probe message echoed as configured)

So the patch is proven end-to-end not just as an embedded-catalog change but through the real remote-update path every user runs.

[tiagodocouto]

Confirming the slot is live upstream: codex --model gpt-daybreak-blue-latest exec "ping" returns normally, so the id is a real routable model and not a placeholder.

Without this entry CLIProxyAPI refuses it at routing time — POST /v1/messages returns HTTP 400 unknown provider for model gpt-daybreak-blue-latest — so the catalog entry is the only missing piece.

One thing worth reconciling before merge: #35 proposes the same id with context_length: 272000 against the 372000 here.