Recover promote failure after dispatch partial-launch fix #1363

New issue

Closed

opened 2026-07-15 09:18:03 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-15 09:18:03 +00:00

Member

Ward main promotion failed immediately after the milestone repair from PR #1362 landed.

Evidence:

PR #1362 (Surface partial-launch after reservation post failure) passed test.yml on head 7d62b0475d8e886708eb4e555a70e4741cfa8d1d and merged.
The exact merged main SHA is 7d62b0475d8e886708eb4e555a70e4741cfa8d1d.
Push-triggered promote.yml action run 8397 (repository run #2165) failed after 5m01s.
The run API reports status failure, event push, branch main, and no approval requirement.
ward agent pr rerun coilyco-flight-deck/ward 8397 cannot retrigger it because this Forgejo exposes no Actions rerun endpoint.
The preceding main promote/release pair for PR #1361 succeeded, so this is specific to the new main head or a newly surfaced transient.

Diagnose the failed promote gate for exact main SHA 7d62b04, repair any reproducible failure, and get a successful promote/release path for the fixed head. If the failure is transient and the code needs no change, use the smallest auditable main update or supported workflow dispatch needed to retrigger and record the green run evidence.

Acceptance:

The failure point in promote run 8397 is identified.
Any code or workflow regression is covered by a focused test.
Required PR checks are green for a repair change.
A promote run succeeds for the repaired or intentionally retriggered main head.
The issue thread records the successful run and resulting release state.

Ward main promotion failed immediately after the milestone repair from PR #1362 landed. Evidence: * PR #1362 (`Surface partial-launch after reservation post failure`) passed `test.yml` on head `7d62b0475d8e886708eb4e555a70e4741cfa8d1d` and merged. * The exact merged main SHA is `7d62b0475d8e886708eb4e555a70e4741cfa8d1d`. * Push-triggered `promote.yml` action run 8397 (repository run #2165) failed after 5m01s. * The run API reports status `failure`, event `push`, branch `main`, and no approval requirement. * `ward agent pr rerun coilyco-flight-deck/ward 8397` cannot retrigger it because this Forgejo exposes no Actions rerun endpoint. * The preceding main promote/release pair for PR #1361 succeeded, so this is specific to the new main head or a newly surfaced transient. Diagnose the failed promote gate for exact main SHA `7d62b04`, repair any reproducible failure, and get a successful promote/release path for the fixed head. If the failure is transient and the code needs no change, use the smallest auditable main update or supported workflow dispatch needed to retrigger and record the green run evidence. Acceptance: * The failure point in promote run 8397 is identified. * Any code or workflow regression is covered by a focused test. * Required PR checks are green for a repair change. * A promote run succeeds for the repaired or intentionally retriggered main head. * The issue thread records the successful run and resulting release state.

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 09:18:03 +00:00

coilyco-ops added the

coherence-core

headless

labels

2026-07-15 09:18:03 +00:00

coilyco-ops commented

2026-07-15 09:18:18 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1363 on host 74a70515a491.

Accepted by ward agent --harness codex (reserved 2026-07-15T09:18:18Z). 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/ward#1363 · branch issue-1363 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1363 · ward v0.710.0 · dispatched 2026-07-15T09:18:15Z
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.710.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1363` on host `74a70515a491`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T09:18:18Z). 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/ward#1363` · branch `issue-1363` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1363` · ward `v0.710.0` · dispatched `2026-07-15T09:18:15Z` - **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.710.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-15 09:18:43 +00:00

Author

Member

WARDED_WORKFLOW: dispatch-deferred

launch failure details

The repair run never started. warded engineer coilyco-flight-deck/ward#1363 --harness codex --workflow pull-request-and-merge failed before container creation because forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest was unavailable remotely and no local image existed. Docker has no engineer-codex-ward-1363 container. No implementation work was performed.

The reservation is released for redispatch from a fresh director. Issue #1363 remains the concrete headless repair for failed promote run 8397 on main SHA 7d62b0475d8e886708eb4e555a70e4741cfa8d1d.

Codex, via ward agent

WARDED_WORKFLOW: dispatch-deferred <details><summary>launch failure details</summary> The repair run never started. `warded engineer coilyco-flight-deck/ward#1363 --harness codex --workflow pull-request-and-merge` failed before container creation because `forgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latest` was unavailable remotely and no local image existed. Docker has no `engineer-codex-ward-1363` container. No implementation work was performed. The reservation is released for redispatch from a fresh director. Issue #1363 remains the concrete headless repair for failed promote run 8397 on main SHA `7d62b0475d8e886708eb4e555a70e4741cfa8d1d`. </details>  - Codex, via `ward agent`

coilyco-ops commented

2026-07-15 09:19:19 +00:00

Author

Member

Duplicate of #1364, which has an active healthy reservation for the same failed promote run 8397. Closing this unstarted issue so the repair has one canonical thread. The failed local launch on #1363 performed no implementation work and its reservation was already released.

coilyco-ops closed this issue

2026-07-15 09:19:20 +00:00