Run ward doctor during dev-base Docker build #408

New issue

Closed

opened 2026-07-10 04:43:14 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 04:43:14 +00:00

Member

Run ward doctor during the dev-base Docker build so bad ward runtime config fails the image publish instead of surfacing later in containers.

Dependency:

Requires coilyco-flight-deck/ward#940 to land and release a ward version that includes ward doctor.

Current aos context:

docker/dev-base/core/Dockerfile builds ward in the dev-base-ward-builder stage.
That stage sets WARD_CONFIG_REF=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os@main//.ward before cloning/building ward.
The final core stage copies /usr/local/bin/ward and currently runs ward --version only.
The aos .ward bundle is the source of truth for the coilyco ward config per docs/ward-specs.md.

Scope:

After the built ward binary exists, run ward doctor in the Docker build against the same WARD_CONFIG_REF that runtime ward commands will use.
Ensure the env is present in whichever stage invokes ward doctor. If the final dev-base-core stage runs it, carry WARD_CONFIG_REF=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os@main//.ward there too.
Bump WARD_VERSION to the first ward release that includes ward doctor.
Keep the check in the core tier, since every other dev-base tier inherits ward from core.
Update docs if the dev-base image doc or ward-specs doc should mention that image publish now gates on ward doctor.
Add/adjust tests if there is existing Dockerfile or pin coverage for the ward build block.

Acceptance:

The Dockerfile runs ward doctor during build and fails the build on a non-zero doctor result.
The command validates the aos .ward bundle, not the neutral embedded example config.
WARD_VERSION points at a ward release containing the command.
Relevant repo validation passes.

If ward#940 has not landed/released when this issue is picked up, post a blocked outcome naming the missing ward release rather than substituting another command.

Run `ward doctor` during the dev-base Docker build so bad ward runtime config fails the image publish instead of surfacing later in containers. Dependency: * Requires coilyco-flight-deck/ward#940 to land and release a ward version that includes `ward doctor`. Current aos context: * `docker/dev-base/core/Dockerfile` builds ward in the `dev-base-ward-builder` stage. * That stage sets `WARD_CONFIG_REF=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os@main//.ward` before cloning/building ward. * The final core stage copies `/usr/local/bin/ward` and currently runs `ward --version` only. * The aos `.ward` bundle is the source of truth for the coilyco ward config per `docs/ward-specs.md`. Scope: * After the built ward binary exists, run `ward doctor` in the Docker build against the same `WARD_CONFIG_REF` that runtime ward commands will use. * Ensure the env is present in whichever stage invokes `ward doctor`. If the final `dev-base-core` stage runs it, carry `WARD_CONFIG_REF=forgejo.coilysiren.me/coilyco-flight-deck/agentic-os@main//.ward` there too. * Bump `WARD_VERSION` to the first ward release that includes `ward doctor`. * Keep the check in the core tier, since every other dev-base tier inherits ward from core. * Update docs if the dev-base image doc or ward-specs doc should mention that image publish now gates on `ward doctor`. * Add/adjust tests if there is existing Dockerfile or pin coverage for the ward build block. Acceptance: * The Dockerfile runs `ward doctor` during build and fails the build on a non-zero doctor result. * The command validates the aos `.ward` bundle, not the neutral embedded example config. * `WARD_VERSION` points at a ward release containing the command. * Relevant repo validation passes. If ward#940 has not landed/released when this issue is picked up, post a blocked outcome naming the missing ward release rather than substituting another command.

coilyco-ops commented

2026-07-10 04:43:47 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-10T04:43:46Z). 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#408 · branch issue-408 · harness codex · workflow direct-main
Run: engineer-codex-agentic-os-408 · ward v0.555.0 · dispatched 2026-07-10T04:43:46Z
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.555.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-agentic-os-408` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T04:43:46Z). 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#408` · branch `issue-408` · harness `codex` · workflow `direct-main` - **Run:** `engineer-codex-agentic-os-408` · ward `v0.555.0` · dispatched `2026-07-10T04:43:46Z` - **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.555.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 04:48:23 +00:00

Author

Member

WARD-OUTCOME: blocked 🛑

details

workflow: blocked; review summary: review gate skipped by ~/.ward/config.yaml default
retrospective: the build path stayed unchanged because the ward release line available here no longer ships doctor
confidence: high
surprises: v0.557.0 has no cmd/ward/doctor.go
follow-ups: wait for the ward release from #940 that restores ward doctor

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: blocked; review summary: review gate skipped by ~/.ward/config.yaml default retrospective: the build path stayed unchanged because the ward release line available here no longer ships `doctor` confidence: high surprises: v0.557.0 has no `cmd/ward/doctor.go` follow-ups: wait for the ward release from #940 that restores `ward doctor` </details>

coilyco-ops referenced this issue from a commit

2026-07-10 07:32:29 +00:00

Run ward doctor in dev-base build

coilyco-ops closed this issue

2026-07-10 07:32:29 +00:00

coilyco-ops referenced this issue from a commit

2026-07-10 07:47:02 +00:00

Fix dev-base ward doctor under buildx