.omo/evidence/20260721-ulw-loop-gajae-adoption/task-6.md
npm run check && npm test in packages/omo-codex/plugin/components/ulw-loop.bun run test:codex from repo root.node packages/omo-codex/plugin/components/ulw-loop/dist/cli.js ulw-loop ... inside a fresh mktemp -d git repo.~/.codex/config.toml isolation via SHA-256 before/after comparison.npm run check and full npm test with 40 files / 418 tests.VB001, completed G001 and auto-advanced to G002, applied a two-item --proposals-json batch, completed G002 and auto-advanced to G003, completed G003 as both validation-batch final and aggregate final, and emitted batch_closed for VB001.ULW_LOOP_VALIDATION_BATCH_OPEN.steering_rejected, accepted batch replay audit-free, conflict flags fail with ULW_LOOP_STEERING_BATCH_CONFLICT, and all validation error code cases.~/.codex/config.toml hash before and after was identical: 780c740e287bda48609b5c9d5ee3ee2fc20434ce1a58c36692ec07e279a161d5.tmp.lEHDskyq7B, tmp.gGowhcocQp, tmp.1f0qwLD50a./var/folders/nj/hqfr8ndn5q56cqw7jqgbrck40000gn/T/tmp.zfDGIZoOCs./var/folders/nj/hqfr8ndn5q56cqw7jqgbrck40000gn/T/tmp.fCBvMuWI5m./var/folders/nj/hqfr8ndn5q56cqw7jqgbrck40000gn/T/tmp.q8CGMWc1hV.This covers the requested real built CLI surface, the component suite, the repo Codex compatibility gate, the new auto-advance path, the atomic steering batch path, validation-batch closure, aggregate completion, fail-closed rejection, independent-review blocker regressions, and real Codex-home isolation.
No live Codex app-server/TUI probe was run because this ulw-loop task changed a standalone component CLI and the plan required CLI-only local-build QA. No published package or real Codex plugin cache was used.
task-6-component-gate.txttask-6-codex-gate.txttask-6-e2e-transcript.txtreviewer-fix-report.mdreviewer-fix-transcript.txt