Brokered dispatch does not carry WARD_SMOKE_TEST_SKIP into the container #1505

Closed
opened 2026-07-22 09:01:32 +00:00 by coilyco-ops · 0 comments
Member

A director tried to work around the Opencode smoke-test bug by launching with WARD_SMOKE_TEST_SKIP=1, but the brokered run still executed the in-container smoke test.\n\nObserved on 2026-07-22:\n\n- Command shape used from the director surface: WARD_SMOKE_TEST_SKIP=1 warded engineer ... --harness opencode ....\n- The accepted AOS dispatch for coilyco-flight-deck/agentic-os#617 reached container engineer-opencode-agentic-os-617.\n- The container log still ran bootstrap prelaunch check start: opencode and failed in ollama smoke test.\n- There was no ollama smoke test skipped (WARD_SMOKE_TEST_SKIP=1) log line, so the env did not survive into the container.\n\nExpected behavior:\n\n- If WARD_SMOKE_TEST_SKIP=1 is the documented bypass for launch smoke tests, brokered dispatch should either carry it through explicitly or reject it with a clear message that the env override is unsupported from a director surface.\n- The supported bypass path should be documented and test-covered for host-direct and brokered launches.\n- If env passthrough is intentionally constrained, provide an explicit CLI/config flag for this bypass and keep it visible in the forwarded command/log.\n\nThis blocks workarounds for #1503 and adds to the current hard-stop state tracked at #1502.

A director tried to work around the Opencode smoke-test bug by launching with `WARD_SMOKE_TEST_SKIP=1`, but the brokered run still executed the in-container smoke test.\n\nObserved on 2026-07-22:\n\n- Command shape used from the director surface: `WARD_SMOKE_TEST_SKIP=1 warded engineer ... --harness opencode ...`.\n- The accepted AOS dispatch for https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/617 reached container `engineer-opencode-agentic-os-617`.\n- The container log still ran `bootstrap prelaunch check start: opencode` and failed in `ollama smoke test`.\n- There was no `ollama smoke test skipped (WARD_SMOKE_TEST_SKIP=1)` log line, so the env did not survive into the container.\n\nExpected behavior:\n\n- If `WARD_SMOKE_TEST_SKIP=1` is the documented bypass for launch smoke tests, brokered dispatch should either carry it through explicitly or reject it with a clear message that the env override is unsupported from a director surface.\n- The supported bypass path should be documented and test-covered for host-direct and brokered launches.\n- If env passthrough is intentionally constrained, provide an explicit CLI/config flag for this bypass and keep it visible in the forwarded command/log.\n\nThis blocks workarounds for https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1503 and adds to the current hard-stop state tracked at https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1502.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/ward#1505
No description provided.