Fix dev-base core image build failure #592

New issue

Closed

opened 2026-07-15 13:03:56 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 13:03:56 +00:00

Member

The release-side core publish failure is now isolated to the image build step.

Current head:

main and release: 6a7f0f1a27f18e8c3164f994c06975eef88058aa (fix(dev-base): split core publish into visible steps (#590)).

Failure evidence from dev-base-publish.yml run 1439:

plan-draft succeeded.
publish-core failed.
In job publish-core, these steps succeeded: Acquire core publish source, Install uv, Resolve docker host, Derive core publish inputs, Registry login, and Check whether the tier already landed.
Build core image failed after 15m19s.
Verify published core image and Probe core buildcache write then failed/skipped as downstream failure.
All downstream tier jobs stayed blocked.

The active blocker is no longer promote, registry login, source acquisition, or release retagging. It is the core Docker image build itself. The engineer should fix the core image build path, or make the build step reveal a precise external wall if it cannot be fixed from the repo. Look for timeout/resource limits, build context size, Dockerfile behavior, missing cache use, and whether the core tier can be built incrementally or with smaller context.

Acceptance:

A PR changes the core image build path so Build core image can complete, or makes its terminal failure exact enough to hand to ops.
PR CI is green.
After merge, dev-base-publish.yml reaches past Build core image on release, or the issue names the precise non-repo wall.

The release-side core publish failure is now isolated to the image build step. Current head: * `main` and `release`: `6a7f0f1a27f18e8c3164f994c06975eef88058aa` (`fix(dev-base): split core publish into visible steps (#590)`). Failure evidence from `dev-base-publish.yml` run `1439`: * `plan-draft` succeeded. * `publish-core` failed. * In job `publish-core`, these steps succeeded: `Acquire core publish source`, `Install uv`, `Resolve docker host`, `Derive core publish inputs`, `Registry login`, and `Check whether the tier already landed`. * `Build core image` failed after 15m19s. * `Verify published core image` and `Probe core buildcache write` then failed/skipped as downstream failure. * All downstream tier jobs stayed blocked. The active blocker is no longer promote, registry login, source acquisition, or release retagging. It is the core Docker image build itself. The engineer should fix the core image build path, or make the build step reveal a precise external wall if it cannot be fixed from the repo. Look for timeout/resource limits, build context size, Dockerfile behavior, missing cache use, and whether the core tier can be built incrementally or with smaller context. Acceptance: * A PR changes the core image build path so `Build core image` can complete, or makes its terminal failure exact enough to hand to ops. * PR CI is green. * After merge, `dev-base-publish.yml` reaches past `Build core image` on `release`, or the issue names the precise non-repo wall.

coilyco-ops commented

2026-07-15 13:04:22 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T13:04:21Z). 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#592 · branch issue-592 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-592 · ward v0.697.0 · dispatched 2026-07-15T13:04:14Z
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.697.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-592` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T13:04:21Z). 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#592` · branch `issue-592` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-592` · ward `v0.697.0` · dispatched `2026-07-15T13:04:14Z` - **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.697.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-15 13:12:07 +00:00

fix(dev-base): shrink tier build contexts #593

coilyco-ops commented

2026-07-15 13:14:56 +00:00

Author

Member

WARDED_WORKFLOW: #593

details

workflow: pull-request-and-merge; review summary: skipped, intentionally skipped because the temporary ward default still has pending brokered QA.

Retrospective: the fix settled cleanly once the build-context wiring was traced through the shared plan helper.

Confidence: high.

Surprises: the blocker was the oversized context path, not the Dockerfile body.

Follow-ups: merge the PR, then recheck the release-side publish path on release.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/593 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped, intentionally skipped because the temporary ward default still has pending brokered QA. Retrospective: the fix settled cleanly once the build-context wiring was traced through the shared plan helper. Confidence: high. Surprises: the blocker was the oversized context path, not the Dockerfile body. Follow-ups: merge the PR, then recheck the release-side publish path on `release`. </details>

coilyco-ops closed this issue

2026-07-15 13:15:40 +00:00

coilyco-ops referenced this issue

2026-07-15 13:16:27 +00:00

Repair the isolated dev-base core image build failure #591