← graph

thin-wrapper-smoke

thin-wrapper-smoke-codex

Metadata

Statusdone
Assignedagent-194
Agent identityf51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e
Created2026-04-26T17:29:45.836121845+00:00
Started2026-04-27T01:53:13.701469565+00:00
Completed2026-04-27T02:37:19.826926187+00:00
Tagseval-scheduled
Eval score0.92
└ blocking impact0.89
└ completeness0.95
└ constraint fidelity0.55
└ coordination overhead0.91
└ correctness0.95
└ downstream usability0.93
└ efficiency0.88
└ intent fidelity0.92
└ style adherence0.92

Description

Description

Extend wave-1-integration-smoke with the user's exact verbatim repro for the new codex-thin-wrap path. This is the HARD GATE for Phase 2 success.

Repro (must succeed end-to-end)

cd $(mktemp -d)
wg init -m qwen3-coder -e https://lambda01.tail334fe6.ts.net:30000 -x codex
wg service start
wg tui
# send 5 messages back-to-back in chat
# all 5 must produce responses

If the codex binary is not installed locally, emit SKIP (not failure) so CI doesn't break, but log clearly that the live smoke was not exercised.

File scope (no overlap with siblings)

  • tests/wave_1_smoke.rs OR scripts/smoke/codex_oai_5turn.sh (whichever pattern wave-1-integration-smoke established — check that task's artifacts first)
  • DO NOT touch src/commands/codex_handler.rs (that's the impl task's file)
  • DO NOT touch docs/ (that's the docs task's scope)

Validation

  • Smoke script / test exists and is wired into the wave-1 smoke harness.
  • When codex CLI is installed and a real lambda01-style endpoint is reachable, all 5 turns succeed (no fault on turn 2 — the original nex pain).
  • When codex CLI is NOT installed, script emits a clear SKIP with explanatory message and exits 0.
  • Behavioral assertions, not just exit-code assertions: assert the chat log shows 5 outbox responses, each with non-empty body and a distinct request_id.
  • cargo build + cargo test pass with no regressions.

Implement directly — do not decompose further.

Depends on

Required by

Log