codex-adapterlisted

# Codex adapter ## Establish the runtime contract 1. Read `AGENTS.md`, `.agentic/project.json`, the active task, and `docs/60-tooling/CODEX.md`. 2. Run `./scripts/codex-doctor.sh` before changing Codex-specific files. 3. Treat `AGENTS.md` as the cross-runtime constitution. Treat `.codex/` as the Codex adapter and `.claude/` as the canonical local skill and safety-script source. 4. Do not add model selection, credentials, provider routing, network access, MCP servers, sandbox expansion, or approval bypasses without an explicit, separately reviewed requirement. ## Route work safely - Use the local checkout for orchestration or one foreground task. - Use `.codex/agents/` for bounded read-only product, architecture, research, design, security, QA, and integration analysis. - Prefer Codex's built-in `explorer` for general codebase mapping rather than duplicating that role locally. - Use one branch and worktree per independent write-heavy task. - Assign exclusive file or tightly coupled module ownership before parallel work starts. - Merge shared contracts before dependent implementations. - Keep the final evaluator separate from the builder. - Do not add a write-capable project subagent merely to simulate worktree isolation inside one checkout. Use `./scripts/task-plan.sh <TASK-ID>` before workspace creation and follow `docs/70-collaboration/PARALLEL_TERMINALS.md` for multi-terminal work. ## Maintain the adapter - Keep `.agents/skills` and the plugin