Repair failed promote run after PR #1448 #1454

New issue

Closed

opened 2026-07-15 13:42:53 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-15 13:42:53 +00:00

Member

Problem

Post-merge promote run 8610 / repository run #2303 failed after PR #1448 merged for #1301. Current run evidence:

run 8610 (#2303) failure promote.yml push main "Include director runs in issue log drains (#1448)"

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

Acceptance

Inspect promote run 8610 / repository run #2303 after PR #1448.
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 document the exact remaining blocker.

Related: #1301, #1448, run 8610 / #2303.

## Problem Post-merge promote run 8610 / repository run #2303 failed after PR #1448 merged for #1301. Current run evidence: ```text run 8610 (#2303) failure promote.yml push main "Include director runs in issue log drains (#1448)" ``` PR #1448 is already merged and #1301 is closed, so this needs its own recovery trail instead of disappearing into the closed issue. ## Acceptance - Inspect promote run 8610 / repository run #2303 after PR #1448. - 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 document the exact remaining blocker. Related: #1301, #1448, run 8610 / #2303.

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

2026-07-15 13:42:53 +00:00

coilyco-ops added the

headless

labels

2026-07-15 13:42:53 +00:00

coilyco-ops commented

2026-07-15 13:43:25 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T13:43:24Z). 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#1454 · branch issue-1454 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1454 · ward v0.710.0 · dispatched 2026-07-15T13:43:17Z
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-1454` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T13:43:24Z). 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#1454` · branch `issue-1454` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1454` · ward `v0.710.0` · dispatched `2026-07-15T13:43:17Z` - **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 referenced this issue from a pull request that will close it,

2026-07-15 13:51:48 +00:00

Repair failed promote run after PR #1448 #1458

coilyco-ops referenced this issue

2026-07-15 13:53:06 +00:00

Replace retry-only ward:release publish repair with daemon-independent aliasing #1459

coilyco-ops closed this issue

2026-07-15 13:55:10 +00:00

coilyco-ops commented

2026-07-15 13:55:11 +00:00

Author

Member

Superseded by #1459. PR #1458 was closed unmerged because retrying Docker commands does not address the observed missing Docker daemon in promote run 8610 / UI run #2303. #1459 is filed and dispatched for the daemon-independent alias publish repair; leaving this issue open would duplicate that active repair trail.