coilyco-flight-deck/agentic-os

Fork 0

Retrigger agentic-os main promote after cancelled fixed-flow run #553

New issue

Open

opened 2026-07-15 05:37:13 +00:00 by coilyco-ops · 5 comments

coilyco-ops commented

2026-07-15 05:37:13 +00:00

Member

The release-flow fix from PR 552 landed on main, but the exact-head promote run was cancelled and the release branch did not advance.

Evidence:

main: 7f61a25470c34587bf240acd0fe065f065a99d8d, fix(release): publish before release branch fast-forward (#552)
release: 24980330c233d1338be428a16a0a2750f24a3749, still the old failed release head
Exact-head runs for main 7f61a254...:
- 1350, ci.yml, success
- 1351, mirror-to-github.yml, success
- 1352, promote.yml, cancelled
Internal run id for the cancelled promote is 8247.
ward agent pr rerun coilyco-flight-deck/agentic-os 8247 cannot work because this Forgejo lacks the Actions rerun API.

Please retrigger the current main head with the smallest acceptable push, then let promote advance release and leave final run evidence. This is a read-only director surface, so the director cannot push the empty/no-op commit directly.

The release-flow fix from PR 552 landed on `main`, but the exact-head promote run was cancelled and the `release` branch did not advance. Evidence: * `main`: `7f61a25470c34587bf240acd0fe065f065a99d8d`, `fix(release): publish before release branch fast-forward (#552)` * `release`: `24980330c233d1338be428a16a0a2750f24a3749`, still the old failed release head * Exact-head runs for `main` `7f61a254...`: * `1350`, `ci.yml`, `success` * `1351`, `mirror-to-github.yml`, `success` * `1352`, `promote.yml`, `cancelled` * Internal run id for the cancelled promote is `8247`. * `ward agent pr rerun coilyco-flight-deck/agentic-os 8247` cannot work because this Forgejo lacks the Actions rerun API. Please retrigger the current `main` head with the smallest acceptable push, then let promote advance `release` and leave final run evidence. This is a read-only director surface, so the director cannot push the empty/no-op commit directly.

coilyco-ops commented

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

Author

Member

Update from director surface on 2026-07-15T05:59Z: the current main head is efb9e76341 and release remains at 24980330c2. Main exact-head runs: ci.yml 1363 success, mirror-to-github.yml 1364 success, promote.yml 1365 still running. Run 1365 was created 2026-07-15T05:44:02Z, started 05:45:48Z, and its detail record last updated 05:47:26Z while release did not advance. Please diagnose why promote is not completing the release fast-forward, repair the workflow or repo state, and get main => release green under the promote-only contract.

Update from director surface on 2026-07-15T05:59Z: the current main head is efb9e76341345089027c5b693ded2c3ee073f73e and release remains at 24980330c233d1338be428a16a0a2750f24a3749. Main exact-head runs: ci.yml 1363 success, mirror-to-github.yml 1364 success, promote.yml 1365 still running. Run 1365 was created 2026-07-15T05:44:02Z, started 05:45:48Z, and its detail record last updated 05:47:26Z while release did not advance. Please diagnose why promote is not completing the release fast-forward, repair the workflow or repo state, and get main => release green under the promote-only contract.

coilyco-ops commented

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

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T06:01: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#553 · branch issue-553 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-agentic-os-553 · ward v0.697.0 · dispatched 2026-07-15T06:00:56Z
Comment thread: 1 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-15T06:00:34Z)

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-553` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T06:01: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#553` · branch `issue-553` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-553` · ward `v0.697.0` · dispatched `2026-07-15T06:00:56Z` - **Comment thread:** 1 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-15T06:00:34Z) 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 commit

2026-07-15 06:05:03 +00:00

chore: retrigger promote for release advance (#553)

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

2026-07-15 06:05:17 +00:00

chore: retrigger promote for release advance #555

coilyco-ops commented

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

Author

Member

WARDED_WORKFLOW: #555

details

workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA intentionally skipped the in-container review gate

felt: straightforward, with one shell-quoting slip while drafting the PR body
confidence: high
surprises: Forgejo only enqueued the pull_request checks until merge, so the retrigger path stopped at PR green
follow-ups: merge PR #555 to let the main push trigger promote and advance release

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/555 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped because the temporary ward default pending brokered QA intentionally skipped the in-container review gate felt: straightforward, with one shell-quoting slip while drafting the PR body confidence: high surprises: Forgejo only enqueued the pull_request checks until merge, so the retrigger path stopped at PR green follow-ups: merge PR #555 to let the main push trigger promote and advance release </details>

coilyco-ops referenced this issue

2026-07-15 06:11:24 +00:00

Unblock green PR 555 stuck on Forgejo merge 500 #556

coilyco-ops referenced this issue from a commit

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

chore: retrigger promote for release advance

coilyco-ops commented

2026-07-15 06:18:08 +00:00

Author

Member

Update from director surface on 2026-07-15T06:17Z: promote run 1365 for main head efb9e76341 is now terminal failure, stopped 2026-07-15T06:14:39Z. ci.yml 1363 and mirror-to-github.yml 1364 are still success, but release remains at 24980330c2, so agentic-os release is still red and behind. PR 555 exists as the retrigger path, and issue 556 is tracking the Forgejo merge 500 on that empty-diff PR.

Update from director surface on 2026-07-15T06:17Z: promote run 1365 for main head efb9e76341345089027c5b693ded2c3ee073f73e is now terminal failure, stopped 2026-07-15T06:14:39Z. ci.yml 1363 and mirror-to-github.yml 1364 are still success, but release remains at 24980330c233d1338be428a16a0a2750f24a3749, so agentic-os release is still red and behind. PR 555 exists as the retrigger path, and issue 556 is tracking the Forgejo merge 500 on that empty-diff PR.

coilyco-ops referenced this issue

2026-07-15 06:19:26 +00:00

Use a non-empty retrigger PR because empty-diff PRs hit Forgejo merge 500 #558

coilyco-ops commented

2026-07-15 06:40:59 +00:00

Author

Member

Update from director surface on 2026-07-15T06:40Z: the non-empty retrigger PR 560 merged and moved main to 802b77ddc7. Exact-head runs: ci.yml 1371 success, mirror-to-github.yml 1372 success, promote.yml 1373 failure at 2026-07-15T06:40:28Z. Release remains at 24980330c2 with old release.yml 1277 failure. So the issue is no longer just retriggering or empty-diff merge 500: current promote itself is failing after the real-change retrigger.

Update from director surface on 2026-07-15T06:40Z: the non-empty retrigger PR 560 merged and moved main to 802b77ddc7735a44899c28dcc6860b3821aeef88. Exact-head runs: ci.yml 1371 success, mirror-to-github.yml 1372 success, promote.yml 1373 failure at 2026-07-15T06:40:28Z. Release remains at 24980330c233d1338be428a16a0a2750f24a3749 with old release.yml 1277 failure. So the issue is no longer just retriggering or empty-diff merge 500: current promote itself is failing after the real-change retrigger.