coilyco-flight-deck/ward

Fork 0

Recover stuck PR #1407 check after runner context cancellation #1413

New issue

Closed

opened 2026-07-15 11:42:31 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-15 11:42:31 +00:00

Member

Problem

PR #1407 for #1335 is mergeable, and local focused tests passed, but its required Forgejo check is stuck pending.

Evidence:

run 8507 (#2236) running test.yml pull_request #1407 "Inject launch pre-flight context into agent seed"

The live job log for run #2236 already ended with a runner-side terminal failure:

go test ./...
[runner]: context canceled
Get "http://localhost:2375/.../SUMMARY.md": context canceled
Get "http://localhost:2375/.../pathcmd.txt": context canceled
Job failed

ward agent pr rerun coilyco-flight-deck/ward 8507 cannot repair it because this Forgejo has no Actions rerun API. The command reports that the run must be retriggered by pushing to the branch, such as an empty commit.

Acceptance

Recover PR #1407 from the stale pending check, preferably by retriggering test.yml on the existing branch without changing behavior.
Confirm the resulting required check is green, or leave exact blocker evidence.
Do not lose the #1335 implementation in PR #1407.
Leave final evidence on #1335 or this issue.

Related: #1335, #1407, run 8507 / #2236.

## Problem PR #1407 for #1335 is mergeable, and local focused tests passed, but its required Forgejo check is stuck pending. Evidence: ```text run 8507 (#2236) running test.yml pull_request #1407 "Inject launch pre-flight context into agent seed" ``` The live job log for run #2236 already ended with a runner-side terminal failure: ```text go test ./... [runner]: context canceled Get "http://localhost:2375/.../SUMMARY.md": context canceled Get "http://localhost:2375/.../pathcmd.txt": context canceled Job failed ``` `ward agent pr rerun coilyco-flight-deck/ward 8507` cannot repair it because this Forgejo has no Actions rerun API. The command reports that the run must be retriggered by pushing to the branch, such as an empty commit. ## Acceptance - Recover PR #1407 from the stale pending check, preferably by retriggering test.yml on the existing branch without changing behavior. - Confirm the resulting required check is green, or leave exact blocker evidence. - Do not lose the #1335 implementation in PR #1407. - Leave final evidence on #1335 or this issue. Related: #1335, #1407, run 8507 / #2236.

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

2026-07-15 11:42:31 +00:00

coilyco-ops added the

headless

labels

2026-07-15 11:42:31 +00:00

coilyco-ops commented

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

Author

Member

DISPATCH-DEFERRED: capacity blocked. Attempted warded engineer coilyco-flight-deck/ward#1413 --harness codex --workflow pull-request-and-merge at 2026-07-15T11:42Z. Ward rejected the launch because coilyco-flight-deck/ward already had 3 active engineers at the repo limit. Broker evidence: repo engineer limit is reached for coilyco-flight-deck/ward: 3 active engineer(s) (limit 3). Dispatch log: /Users/kai/.ward/agent-logs/dispatch/20260715T114235Z-director-codex-jp85-coilyco-flight-deck-ward-1413.log. Retry this #1407 CI recovery at the next available slot.

coilyco-ops commented

2026-07-15 11:49:18 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

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

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-1413` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T11:49: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#1413` · branch `issue-1413` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1413` · ward `v0.710.0` · dispatched `2026-07-15T11:49:00Z` - **Comment thread:** 1 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-15T11:42:53Z) 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:00:13 +00:00

Diagnose broker-forwarded dispatches that leave no reservation or running engineer #1418

coilyco-ops commented

2026-07-15 12:05:51 +00:00

Author

Member

WARDED_WORKFLOW: #1407

details

workflow: pull-request-and-merge; review summary: review gate skipped intentionally by temporary ward default pending brokered QA

Recovered the stuck check by pushing a no-op commit to issue-1335, then merged PR #1407 after the retriggered test.yml turned green.
The first retrigger failed after 10m3s; the second retrigger succeeded in 54s.

Confidence: high. Surprise: Forgejo Actions logs on this instance 404'd, so the run-page summary was the reliable blocker evidence.
Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1407 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped intentionally by temporary ward default pending brokered QA Recovered the stuck check by pushing a no-op commit to `issue-1335`, then merged PR #1407 after the retriggered `test.yml` turned green. The first retrigger failed after 10m3s; the second retrigger succeeded in 54s. Confidence: high. Surprise: Forgejo Actions logs on this instance 404'd, so the run-page summary was the reliable blocker evidence. Follow-ups: none. </details>

coilyco-ops closed this issue

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