Keep ward container bootstrap independent of WARD_CONFIG_REF edge guard #958

New issue

Closed

opened 2026-07-10 06:33:12 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-10 06:33:12 +00:00

Member

Recent dispatches started reserving issues and then exiting before the agent launch. The drained agentic-os#417 log shows the container reaches ward v0.564.0, then dies in the internal container path:

ward container: WARD_CONFIG_REF: active config source is baked neutral default (no external config source active); expected WARD_CONFIG_REF to point at the coilyco bundle for target coilyco-flight-deck/agentic-os

ward container currently runs smartDefaultsGuard("ward container"), which calls selectConfigSource(). That is correct for edge/operator surfaces, but it is wrong for the internal container bootstrap/reap namespace. The container path must use ward-owned baked runtime data and must not require a live WARD_CONFIG_REF, otherwise a config-source diagnostic becomes a pre-agent smoke death and can leave stale reservations.

Fix the internal container namespace so it does not fail on missing WARD_CONFIG_REF for coilyco targets. Add a regression that ward container bootstrap/the container command does not run the selected edge config guard while ops still does.

Recent dispatches started reserving issues and then exiting before the agent launch. The drained `agentic-os#417` log shows the container reaches ward `v0.564.0`, then dies in the internal container path: ```text ward container: WARD_CONFIG_REF: active config source is baked neutral default (no external config source active); expected WARD_CONFIG_REF to point at the coilyco bundle for target coilyco-flight-deck/agentic-os ``` `ward container` currently runs `smartDefaultsGuard("ward container")`, which calls `selectConfigSource()`. That is correct for edge/operator surfaces, but it is wrong for the internal container bootstrap/reap namespace. The container path must use ward-owned baked runtime data and must not require a live `WARD_CONFIG_REF`, otherwise a config-source diagnostic becomes a pre-agent smoke death and can leave stale reservations. Fix the internal container namespace so it does not fail on missing `WARD_CONFIG_REF` for coilyco targets. Add a regression that `ward container bootstrap`/the container command does not run the selected edge config guard while `ops` still does.

coilyco-ops referenced this issue from a commit

2026-07-10 06:34:09 +00:00

fix(container): keep bootstrap off edge config guard (closes #958)

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-10 06:34:16 +00:00

fix(container): keep bootstrap off edge config guard #959

coilyco-ops closed this issue

2026-07-10 06:35:15 +00:00