coilyco-flight-deck/agentic-os

Watch

Harden dev-base publish cache visibility and determinism #594

New issue

Closed

opened 2026-07-15 13:18:02 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 13:18:02 +00:00

Owner

Context

During the July 15 release recovery, the dev-base publish chain repeatedly made it hard to tell whether a failure came from a true Dockerfile problem, a cold or missing cache, or registry/cache plumbing. Kai called out missing caches as one of the likely contributors.

Requested work

Audit the dev-base publish workflows and composite actions for cache import/export coverage across core, lang-node, lang-go, lang-dotnet, ops, agent, and full tiers.
Make cache keys, cache sources, and cache destinations explicit in the workflow or action summaries that already exist.
Add a cheap cache availability/provenance check before expensive builds where the information is available without depending on live cluster state.
Keep this focused on cache determinism and release debuggability. Do not add broad summarize-publish work.

Acceptance

A future dev-base publish run shows which cache path each tier attempted to read and write.
A cache miss is distinguishable from a build failure without scraping raw logs.
The change is covered by the repo's normal validation path.

Context During the July 15 release recovery, the dev-base publish chain repeatedly made it hard to tell whether a failure came from a true Dockerfile problem, a cold or missing cache, or registry/cache plumbing. Kai called out missing caches as one of the likely contributors. Requested work * Audit the dev-base publish workflows and composite actions for cache import/export coverage across core, lang-node, lang-go, lang-dotnet, ops, agent, and full tiers. * Make cache keys, cache sources, and cache destinations explicit in the workflow or action summaries that already exist. * Add a cheap cache availability/provenance check before expensive builds where the information is available without depending on live cluster state. * Keep this focused on cache determinism and release debuggability. Do not add broad summarize-publish work. Acceptance * A future dev-base publish run shows which cache path each tier attempted to read and write. * A cache miss is distinguishable from a build failure without scraping raw logs. * The change is covered by the repo's normal validation path.

coilyco-ops commented

2026-07-15 13:18:20 +00:00

Author

Owner

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T13:18:20Z). 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#594 · branch issue-594 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-594 · ward v0.697.0 · dispatched 2026-07-15T13:18:16Z
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-594` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T13:18:20Z). 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#594` · branch `issue-594` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-594` · ward `v0.697.0` · dispatched `2026-07-15T13:18:16Z` - **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:27:13 +00:00

Harden dev-base publish cache visibility and determinism #597

coilyco-ops commented

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

Author

Owner

WARDED_WORKFLOW: #597

details

workflow: pull-request-and-merge; review summary: skipped, in-container review gate intentionally skipped because the temporary ward default pending brokered QA
implementation felt straightforward once the shared cache helper carried the breadcrumbing for every tier.
confidence: high
surprises: the handwritten core publish step was still bypassing the helper.
follow-ups: none

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/597 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped, in-container review gate intentionally skipped because the temporary ward default pending brokered QA implementation felt straightforward once the shared cache helper carried the breadcrumbing for every tier. confidence: high surprises: the handwritten core publish step was still bypassing the helper. follow-ups: none </details>

coilyco-ops closed this issue

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

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#594

No description provided.

Rows
Columns