Make publish-core failure actionable after bound clone fix #584

New issue

Closed

opened 2026-07-15 11:04:32 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 11:04:32 +00:00

Member

The release path is still blocked after #582.

Current head:

main and release: 81cdc64dc05283f4b2d55e65b33093c0edf3df28 (fix(dev-base): bound ward source clone in core publish (#582)).
Promote run 1422 succeeded and moved release to this head.

Failure evidence:

Auto-triggered dev-base-publish.yml run 1423 failed before publish work: publish-core failed in Set up job after 1m22s. A manual dispatch was used because that was a runner/setup failure.
Manual dev-base-publish.yml run 1424 cleared setup, ran publish-core, and still failed.
In run 1424, plan-draft succeeded.
publish-core failed.
publish-lang-node, publish-lang-go, publish-lang-dotnet, publish-ops, publish-agent, and publish-full stayed blocked.
In publish-core job index 1, ./actions/publish-dev-base-tier failed after 21m16s.

The previous fixes improved promote and retag ordering, and #582 bounded the ward source clone, but the core tier still fails opaquely in the release-side publish action. The raw Forgejo log helper remains unavailable from the director surface, so the engineer should make this specific core-tier failure actionable and fix it if the repo-side cause is clear.

Acceptance:

A PR either fixes the publish-core failure or adds narrow, release-actionable observability around ./actions/publish-dev-base-tier for the core tier.
Do not broaden into generic diagnostic-message churn. Keep it targeted to the dev-base core publish path.
PR CI is green.
After merge, the director can run or observe dev-base-publish.yml and know whether the core publish passed or the exact external wall that needs operator action.

Related: #581/#582.

The release path is still blocked after #582. Current head: * `main` and `release`: `81cdc64dc05283f4b2d55e65b33093c0edf3df28` (`fix(dev-base): bound ward source clone in core publish (#582)`). * Promote run `1422` succeeded and moved `release` to this head. Failure evidence: * Auto-triggered `dev-base-publish.yml` run `1423` failed before publish work: `publish-core` failed in `Set up job` after 1m22s. A manual dispatch was used because that was a runner/setup failure. * Manual `dev-base-publish.yml` run `1424` cleared setup, ran `publish-core`, and still failed. * In run `1424`, `plan-draft` succeeded. * `publish-core` failed. * `publish-lang-node`, `publish-lang-go`, `publish-lang-dotnet`, `publish-ops`, `publish-agent`, and `publish-full` stayed blocked. * In `publish-core` job index 1, `./actions/publish-dev-base-tier` failed after 21m16s. The previous fixes improved promote and retag ordering, and #582 bounded the ward source clone, but the core tier still fails opaquely in the release-side publish action. The raw Forgejo log helper remains unavailable from the director surface, so the engineer should make this specific core-tier failure actionable and fix it if the repo-side cause is clear. Acceptance: * A PR either fixes the `publish-core` failure or adds narrow, release-actionable observability around `./actions/publish-dev-base-tier` for the core tier. * Do not broaden into generic diagnostic-message churn. Keep it targeted to the dev-base core publish path. * PR CI is green. * After merge, the director can run or observe `dev-base-publish.yml` and know whether the core publish passed or the exact external wall that needs operator action. Related: #581/#582.

coilyco-ops commented

2026-07-15 11:04:54 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T11:04:54Z). 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#584 · branch issue-584 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-584 · ward v0.697.0 · dispatched 2026-07-15T11:04:47Z
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-584` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T11:04:54Z). 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#584` · branch `issue-584` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-584` · ward `v0.697.0` · dispatched `2026-07-15T11:04:47Z` - **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 11:11:14 +00:00

fix(dev-base): add core publish breadcrumbs #585

coilyco-ops closed this issue

2026-07-15 11:16:11 +00:00

coilyco-ops commented

2026-07-15 11:19:08 +00:00

Author

Member

WARDED_WORKFLOW: #585

details

workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA.
Implementation felt narrow and mechanical. Confidence: medium-high. Surprise: the release-side breadcrumb needed more value than a code fix. Follow-up: none unless the next release run shows a different external wall.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/585 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA. Implementation felt narrow and mechanical. Confidence: medium-high. Surprise: the release-side breadcrumb needed more value than a code fix. Follow-up: none unless the next release run shows a different external wall. </details>