Bump dev-base ward to a config-ref capable release #390

New issue

Closed

opened 2026-07-09 20:36:38 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-09 20:36:38 +00:00

Member

Problem

The AOS dev-base image still bakes an old ward binary:

docker/dev-base/Dockerfile:20 ARG WARD_VERSION=0.396.0

The current ward release is v0.529.0. Current ward no longer builds a custom deployment-specific binary from the AOS ward-specs release asset. Since ward#653 / ward#650, the current path is one neutral ward binary plus live edge config selection via WARD_CONFIG_REF, documented in ward docs/release.md, docs/config-source.md, and docs/ward-kdl-authoring.md.

AOS does publish ward-specs-<tag>.tar.gz as a release asset and owns the coilyco .ward/ bundle, but the AOS image cannot exercise the current config-source behavior while it ships ward v0.396.0.

Scope

Update docker/dev-base/Dockerfile to a current ward tag that includes live WARD_CONFIG_REF support, likely the latest released tag unless there is a known regression.
Keep building ward from the pinned release tag. Pin the tag, not a commit hash.
Add or update any dev-base smoke check that verifies the baked ward version.
Do not revive the removed release-time ward-specs overlay. The custom coilyco config path is live WARD_CONFIG_REF, not a custom-built binary.
Note any dependency on #383 if publish-image is still blocked by the Homebrew layer when this lands.

Acceptance

docker/dev-base/Dockerfile no longer pins WARD_VERSION=0.396.0.
The dev-base build reaches a ward --version check for the new tag, or the failure is explicitly a pre-existing publish-image blocker.
Any docs that describe how AOS-provided ward config reaches ward mention the current live WARD_CONFIG_REF path rather than implying a custom ward binary is built from the release asset.
The change lands on Forgejo main with closes #N.

Status context

As of 2026-07-09, #383 is in flight to fix the current dev-base Homebrew install failure, and #385 is in flight to split the dev-base image into named tiers. This issue owns the stale ward release pin specifically.

## Problem The AOS dev-base image still bakes an old ward binary: ```text docker/dev-base/Dockerfile:20 ARG WARD_VERSION=0.396.0 ``` The current ward release is `v0.529.0`. Current ward no longer builds a custom deployment-specific binary from the AOS `ward-specs` release asset. Since ward#653 / ward#650, the current path is one neutral ward binary plus live edge config selection via `WARD_CONFIG_REF`, documented in ward `docs/release.md`, `docs/config-source.md`, and `docs/ward-kdl-authoring.md`. AOS does publish `ward-specs-<tag>.tar.gz` as a release asset and owns the coilyco `.ward/` bundle, but the AOS image cannot exercise the current config-source behavior while it ships ward `v0.396.0`. ## Scope * Update `docker/dev-base/Dockerfile` to a current ward tag that includes live `WARD_CONFIG_REF` support, likely the latest released tag unless there is a known regression. * Keep building ward from the pinned release tag. Pin the tag, not a commit hash. * Add or update any dev-base smoke check that verifies the baked ward version. * Do not revive the removed release-time `ward-specs` overlay. The custom coilyco config path is live `WARD_CONFIG_REF`, not a custom-built binary. * Note any dependency on #383 if publish-image is still blocked by the Homebrew layer when this lands. ## Acceptance * `docker/dev-base/Dockerfile` no longer pins `WARD_VERSION=0.396.0`. * The dev-base build reaches a `ward --version` check for the new tag, or the failure is explicitly a pre-existing publish-image blocker. * Any docs that describe how AOS-provided ward config reaches ward mention the current live `WARD_CONFIG_REF` path rather than implying a custom ward binary is built from the release asset. * The change lands on Forgejo `main` with `closes #N`. ## Status context As of 2026-07-09, #383 is in flight to fix the current dev-base Homebrew install failure, and #385 is in flight to split the dev-base image into named tiers. This issue owns the stale ward release pin specifically.

coilyco-ops commented

2026-07-09 20:36:46 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-agentic-os-390 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T20:36:44Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/agentic-os#390 · branch issue-390 · harness codex · workflow direct-to-main
Run: engineer-codex-agentic-os-390 · ward v0.493.0 · dispatched 2026-07-09T20:36:44Z
Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-agentic-os-390` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T20:36:44Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/agentic-os#390` · branch `issue-390` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-agentic-os-390` · ward `v0.493.0` · dispatched `2026-07-09T20:36:44Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 20:47:14 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: skipped (review gate skipped by ~/.ward/config.yaml default)
retrospective: the pin move was straightforward. the only friction came from the container disk ceiling during validation.
confidence: high
surprises: origin/main landed the named dev-base tier split while this branch was open, so the merge had to carry both changes.
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: skipped (review gate skipped by ~/.ward/config.yaml default) retrospective: the pin move was straightforward. the only friction came from the container disk ceiling during validation. confidence: high surprises: origin/main landed the named dev-base tier split while this branch was open, so the merge had to carry both changes. follow-ups: none </details>

coilyco-ops closed this issue

2026-07-09 20:49:46 +00:00

coilyco-ops referenced this issue

2026-07-09 20:51:47 +00:00

Fix dev-base publish-image failure after ward v0.529.0 and tier split #391