feat(codex): add Daybreak Blue catalog entry

[miwgel]

Summary

Adds OpenAI Daybreak Blue (gpt-daybreak-blue-latest) to the Codex catalog:

• registers the routable model under codex-plus in models.json
• adds the corresponding Codex client metadata to codex_client_models.json

Without the routing entry, CLIProxyAPI rejects the model before contacting Codex with model_not_found / unknown provider for model gpt-daybreak-blue-latest, even when the upstream Codex OAuth model catalog advertises it as API-supported.

Source and observed metadata

OpenAI describes Daybreak Blue as access to frontier models with safeguards tailored for authorized defensive-security work:

• https://openai.com/index/expanding-daybreak-as-the-cyber-defense-window-narrows/
• https://learn.chatgpt.com/docs/cyber-safety

The authenticated Codex model catalog for client 0.147.0 returns:

• slug: gpt-daybreak-blue-latest
• display name: Daybreak Blue
• description: Latest frontier agentic coding model for broad defensive cybersecurity work.
• context window: 272000
• input modalities: text and image
• supported_in_api: true
• reasoning levels: low, medium, high, xhigh, max, and the client-side ultra mode

The codex_client_models.json object is copied exactly from that upstream model record. The routing entry follows the existing GPT-5.6 catalog shape; fields not published by the model endpoint (created, version, and max_completion_tokens) are intentionally omitted rather than inferred.

Tier scope

Daybreak access is separately approved and does not appear to be represented by the ordinary plan list in the returned model metadata. I have only added the routing entry to codex-plus, because that is the static CLIProxyAPI tier I could verify. I did not assume availability for free, team, or pro accounts.

If maintainers have upstream evidence for additional tier placement, I would be happy to adjust the PR.

Verification

• both JSON files parse successfully
• gpt-daybreak-blue-latest appears exactly once in codex-plus and nowhere in the other static Codex tiers
• the client metadata object matches the upstream record exactly
• the diff is additive and contains no credentials or account metadata

[rany2]

Is the behavior actually different from GPT 5.6 Sol? My understanding is that it's just an alias.