Promote failed after non-empty release retrigger PR 560 #562

New issue

Closed

opened 2026-07-15 06:41:46 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 06:41:46 +00:00

Member

Problem

The non-empty retrigger PR #560 merged successfully, but the follow-on promote workflow failed instead of advancing release.

Evidence from the 2026-07-15 director heartbeat:

PR #560 merged at 2026-07-15T06:31:51Z as 802b77ddc7735a44899c28dcc6860b3821aeef88.
Main ci.yml push run #1371 succeeded.
mirror-to-github.yml push run #1372 succeeded.
promote.yml push run #1373 failed. Native run id: 8309.
Run URL: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/1373
Run metadata: workflow promote.yml, event push, ref main, commit 802b77ddc7735a44899c28dcc6860b3821aeef88, started 2026-07-15T06:32:40Z, stopped 2026-07-15T06:40:28Z.

Task

Diagnose and fix the failed promote path so release advances from the merged #560 main commit under the normal promote-only contract.

Acceptance criteria

Root cause of run #1373 / id 8309 is identified in the issue or PR.
Fix lands through a normal PR, if code/config changes are needed.
Main promote rerun or follow-up promote succeeds.
Release advancement evidence is left on this issue.
No direct push to main or release.

## Problem The non-empty retrigger PR #560 merged successfully, but the follow-on promote workflow failed instead of advancing release. Evidence from the 2026-07-15 director heartbeat: * PR #560 merged at 2026-07-15T06:31:51Z as `802b77ddc7735a44899c28dcc6860b3821aeef88`. * Main `ci.yml` push run #1371 succeeded. * `mirror-to-github.yml` push run #1372 succeeded. * `promote.yml` push run #1373 failed. Native run id: `8309`. * Run URL: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/1373 * Run metadata: workflow `promote.yml`, event `push`, ref `main`, commit `802b77ddc7735a44899c28dcc6860b3821aeef88`, started 2026-07-15T06:32:40Z, stopped 2026-07-15T06:40:28Z. ## Task Diagnose and fix the failed promote path so `release` advances from the merged #560 main commit under the normal promote-only contract. ## Acceptance criteria * Root cause of run #1373 / id 8309 is identified in the issue or PR. * Fix lands through a normal PR, if code/config changes are needed. * Main promote rerun or follow-up promote succeeds. * Release advancement evidence is left on this issue. * No direct push to `main` or `release`.

coilyco-ops commented

2026-07-15 06:42:20 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T06:42: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#562 · branch issue-562 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-562 · ward v0.697.0 · dispatched 2026-07-15T06:42:09Z
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-562` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T06:42: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#562` · branch `issue-562` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-562` · ward `v0.697.0` · dispatched `2026-07-15T06:42:09Z` - **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 commented

2026-07-15 06:43:43 +00:00

Author

Member

Duplicate of #561. Issue #561 was already filed with the same promote.yml #1373 failure evidence and has an active engineer. Closing this duplicate and stopping its duplicate dispatch so the repair work stays on #561.