Codex Lab identity and channel naming

[shiny-code-bot]

Intent

Define the visible identity and channel markers for the forked Codex overlay so users can tell when they are running the fork rather than upstream Codex.

Parent: #1

Proposed Naming

• Codex CLI Lab for the forked CLI/substrate.
• Codex Lab for a Desktop app bundle that has been patched to use the Lab CLI.
• Treat Lab as a build/channel identity, not a permanent product rename.
• Keep Every Code as the overlay/workflow/personality/service layer where useful.

Finish Line

Produce a small identity spec covering:

• CLI version string, e.g. codex-cli-lab ... or codex-cli ... (Lab).
• doctor output: channel, binary path, fork commit, build date, upstream base commit.
• app-server initialize/version metadata if Desktop reads it.
• Desktop visible naming: whether first pilot keeps Codex.app or uses Codex Lab.app.
• how to avoid breaking Desktop compatibility when executable names or bundle IDs must stay upstream-compatible.
• how to make patched Desktop visually distinguishable without fighting Sparkle/update behavior too early.

Current Status

Planning decision from discussion:

Start with CLI Lab identity first, because the embedded binary may still need to be named codex for Desktop compatibility. Desktop Lab identity should be tested after the patcher works, because renaming the app bundle or bundle identifier may affect deep links, update behavior, signatures, and Desktop assumptions.

Guardrails

• Do not rename the fork/product broadly yet.
• Do not change bundle identifiers, app names, or executable names until Desktop compatibility is tested.
• Prefer additive channel/build metadata over invasive branding changes for the first proof.

[shiny-code-bot]

Naming adjustment

Decision from follow-up discussion: prefer Codex Lab as the channel/umbrella name, with form factors after it.

Working names:

• Codex Lab CLI for the forked CLI binary/channel.
• Codex Lab Desktop Patcher for the distributed tool that patches a user's own installed official Desktop app.
• Codex Lab Desktop only as the name of the user's local patched installation/state, not as a redistributed app bundle.

Rationale:

Putting Lab before CLI reads better when discussing both products together: Codex Lab CLI and Codex Lab Desktop Patcher. It also makes Codex Lab the visible channel while keeping the delivery vehicle explicit.

Updated guardrail:

Do not imply that we redistribute a full Codex Lab Desktop app. The thing we can distribute is the patcher plus our CLI; the patched Desktop app remains user-local.