coilyco-flight-deck/agentic-os

Fork 0

Restore agentic-os-full latest image for warded engineer launches #532

New issue

Closed

opened 2026-07-14 12:03:43 +00:00 by coilyco-ops · 4 comments

coilyco-ops commented

2026-07-14 12:03:43 +00:00

Member

Problem

During the 2026-07-14 director burndown, dispatching coilyco-flight-deck/ward#1281 reached reservation and sibling container creation, then failed before the engineer could launch because the host could not pull or find the dev-base image:

ward agent engineer --harness codex: pulling forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest
ward agent engineer --harness codex: image pull failed (exit status 1); trying the local image
Unable to find image `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest` locally
Error response from daemon: manifest unknown
ward: ward container: create sibling: exit status 1

ward agent dispatch-health then reported stale-prelaunch=1 for ward#1281. This blocks new headless engineers even when issue dispatch and reservation succeed.

Impact

The director cannot continue the requested headless burndown reliably because new sibling engineer containers cannot start without an available agentic-os-full:latest image or an updated launch image reference.

Do

Determine whether the correct fix is publishing the agentic-os-full:latest tag, changing Ward launch configuration to an existing release tag, or restoring the expected moving alias.
Keep the fix public-safe and do not embed host-specific credentials or opaque values.
Make the chosen image reference match the documented dev-base release behavior.
Add or update validation if there is a local check that can catch missing launch image references.

Acceptance

A fresh warded <headless issue> --harness codex can create the sibling container instead of failing with manifest unknown for agentic-os-full:latest.
ward#1281 can be redispatched after the image fix.
The issue or PR notes whether the fix published the tag or changed the launch reference.

## Problem During the 2026-07-14 director burndown, dispatching `coilyco-flight-deck/ward#1281` reached reservation and sibling container creation, then failed before the engineer could launch because the host could not pull or find the dev-base image: ```text ward agent engineer --harness codex: pulling forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest ward agent engineer --harness codex: image pull failed (exit status 1); trying the local image Unable to find image `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest` locally Error response from daemon: manifest unknown ward: ward container: create sibling: exit status 1 ``` `ward agent dispatch-health` then reported `stale-prelaunch=1` for ward#1281. This blocks new headless engineers even when issue dispatch and reservation succeed. ## Impact The director cannot continue the requested headless burndown reliably because new sibling engineer containers cannot start without an available `agentic-os-full:latest` image or an updated launch image reference. ## Do * Determine whether the correct fix is publishing the `agentic-os-full:latest` tag, changing Ward launch configuration to an existing release tag, or restoring the expected moving alias. * Keep the fix public-safe and do not embed host-specific credentials or opaque values. * Make the chosen image reference match the documented dev-base release behavior. * Add or update validation if there is a local check that can catch missing launch image references. ## Acceptance * A fresh `warded <headless issue> --harness codex` can create the sibling container instead of failing with `manifest unknown` for `agentic-os-full:latest`. * ward#1281 can be redispatched after the image fix. * The issue or PR notes whether the fix published the tag or changed the launch reference.

coilyco-ops added the

headless

labels

2026-07-14 12:03:43 +00:00

coilyco-ops commented

2026-07-14 12:03:56 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-agentic-os-532 on host 2954e4865732.

Accepted by ward agent --harness codex (reserved 2026-07-14T12:03:56Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation 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#532 · branch issue-532 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-532 · ward v0.679.0 · dispatched 2026-07-14T12:03:54Z
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.679.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-532` on host `2954e4865732`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T12:03:56Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` 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#532` · branch `issue-532` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-532` · ward `v0.679.0` · dispatched `2026-07-14T12:03:54Z` - **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.679.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-14 12:04:13 +00:00

Author

Member

Director follow-up from 2026-07-14: dispatch was attempted immediately after filing this issue. It reached reservation and sibling container creation for engineer-codex-agentic-os-532, then failed with the same blocker: pull of forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest failed, no local image existed, Docker returned manifest unknown, and ward ended with ward container: create sibling: exit status 1. This issue cannot currently be fixed by a fresh headless engineer because the missing image prevents the engineer container from starting.

Director follow-up from 2026-07-14: dispatch was attempted immediately after filing this issue. It reached reservation and sibling container creation for `engineer-codex-agentic-os-532`, then failed with the same blocker: pull of `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest` failed, no local image existed, Docker returned `manifest unknown`, and ward ended with `ward container: create sibling: exit status 1`. This issue cannot currently be fixed by a fresh headless engineer because the missing image prevents the engineer container from starting.

coilyco-ops commented

2026-07-14 15:24:18 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-agentic-os-532 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-14T15:24:17Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

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

Resolved: coilyco-flight-deck/agentic-os#532 · branch issue-532 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-532 · ward v0.686.0 · dispatched 2026-07-14T15:24:09Z
Comment thread: 1 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-14T12:04:13Z)
- stripped: @coilyco-ops (2026-07-14T12:03:56Z)

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

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-532` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T15:24:17Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` 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#532` · branch `issue-532` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-532` · ward `v0.686.0` · dispatched `2026-07-14T15:24:09Z` - **Comment thread:** 1 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-14T12:04:13Z) - stripped: @coilyco-ops (2026-07-14T12:03:56Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.686.0). </details> </details>  — Codex, via `ward agent`

coilysiren referenced this issue from coilyco-flight-deck/ward

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283

coilyco-ops referenced this issue from a commit

2026-07-14 15:31:37 +00:00

fix(dev-base): restore agentic-os-full latest alias

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-14 15:31:55 +00:00

fix(dev-base): restore agentic-os-full latest alias #533

coilyco-ops closed this issue

2026-07-14 15:38:46 +00:00

coilyco-ops commented

2026-07-14 15:39:21 +00:00

Author

Member

WARDED_WORKFLOW: #533

details

workflow: pull-request-and-merge; review summary: skipped intentionally because the temporary ward default is pending brokered QA retrospective: the fix felt small once the publish path was traced, but the release alias split needed careful wording confidence: high surprise: the doc cap forced a second trim pass follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/533 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped intentionally because the temporary ward default is pending brokered QA retrospective: the fix felt small once the publish path was traced, but the release alias split needed careful wording confidence: high surprise: the doc cap forced a second trim pass follow-ups: none </details>