Repair failed promote run after PR #1407 #1422

New issue

Closed

opened 2026-07-15 12:08:20 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-15 12:08:20 +00:00

Member

Problem

Post-merge promote run 8528 / repository run #2250 failed after PR #1407 merged for issue #1335. Current run evidence:

run 8528 (#2250) failure promote.yml push main "Inject pre-flight launch logs into the launched agent context (#1407)"

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

Acceptance

Inspect the failed promote run for PR #1407 / issue #1335.
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: #1335, #1407, run 8528 / #2250.

## Problem Post-merge promote run 8528 / repository run #2250 failed after PR #1407 merged for issue #1335. Current run evidence: ```text run 8528 (#2250) failure promote.yml push main "Inject pre-flight launch logs into the launched agent context (#1407)" ``` PR #1407 is already merged and issue #1335 is closed, so this needs its own recovery trail instead of disappearing into the closed issue. ## Acceptance - Inspect the failed promote run for PR #1407 / issue #1335. - 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: #1335, #1407, run 8528 / #2250.

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

2026-07-15 12:08:20 +00:00

coilyco-ops added the

headless

labels

2026-07-15 12:08:20 +00:00

coilyco-ops commented

2026-07-15 12:08:50 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T12:08:49Z). 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#1422 · branch issue-1422 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1422 · ward v0.710.0 · dispatched 2026-07-15T12:08:40Z
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-1422` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T12:08:49Z). 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#1422` · branch `issue-1422` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1422` · ward `v0.710.0` · dispatched `2026-07-15T12:08:40Z` - **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

2026-07-15 12:09:55 +00:00

Repair failed promote run after PR #1421 #1423

coilyco-ops referenced this issue

2026-07-15 12:10:04 +00:00

Repair promote gate tempdir cleanup failure after #1404 #1408

coilyco-ops referenced this issue from a commit

2026-07-15 12:19:32 +00:00

fix(test): clean dispatch temp home in broker launch test (#1422)

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

2026-07-15 12:19:45 +00:00

Repair failed promote run after PR #1407 #1425