Verify the exact Daybreak Blue picker entry before review

[jmanico]

Change

The #243 review marked Daybreak unavailable without trying the exact Codex model-picker entry. Preserve the operator's requested Daybreak Blue selection (gpt-daybreak-blue-latest) and add an explicit access preflight, provenance requirements, and distinct statuses for untested access, failed probes, verified access and completed review.

The API catalog marks the alias deprecated, but the installed Codex catalog advertises this entry for the current account. Both the exact CLI probe and a no-fallback app-server turn succeeded with explicit Blue access. The underlying backend model is not exposed; no resolved model identity is claimed. GPT-6 Sol plus Blue is a separate selection, not an undisclosed substitute.

Compatibility and validation

Documentation only; no library or CI behavior changes. Codex CLI 0.163.0 accepted the documented command and completed READY. Authenticated catalog and app-server evidence corroborate the alias/program. An independent supplemental Daybreak review of final fix da8b7a0 returned MERGE, with static-review limitations disclosed; this occurred after publication and is not counted as pre-release coverage.

Focused Sol review: MERGE. New official documentation links resolve; git diff --check passes. Word count: 1,458 to 1,777; code-block content lines: 7 to 11. Runtime tests are unnecessary for this documentation-only change; required CI still applies.

Material AI assistance: Codex investigated and prepared the change, Sol reviewed it, and the requested Daybreak entry completed a supplemental review. Model recommendations do not replace maintainer controls.

• I kept the change scoped and preserved relevant notices.
• I checked documentation/changelog and tests for any behavior change.
• This PR contains no credentials or private vulnerability evidence.