coilyco-flight-deck/ward

Fork 0

Repair PR #1369 backlog refresh test failure #1371

New issue

Closed

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

coilyco-ops commented

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

Member

Problem

PR #1369 for issue #1016 is open but red on hosted PR CI. The failure reaches repository tests, so this is not a runner setup timeout.

Run evidence:

run 8416 (#2173) failure test.yml pull_request #1369 "fix: keep engineer dispatch under the global cap"
--- FAIL: TestBacklogRefreshReservationStates (0.00s)
agent_director_test.go:627: unexpected path: /api/v1/repos/coilyco-flight-deck/ward/issues?limit=50&state=open
agent_director_test.go:636: backlogRefresh: director: forgejo: list open issues in coilyco-flight-deck/ward: Get "http://127.0.0.1:34351/api/v1/repos/coilyco-flight-deck/ward/issues?limit=50&state=open": EOF

ward agent pr recover coilyco-flight-deck/ward#1369 says the next safe action is to merge once required checks are green, but the check is currently failing.

Acceptance

Repair PR #1369 so TestBacklogRefreshReservationStates passes under hosted test.yml.
Keep the #1016 behavior intact: director dispatch must not exceed the global engineer limit.
Leave PR #1369 green and merge-ready, or merge it if the Ward gate accepts it.

Related: #1016, #1369, run 8416.

## Problem PR #1369 for issue #1016 is open but red on hosted PR CI. The failure reaches repository tests, so this is not a runner setup timeout. Run evidence: ```text run 8416 (#2173) failure test.yml pull_request #1369 "fix: keep engineer dispatch under the global cap" --- FAIL: TestBacklogRefreshReservationStates (0.00s) agent_director_test.go:627: unexpected path: /api/v1/repos/coilyco-flight-deck/ward/issues?limit=50&state=open agent_director_test.go:636: backlogRefresh: director: forgejo: list open issues in coilyco-flight-deck/ward: Get "http://127.0.0.1:34351/api/v1/repos/coilyco-flight-deck/ward/issues?limit=50&state=open": EOF ``` `ward agent pr recover coilyco-flight-deck/ward#1369` says the next safe action is to merge once required checks are green, but the check is currently failing. ## Acceptance - Repair PR #1369 so `TestBacklogRefreshReservationStates` passes under hosted `test.yml`. - Keep the #1016 behavior intact: director dispatch must not exceed the global engineer limit. - Leave PR #1369 green and merge-ready, or merge it if the Ward gate accepts it. Related: #1016, #1369, run 8416.

coilyco-ops added the

coherence-core

headless

labels

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

coilyco-ops commented

2026-07-15 09:36:14 +00:00

Author

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-15T09:36:13Z). 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#1371 · branch issue-1371 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1371 · ward v0.710.0 · dispatched 2026-07-15T09:36:06Z
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-1371` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T09:36:13Z). 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#1371` · branch `issue-1371` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1371` · ward `v0.710.0` · dispatched `2026-07-15T09:36:06Z` - **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 09:41:17 +00:00

Recover green PR #1369 from Forgejo merge 405 #1372

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

2026-07-15 09:51:23 +00:00

Fix backlog refresh test config source #1377

coilyco-ops closed this issue

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

coilyco-ops commented

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

Author

Member

WARDED_WORKFLOW: #1377

details

workflow: pull-request-and-merge; review summary: skipped (temporary ward default pending brokered QA)
felt like a small test-fixture hardening; the behavior stayed the same.
confidence: high
surprises: the test was inheriting host WARD_CONFIG_REF.
follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1377 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped (temporary ward default pending brokered QA) felt like a small test-fixture hardening; the behavior stayed the same. confidence: high surprises: the test was inheriting host `WARD_CONFIG_REF`. follow-ups: none. </details>

coilyco-ops commented

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

Author

Member

Downstream evidence: #1369 subsequently merged, and its post-merge promote/release runs 8443 and 8444 both succeeded.

QA follow-up: PASS for the backlog-refresh test repair. PR #1377 test run 8436 succeeded and post-merge promote run 8437 succeeded. The later release failure on run 8438 was the separate ignored-defaults-asset release bug, captured in #1375 and repaired by #1379. Downstream evidence: #1369 subsequently merged, and its post-merge promote/release runs 8443 and 8444 both succeeded.