Replace unmergeable ward#1017 issue-scoped director PR #1022

Closed
opened 2026-07-10 10:27:59 +00:00 by coilyco-ops · 1 comment
Member

Problem

ward#1007 produced PR ward#1017 for issue-scoped director behavior, but the director merge lane cannot land it.

Live evidence from the director surface on 2026-07-10 UTC:

  • PR ward#1017 targets closes #1007.
  • Forgejo reports mergeable=false against current main.
  • The PR head 4c4127879bf92c3a4052a8b4717a006ca7dbf24b also reports test / test (pull_request)=failure, target /coilyco-flight-deck/ward/actions/runs/1617/jobs/0, description Failing after 24s.
  • The job log includes current ward test-gate failures around missing .ward/ward-kdl/* source bundle files, plus the PR-specific issue-scoped director tests.

Do

  • Inspect PR ward#1017, resolve or replace its conflict against current main, and preserve the issue-scoped director acceptance from ward#1007 and original ward#988.
  • Keep the issue-scoped path fail-closed: a single issue ref must not widen into the full repo backlog.
  • Account for the .ward/ward-kdl/* source-bundle test failures. If they are fixed by ward#1014, rebase after that lands; if not, include or file the required source-bundle repair with evidence.
  • Produce a mergeable PR and do not close ward#1007 until the fix lands.

Acceptance

  • The replacement PR is mergeable against current main.
  • warded director <owner>/<repo>#N --dry-run or covered tests prove the single-issue path stays scoped to that issue.
  • test / test (pull_request) passes or the issue comment names the exact remaining failing check.
  • The director dry-run no longer skips the replacement PR for merge conflicts.

Related: coilyco-flight-deck/ward#1007, coilyco-flight-deck/ward#988, coilyco-flight-deck/ward#1017, coilyco-flight-deck/ward#1014.

## Problem `ward#1007` produced PR `ward#1017` for issue-scoped director behavior, but the director merge lane cannot land it. Live evidence from the director surface on 2026-07-10 UTC: * PR `ward#1017` targets `closes #1007`. * Forgejo reports `mergeable=false` against current `main`. * The PR head `4c4127879bf92c3a4052a8b4717a006ca7dbf24b` also reports `test / test (pull_request)=failure`, target `/coilyco-flight-deck/ward/actions/runs/1617/jobs/0`, description `Failing after 24s`. * The job log includes current ward test-gate failures around missing `.ward/ward-kdl/*` source bundle files, plus the PR-specific issue-scoped director tests. ## Do * Inspect PR `ward#1017`, resolve or replace its conflict against current `main`, and preserve the issue-scoped director acceptance from `ward#1007` and original `ward#988`. * Keep the issue-scoped path fail-closed: a single issue ref must not widen into the full repo backlog. * Account for the `.ward/ward-kdl/*` source-bundle test failures. If they are fixed by `ward#1014`, rebase after that lands; if not, include or file the required source-bundle repair with evidence. * Produce a mergeable PR and do not close `ward#1007` until the fix lands. ## Acceptance * The replacement PR is mergeable against current `main`. * `warded director <owner>/<repo>#N --dry-run` or covered tests prove the single-issue path stays scoped to that issue. * `test / test (pull_request)` passes or the issue comment names the exact remaining failing check. * The director dry-run no longer skips the replacement PR for merge conflicts. Related: coilyco-flight-deck/ward#1007, coilyco-flight-deck/ward#988, coilyco-flight-deck/ward#1017, coilyco-flight-deck/ward#1014.
Author
Member

Closing as a duplicate of ward#1020, which was filed first for the same unmergeable ward#1017 / issue-scoped director replacement and is already running as engineer-codex-ward-1020. Keeping ward#1020 as the active repair channel.

Closing as a duplicate of `ward#1020`, which was filed first for the same unmergeable `ward#1017` / issue-scoped director replacement and is already running as `engineer-codex-ward-1020`. Keeping `ward#1020` as the active repair channel.
Sign in to join this conversation.
No milestone
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#1022
No description provided.