Repair failed promote run after PR #1391 #1392

New issue

Closed

opened 2026-07-15 10:51:46 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-15 10:51:46 +00:00

Member

Problem

Post-merge promote run 8479 / repository run #2217 failed after PR #1391 merged for issue #1300. Current run evidence:

run 8479 (#2217) failure promote.yml push main "Rehome agent homes under ~/.ward (#1391)"

The PR is already merged and issue #1300 is closed, so this needs its own recovery trail instead of disappearing into the closed issue.

Acceptance

Inspect the failed promote run for PR #1391 / issue #1300.
If the failure is transient, retrigger the supported promote path.
If the failure is real, repair it with a focused change.
Leave final evidence showing promote/release green or the exact remaining blocker.

Related: #1300, #1391, run 8479 / #2217.

## Problem Post-merge promote run 8479 / repository run #2217 failed after PR #1391 merged for issue #1300. Current run evidence: ```text run 8479 (#2217) failure promote.yml push main "Rehome agent homes under ~/.ward (#1391)" ``` The PR is already merged and issue #1300 is closed, so this needs its own recovery trail instead of disappearing into the closed issue. ## Acceptance - Inspect the failed promote run for PR #1391 / issue #1300. - If the failure is transient, retrigger the supported promote path. - If the failure is real, repair it with a focused change. - Leave final evidence showing promote/release green or the exact remaining blocker. Related: #1300, #1391, run 8479 / #2217.

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

2026-07-15 10:51:46 +00:00

coilyco-ops added the

headless

labels

2026-07-15 10:51:46 +00:00

coilyco-ops commented

2026-07-15 10:59:15 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1392 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T10:59:14Z). 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#1392 · branch issue-1392 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1392 · ward v0.710.0 · dispatched 2026-07-15T10:59:08Z
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-1392` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T10:59:14Z). 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#1392` · branch `issue-1392` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1392` · ward `v0.710.0` · dispatched `2026-07-15T10:59:08Z` - **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 10:59:57 +00:00

Author

Member

DISPATCH-DEFERRED: capacity blocked.

Attempted warded engineer coilyco-flight-deck/ward#1392 --harness codex --workflow pull-request-and-merge with the healthy lane's agentic-os:release image override at 2026-07-15T10:59Z. Ward rejected the launch before reservation because it still counted 3 active Ward engineers at the repo limit. No container or reservation was created. This P1 promote-recovery issue remains first for a genuinely free slot.

DISPATCH-DEFERRED: capacity blocked. Attempted `warded engineer coilyco-flight-deck/ward#1392 --harness codex --workflow pull-request-and-merge` with the healthy lane's `agentic-os:release` image override at 2026-07-15T10:59Z. Ward rejected the launch before reservation because it still counted 3 active Ward engineers at the repo limit. No container or reservation was created. This P1 promote-recovery issue remains first for a genuinely free slot.

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

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

fix(release): avoid hard Go download in promote #1399

coilyco-ops closed this issue

2026-07-15 11:09:10 +00:00

coilyco-ops commented

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

Author

Member

QA follow-up on the promote recovery trail. PR #1399 removed the hard Go download blocker, and #1401 then fixed the draft-release creation blocker; promote.yml run 8495 is now green. The remaining public release blocker is downstream release.yml run 8499, job bump-scoop-manifest, where the Scoop updater reads sidecar asset metadata JSON instead of the 64-hex sha256 digest. Active follow-up: #1403, filed with headless/P2 and dispatch-deferred because the repo is at the three-engineer limit.