once the codex tier work lands, three doc surfaces go stale:
adapters/README.md — the table still describes codex as "config.toml snippet": one file, one tier.
adapters/codex/README.md — documents only the manual ~/.codex/config.toml edit. it should lead with vouch install-mcp codex, explain the project-local .codex/config.toml choice, describe what each tier adds (mcp wire / AGENTS.md snippet / prompts / capture), and keep the manual edit as the fallback path.
docs/getting-started.md — mentions codex once, inside the mcp add one-liner; the install section should treat codex as a first-class host alongside claude-code.
no code. lowercase prose, match the existing adapter README voice. placeholder examples only — no real usernames, internal urls, or machine paths.
acceptance criteria
once the codex tier work lands, three doc surfaces go stale:
adapters/README.md— the table still describes codex as "config.tomlsnippet": one file, one tier.adapters/codex/README.md— documents only the manual~/.codex/config.tomledit. it should lead withvouch install-mcp codex, explain the project-local.codex/config.tomlchoice, describe what each tier adds (mcp wire / AGENTS.md snippet / prompts / capture), and keep the manual edit as the fallback path.docs/getting-started.md— mentions codex once, inside themcp addone-liner; the install section should treat codex as a first-class host alongside claude-code.no code. lowercase prose, match the existing adapter README voice. placeholder examples only — no real usernames, internal urls, or machine paths.
acceptance criteria
adapters/codex/README.mdcovers installer-first flow, per-tier summary, the prompts-location decision from the T3 ticket, and the manual fallback