coilyco-flight-deck/ward

Fork 0

Recover PR #1369 after widened retry still 405 #1378

New issue

Closed

opened 2026-07-15 09:52:05 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-15 09:52:05 +00:00

Member

Problem

PR #1374 closed #1372 by widening the transient Forgejo 405 retry window, but the linked target PR #1369 is still not recovered:

PR #1369 state=open merged=false mergeable=false
head 1456f05378a91aee5bbca3cefd96276aa74d9cd0
combined status success: test / test (pull_request)=success

The #1372 workflow comment also says PR #1369 still refused with 405 after the wider retry window, so #1372's acceptance remains incomplete.

Acceptance

Recover PR #1369 to a merged state, or leave exact current Forgejo diagnostics showing why it cannot be merged.
Do not change the green #1369 head unless required for a focused recovery.
Confirm post-merge promote/release if #1369 lands, or capture any follow-on failure separately.

Related: #1016, #1369, #1372, #1374.

## Problem PR #1374 closed #1372 by widening the transient Forgejo 405 retry window, but the linked target PR #1369 is still not recovered: ```text PR #1369 state=open merged=false mergeable=false head 1456f05378a91aee5bbca3cefd96276aa74d9cd0 combined status success: test / test (pull_request)=success ``` The #1372 workflow comment also says PR #1369 still refused with 405 after the wider retry window, so #1372's acceptance remains incomplete. ## Acceptance - Recover PR #1369 to a merged state, or leave exact current Forgejo diagnostics showing why it cannot be merged. - Do not change the green #1369 head unless required for a focused recovery. - Confirm post-merge promote/release if #1369 lands, or capture any follow-on failure separately. Related: #1016, #1369, #1372, #1374.

coilyco-ops added the

coherence-core

headless

labels

2026-07-15 09:52:05 +00:00

coilyco-ops commented

2026-07-15 09:52:28 +00:00

Author

Member

WARDED_WORKFLOW: dispatch-deferred

capacity details

Attempted dispatch:

warded engineer coilyco-flight-deck/ward#1378 --harness codex --workflow pull-request-and-merge

The broker refused before launch because the per-repo engineer limit is full:

repo engineer limit is reached for coilyco-flight-deck/ward: 3 active engineer(s) (limit 3)

Host dispatch log: /Users/kai/.ward/agent-logs/dispatch/20260715T095209Z-director-codex-jp85-coilyco-flight-deck-ward-1378.log

No container was launched for this attempt. Redispatch when a Ward engineer slot opens.

WARDED_WORKFLOW: dispatch-deferred <details><summary>capacity details</summary> Attempted dispatch: ```text warded engineer coilyco-flight-deck/ward#1378 --harness codex --workflow pull-request-and-merge ``` The broker refused before launch because the per-repo engineer limit is full: ```text repo engineer limit is reached for coilyco-flight-deck/ward: 3 active engineer(s) (limit 3) ``` Host dispatch log: `/Users/kai/.ward/agent-logs/dispatch/20260715T095209Z-director-codex-jp85-coilyco-flight-deck-ward-1378.log` No container was launched for this attempt. Redispatch when a Ward engineer slot opens. </details>

coilyco-ops referenced this issue

2026-07-15 09:54:05 +00:00

Recover green PR #1369 from Forgejo merge 405 #1372

coilyco-ops commented

2026-07-15 09:54:57 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

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

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

2026-07-15 10:01:43 +00:00

coilyco-ops commented

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

Author

Member

QA follow-up: PASS / no longer actionable. This recovery issue existed to get PR #1369 past the transient 405/retry state. PR #1369 is now merged at 5dc306f5f5, with promote run 8443 and release run 8444 both green. No replacement issue is needed.

QA follow-up: PASS / no longer actionable. This recovery issue existed to get PR #1369 past the transient 405/retry state. PR #1369 is now merged at 5dc306f5f56af04946c814ae75b1910e5e182cbc, with promote run 8443 and release run 8444 both green. No replacement issue is needed.