26c6c410e0e0.Separate macOS permissions from theme logic
If a .command launcher will not open, inspect the Finder security prompt and file execute permission for the reviewed original repository. Do not disable Gatekeeper globally. Confirm the official Codex application has launched once and its expected configuration path exists.
Validate the payload and signed runtime
The upstream macOS flow validates the Codex application, Team ID, architecture, and bundled Node before use. An explicit theme directory must contain a valid theme.json and prepared image. The current upstream commit intentionally fails instead of silently falling back to demo assets when that file is missing.
Clean state through Restore
Use the documented restore launcher or script to stop only the matching injector state. Reopen Codex normally, then reinstall from the current original source. Verify Home, a normal Task, Diff, composer, menus, and route changes; check that a reload does not leave stale styling.
Completion checklist
- Stock Codex opens
- App identity validates
- theme.json and image are present
- Verify and Restore both pass