Recover PR #1442 merge 405 after green checks #1445

Closed
opened 2026-07-15 13:08:46 +00:00 by coilyco-ops · 2 comments
Member

Problem

PR #1442 for #1166 is green, but the ward-native merge path hit a Forgejo 405 while the PR remained green.

Evidence from the director surface on 2026-07-15:

ward agent pr status coilyco-flight-deck/ward#1442
combined status: success
  test / test (pull_request) = success

ward agent pr merge coilyco-flight-deck/ward#1442
pr merge: coilyco-flight-deck/ward#1442: forgejo merge stayed on 405 after 3 settle attempt(s) while the PR remained green (success on 1afe974675506c8e58972e0a5f2db2b30dc81f32); retry later or check the Forgejo merge queue: forgejo merge PR returned 405 Method Not Allowed: {"message":"Please try again later"...}

The issue #1166 engineer is still active, but it will not see this director-side merge attempt in its seed. This issue is the durable recovery trail if the active run does not land the PR itself.

Acceptance

  • Re-check PR #1442 at head 1afe974675506c8e58972e0a5f2db2b30dc81f32 or a newer explicitly pushed head.
  • If checks remain green and the PR is mergeable, merge it with the ward-native path.
  • If Forgejo continues returning 405, leave exact evidence and either retry through the supported path or repair the merge/retry handling with a focused change.
  • Ensure #1166 closes only after the PR contents land on main.

Related: #1166, #1442.

## Problem PR #1442 for #1166 is green, but the ward-native merge path hit a Forgejo 405 while the PR remained green. Evidence from the director surface on 2026-07-15: ```text ward agent pr status coilyco-flight-deck/ward#1442 combined status: success test / test (pull_request) = success ward agent pr merge coilyco-flight-deck/ward#1442 pr merge: coilyco-flight-deck/ward#1442: forgejo merge stayed on 405 after 3 settle attempt(s) while the PR remained green (success on 1afe974675506c8e58972e0a5f2db2b30dc81f32); retry later or check the Forgejo merge queue: forgejo merge PR returned 405 Method Not Allowed: {"message":"Please try again later"...} ``` The issue #1166 engineer is still active, but it will not see this director-side merge attempt in its seed. This issue is the durable recovery trail if the active run does not land the PR itself. ## Acceptance - Re-check PR #1442 at head `1afe974675506c8e58972e0a5f2db2b30dc81f32` or a newer explicitly pushed head. - If checks remain green and the PR is mergeable, merge it with the ward-native path. - If Forgejo continues returning 405, leave exact evidence and either retry through the supported path or repair the merge/retry handling with a focused change. - Ensure #1166 closes only after the PR contents land on main. Related: #1166, #1442.
Author
Member

DISPATCH-DEFERRED: capacity blocked. Attempted warded engineer coilyco-flight-deck/ward#1445 --harness codex --workflow pull-request-and-merge from the director surface at 2026-07-15T13:08Z. Ward rejected the launch because coilyco-flight-deck/ward already has 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/20260715T130850Z-director-codex-md65-coilyco-flight-deck-ward-1445.log. Retry as soon as a slot opens unless #1166/#1442 lands first.

DISPATCH-DEFERRED: capacity blocked. Attempted `warded engineer coilyco-flight-deck/ward#1445 --harness codex --workflow pull-request-and-merge` from the director surface at 2026-07-15T13:08Z. Ward rejected the launch because coilyco-flight-deck/ward already has 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/20260715T130850Z-director-codex-md65-coilyco-flight-deck-ward-1445.log. Retry as soon as a slot opens unless #1166/#1442 lands first.
Author
Member

Superseded by successful retry: PR #1442 merged at head 82c0b10d01 after checks passed. Closing this merge-405 recovery trail.

Superseded by successful retry: PR #1442 merged at head 82c0b10d01d4e45b4e8b3725f30759adeb7b6128 after checks passed. Closing this merge-405 recovery trail.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/ward#1445
No description provided.