coilyco-flight-deck/agentic-os

Watch

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

New issue

Closed

opened 2026-07-09 20:51:47 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

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

Member

Problem

The AOS ward bump and tier split landed on main, but the latest release workflow did not publish the new dev-base image.

Run: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/798/jobs/1/attempt/1

Observed from Forgejo task metadata on 2026-07-09:

workflow: release.yml
run number: 798
commit: c96ad11c1f2df765b35446052933d6523d007a12 (merge origin/main)
plan-release: success
publish-image: failure, duration 2m40s
failed step: Build and push (multi-arch), duration 2m15s
release: skipped

The last known successful publish-image run was run 792 on commit 0dfafea79299afeea248eb9fb59934c209026fe2, before the Linuxbrew fix, named dev-base target split, and ward v0.529.0 bump.

Scope

Read the full run 798 publish-image log from Forgejo and identify the exact failing command.
Fix the dev-base Dockerfile or release workflow regression that prevents publish.
Keep the ward bump to v0.529.0; do not roll back to the stale v0.396.0 pin unless a ward upstream regression is proven and a newer safe tag is unavailable.
Preserve the named target split from #385 unless the failure proves it needs a targeted correction.
Ensure release.yml publishes the intended default/full dev-base image and only tags it after verification.

Acceptance

A new publish-image run succeeds on main.
The release job is not skipped because of publish-image failure.
The published dev-base image contains ward v0.529.0 or a newer tag with WARD_CONFIG_REF support.
Any follow-up for long-term tier fan-out remains on #386/#387/#388 rather than being bundled here.

Notes

#383, #385, and #390 are closed. This issue is the remaining publication blocker for getting the custom AOS ward config path into the usable dev-base image.

## Problem The AOS ward bump and tier split landed on `main`, but the latest release workflow did not publish the new dev-base image. Run: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/798/jobs/1/attempt/1 Observed from Forgejo task metadata on 2026-07-09: * workflow: `release.yml` * run number: `798` * commit: `c96ad11c1f2df765b35446052933d6523d007a12` (`merge origin/main`) * `plan-release`: success * `publish-image`: failure, duration 2m40s * failed step: `Build and push (multi-arch)`, duration 2m15s * `release`: skipped The last known successful publish-image run was run 792 on commit `0dfafea79299afeea248eb9fb59934c209026fe2`, before the Linuxbrew fix, named dev-base target split, and ward `v0.529.0` bump. ## Scope * Read the full run 798 `publish-image` log from Forgejo and identify the exact failing command. * Fix the dev-base Dockerfile or release workflow regression that prevents publish. * Keep the ward bump to `v0.529.0`; do not roll back to the stale `v0.396.0` pin unless a ward upstream regression is proven and a newer safe tag is unavailable. * Preserve the named target split from #385 unless the failure proves it needs a targeted correction. * Ensure release.yml publishes the intended default/full dev-base image and only tags it after verification. ## Acceptance * A new `publish-image` run succeeds on `main`. * The release job is not skipped because of `publish-image` failure. * The published dev-base image contains `ward v0.529.0` or a newer tag with `WARD_CONFIG_REF` support. * Any follow-up for long-term tier fan-out remains on #386/#387/#388 rather than being bundled here. ## Notes #383, #385, and #390 are closed. This issue is the remaining publication blocker for getting the custom AOS ward config path into the usable dev-base image.

coilyco-ops commented

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

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T20:51:52Z). 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#391 · branch issue-391 · harness codex · workflow direct-to-main
Run: engineer-codex-agentic-os-391 · ward v0.493.0 · dispatched 2026-07-09T20:51:52Z
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-391` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T20:51:52Z). 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#391` · branch `issue-391` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-agentic-os-391` · ward `v0.493.0` · dispatched `2026-07-09T20:51:52Z` - **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 referenced this issue from a commit

2026-07-09 20:56:16 +00:00

fix(dev-base): install passwd for Linuxbrew useradd

coilyco-ops closed this issue

2026-07-09 20:56:16 +00:00

coilyco-ops referenced this issue from a commit

2026-07-09 20:59:18 +00:00

fix(dev-base): use sbin path for Linuxbrew setup

coilyco-ops referenced this issue from a commit

2026-07-09 21:00:45 +00:00

fix(dev-base): re-declare UV_VERSION in core stage

coilyco-ops commented

2026-07-09 21:15:55 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: release.yml; review summary: skipped by ~/.ward/config.yaml default
felt like a split-scope regression, then a PATH miss, then the release path settled cleanly.
confidence: high
surprises: Homebrew needed explicit /usr/sbin paths, then dev-base-core needed UV_VERSION re-declared.
follow-ups: none

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: release.yml; review summary: skipped by ~/.ward/config.yaml default felt like a split-scope regression, then a PATH miss, then the release path settled cleanly. confidence: high surprises: Homebrew needed explicit /usr/sbin paths, then dev-base-core needed UV_VERSION re-declared. follow-ups: none </details>

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#391

No description provided.

Rows
Columns