codex-qa

# Codex QA QA the omo Codex Light edition (`packages/omo-codex/`, shipped as lazycodex). We exercise OUR plugin in a REAL Codex while touching nothing of the user's setup: an isolated `CODEX_HOME` + a local mock model means no real API call and the real `~/.codex` is never read or written. Each helper script ships a `--self-test` that asserts its scenario against the live machine, so the scripts are both the QA tools and their own regression checks. Verified against `codex-cli 0.140.0` (node, jq, tmux, bun on macOS). Confirm with `codex --version`; check a flag with `codex <cmd> --help`. ## Golden rules (read before running anything) - **QA ONLY our plugin.** Everything that spawns codex uses an isolated `CODEX_HOME` (created by `cqa_mk_isolated_home`) and a LOCAL mock model provider (`cqa_start_mock`). Never QA against the real `~/.codex`, never hit a real model API. The bundled scripts enforce this; if you run codex by hand, `export CODEX_HOME="$(mktemp -d)/codex"; mkdir -p "$CODEX_HOME"` FIRST (a set `CODEX_HOME` must already exist or codex hard-errors). - **Prove the real home stayed clean.** Every script shasums `~/.codex/config.toml` before and after and asserts it is unchanged. If you script by hand, do the same. - **The interactive `codex` is a shell function** that injects `--profile quotio`. Bash scripts bypass it and get the real binary; never rely on the interactive alias. See [references/isolation.md](references/isolation.md). - **The first-...