feat(container): publish ward as a devcontainer Feature + customizations.ward #113

New issue

Closed

opened 2026-06-17 17:25:56 +00:00 by coilysiren · 4 comments

coilysiren commented

2026-06-17 17:25:56 +00:00

Owner

Goal

Invert the image relationship: instead of ward container wrapping one aos dev-base image, publish ward as a devcontainer Feature so any repo's existing .devcontainer opts into agent-driving via "features": { "ward": {...} }. This is the move that makes ward and "true devcontainers" genuinely the same system rather than two parallel container stacks.

The Feature

Package as one installable containers.dev Feature:

the embedded entrypoint (forgejo auth, ward install, clone, context compose, launch, reap),
the substrate warmer (preclone-repos.txt tiers into /substrate),
the doctrine composer (AGENTS.container.md + the mode ladder),
the permission policy (bypassPermissions + force-push deny).

Then ward stops owning the base image. Any repo declaring its own image/Dockerfile/features adds the ward Feature and gets agent-driving for free.

`customizations.ward` namespace

Add a customizations.ward block to carry per-repo ward policy in the same file humans already maintain:

mode ladder (claude/codex/qwen),
substrate tier selection,
--aws opt-in,
egress allowlist additions (pairs with the firewall issue).

This mirrors how [tool.agentic-os.*] carries per-repo hook opt-outs today: policy lives next to the thing it configures, not in ward's global defaults.

Sequence

Third of three. After the egress firewall and after .devcontainer/ consumption (separate issues). Bigger lift, but it is the endgame where ward and the open spec converge.

Refs the ward container epic agentic-os#220, ward#98.

## Goal Invert the image relationship: instead of `ward container` **wrapping** one aos dev-base image, **publish ward as a devcontainer Feature** so any repo's existing `.devcontainer` opts into agent-driving via `"features": { "ward": {...} }`. This is the move that makes ward and "true devcontainers" genuinely the same system rather than two parallel container stacks. ## The Feature Package as one installable containers.dev Feature: - the embedded entrypoint (forgejo auth, ward install, clone, context compose, launch, reap), - the substrate warmer (`preclone-repos.txt` tiers into `/substrate`), - the doctrine composer (`AGENTS.container.md` + the mode ladder), - the permission policy (`bypassPermissions` + force-push deny). Then ward stops owning the base image. Any repo declaring its own image/Dockerfile/features adds the ward Feature and gets agent-driving for free. ## `customizations.ward` namespace Add a `customizations.ward` block to carry **per-repo ward policy** in the same file humans already maintain: - mode ladder (`claude`/`codex`/`qwen`), - substrate tier selection, - `--aws` opt-in, - egress allowlist additions (pairs with the firewall issue). This mirrors how `[tool.agentic-os.*]` carries per-repo hook opt-outs today: policy lives next to the thing it configures, not in ward's global defaults. ## Sequence Third of three. After the egress firewall and after `.devcontainer/` consumption (separate issues). Bigger lift, but it is the endgame where ward and the open spec converge. Refs the `ward container` epic agentic-os#220, ward#98.

coilysiren added the

consult

labels

2026-06-18 06:18:31 +00:00

coilyco-ops commented

2026-06-24 17:26:10 +00:00

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P3 - Publish ward as a devcontainer Feature, big real feature, committed-ish direction, kept.
consult - Large design (image relationship inversion), human-gated start.

**Re-triage** (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24) - **P3** - Publish ward as a devcontainer Feature, big real feature, committed-ish direction, kept. - **consult** - Large design (image relationship inversion), human-gated start.

coilyco-ops commented

2026-06-24 17:28:26 +00:00

Member

Re-triage (goose-triage method, claude-macos-kais-macbook-pro-2 as the judgment engine, 2026-06-24)

P3 - Publish ward as a devcontainer Feature, big real feature, committed-ish direction, kept.
consult - Large design (image relationship inversion), human-gated start.

coilyco-ops added

headless

and removed

consult

labels

2026-07-02 00:18:46 +00:00

coilyco-ops commented

2026-07-02 00:20:46 +00:00

Member

Flipped headless: concrete goal (publish ward as a devcontainer Feature). Pairs with #112 (consume devcontainer.json) - sequence 112 first so the Feature consumes the same contract it publishes. Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.