ward container: follow-ups (codex/qwen binaries, faithful context compose, headless-in-container, --build, runtime acceptance) #99

New issue

Closed

opened 2026-06-16 22:57:16 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-16 22:57:16 +00:00

Owner

Follow-ups from the ward container v0 (landed in c2cb54c, ward#98). Each is deliberately out of v0 scope.

1. codex / qwen agent binaries in the dev-base image

--mode codex|qwen already computes the progressively-less-context ladder and sets the agent command, but the dev-base image (agentic-os) only ships claude. The entrypoint drops to a shell for those modes today. Add the codex and qwen-opencode binaries to the dev-base image (or install them in the entrypoint) so the modes launch their agents.

2. Faithful per-harness context composition

v0 composes context with a simple level ladder (2=doctrine+host context, 1=doctrine+host AGENTS.md, 0=doctrine only). Replace with the real agent-compose generator run inside the container against the mounted sources + scopes, so the in-container slice matches what the host harness would compose.

3. Headless / cascade dispatch inside a container

The opaque model deferred in ward#98: run a headless/cascade dispatch surface inside an ephemeral container instead of a host worktree. Highest payoff, but iterating on headless is annoying — own it once interactive is proven live.

4. `--build` escape hatch

Rebuild the dev-base image from a local aos checkout for image iteration, instead of pulling the published tag.

5. Runtime acceptance

First live ward container up against a real repo (e.g. coilyco-gaming/eco-app): confirm the cached-fresh-clone, credential injection, context composition, and feature->merge->push loop end to end. v0 was built and dry-run-verified but docker was unavailable in the authoring sandbox.

Follow-ups from the `ward container` v0 (landed in c2cb54c, ward#98). Each is deliberately out of v0 scope. ## 1. codex / qwen agent binaries in the dev-base image `--mode codex|qwen` already computes the progressively-less-context ladder and sets the agent command, but the dev-base image (agentic-os) only ships `claude`. The entrypoint drops to a shell for those modes today. Add the codex and qwen-opencode binaries to the dev-base image (or install them in the entrypoint) so the modes launch their agents. ## 2. Faithful per-harness context composition v0 composes context with a simple level ladder (2=doctrine+host context, 1=doctrine+host AGENTS.md, 0=doctrine only). Replace with the real agent-compose generator run inside the container against the mounted sources + scopes, so the in-container slice matches what the host harness would compose. ## 3. Headless / cascade dispatch inside a container The opaque model deferred in ward#98: run a headless/cascade dispatch surface inside an ephemeral container instead of a host worktree. Highest payoff, but iterating on headless is annoying — own it once interactive is proven live. ## 4. `--build` escape hatch Rebuild the dev-base image from a local aos checkout for image iteration, instead of pulling the published tag. ## 5. Runtime acceptance First live `ward container up` against a real repo (e.g. coilyco-gaming/eco-app): confirm the cached-fresh-clone, credential injection, context composition, and feature->merge->push loop end to end. v0 was built and dry-run-verified but docker was unavailable in the authoring sandbox.

coilysiren added the

label

2026-06-17 07:05:38 +00:00

coilysiren commented

2026-06-17 08:21:57 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:21:58 +00:00