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

CODEXHOME (created by cqamkisolatedhome) and a LOCAL mock model provider (cqastartmock). Never QA against the real ~/.codex, never hit a real model API. The bundled scripts enforce this; if you run codex by hand, export CODEXHOME="$(mktemp -d)/codex"; mkdir -p "$CODEXHOME" 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-party way to prove a hook fired is the app-server notification

stream (hook/started / hook/completed), not log scraping. See [references/app-server.md](references/app-server.md).

• The captured JSON / pane IS the evidence — write it under

.omo/evidence/<YYYYMMDD>-<slug>/ (no evidence file == the QA did not happen).

Setup

cd <this-skill-dir>                        # .agents/skills/codex-qa
bash scripts/lib/common.sh --self-check    # confirm deps + isolation harness

Docker is the default QA surface. Run this QA inside a disposable container that has the latest codex and a copy of your config, with the host ~/.codex untouched: script/agent/qa-docker.sh (see [references/docker-qa.md](references/docker-qa.md)). The local scripts below are the fallback for when Docker is unavailable or on Windows.

Router: pick your case

Scripts index (each is its own regression test)

When TUI visual QA evidence is needed, follow docs/reference/web-terminal-visual-qa.md: render the TUI through the real xterm.js web terminal - NEVER the tmux capture-pane frame, which degrades color and CJK width:

node script/qa/web-terminal-visual-qa.mjs --title "Codex TUI QA" \
  --command "codex" --input "{Enter}" \
  --evidence-dir .omo/evidence/<slug>/codex-web-terminal

The helper runs a real pty, renders it in xterm.js under Chrome, and writes terminal.txt, terminal-ansi.txt, terminal.png (true color), and metadata.json (--from-file <capture.ansi> replays a saved raw stream). Use that artifact set for TUI visual QA; use app-server-drive.sh --plugin for assertion-grade hook behavior.

Match QA to your change scope

• Component / hook logic (packages/omo-codex/plugin/components/*):

hook-unit-probe.sh for the exact stdout, THEN app-server-drive.sh --plugin to prove the live wiring. See [components-hooks.md](references/components-hooks.md).

• Installer / config.toml (packages/omo-codex/src/install/*):

install-verify.sh.

• Anything that affects a live session (hooks, agents, MCP wiring):

app-server-drive.sh --plugin, and tui-smoke.sh --plugin if the TUI path matters.

Capturing evidence

ev=".omo/evidence/$(date +%Y%m%d)-codex-qa-<slug>"; mkdir -p "$ev"
bash scripts/app-server-drive.sh --plugin > "$ev/app-server-drive.json" 2>&1
bash scripts/install-verify.sh --self-test > "$ev/install-verify.txt" 2>&1

On /debugging

There is no /debugging command in Codex. To observe a run: the app-server notification stream (above), RUSTLOG=debug on the app-server's stderr, the logs SQLite under $CODEXHOME, the TUI's /debug-config, and the codex debug … subcommands. See [logging-debug.md](references/logging-debug.md).