Fix syncGitRef full-suite failure blocking reservation-cache PR #1236

coilyco-ops commented

2026-07-14 07:31:15 +00:00

Owner

Problem

PR #1236 for ward#1224 is blocked by a full-suite failure outside the reservation-cache change. The engineer reported:

pre-commit run --all-files passed.
Targeted reservation-cache tests passed.
ward exec test still fails in the existing syncGitRef path.
ward agent pr status coilyco-flight-deck/ward#1236 reports the pull_request test / test check failing, with repair bucket ci-parity-gap and note that workflow test.yml has no local ward exec test.yml mirror.

This keeps a targeted-pass PR red and blocks the headless burn-down lane from merging ward#1224.

Do

Reproduce the failing syncGitRef path from the PR #1236 CI context.
Fix the underlying test or implementation issue without weakening the reservation-cache PR.
Add or update the smallest relevant test coverage so the failure does not recur.
Rerun the repo validation needed for PR #1236 to go green.

Acceptance

The syncGitRef failure no longer fails the pull_request test / test workflow.
PR #1236 can be rerun and reaches green checks without changing its intended reservation-cache scope.
Any CI parity gap discovered while debugging is either fixed directly or captured as a separate focused issue.

Blocks PR #1236.
Blocks ward#1224.
Observed during the 2026-07-14 headless burn-down.

## Problem PR #1236 for ward#1224 is blocked by a full-suite failure outside the reservation-cache change. The engineer reported: * `pre-commit run --all-files` passed. * Targeted reservation-cache tests passed. * `ward exec test` still fails in the existing `syncGitRef` path. * `ward agent pr status coilyco-flight-deck/ward#1236` reports the pull_request `test / test` check failing, with repair bucket `ci-parity-gap` and note that workflow `test.yml` has no local `ward exec test.yml` mirror. This keeps a targeted-pass PR red and blocks the headless burn-down lane from merging ward#1224. ## Do * Reproduce the failing `syncGitRef` path from the PR #1236 CI context. * Fix the underlying test or implementation issue without weakening the reservation-cache PR. * Add or update the smallest relevant test coverage so the failure does not recur. * Rerun the repo validation needed for PR #1236 to go green. ## Acceptance * The `syncGitRef` failure no longer fails the pull_request `test / test` workflow. * PR #1236 can be rerun and reaches green checks without changing its intended reservation-cache scope. * Any CI parity gap discovered while debugging is either fixed directly or captured as a separate focused issue. ## Related * Blocks PR #1236. * Blocks ward#1224. * Observed during the 2026-07-14 headless burn-down.

coilyco-ops added the

labels

2026-07-14 07:31:23 +00:00

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

2026-07-14 07:43:22 +00:00

Fix syncGitRef full-suite failure blocking reservation-cache PR #1236 #1241

coilyco-ops commented

2026-07-14 07:45:24 +00:00

Author

Owner

WARDED_WORKFLOW: #1241

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

The fix was small. The failing branch had added a reservations cleanup surface, but the base roster registry still treated it like a startup role. Marking it as a meta command cleared the full-suite registration failure.

Validation: ward exec test, pre-commit run --all-files

Confidence: high.
Surprises: the red check was registry drift, not syncGitRef behavior.
Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1241 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The fix was small. The failing branch had added a `reservations` cleanup surface, but the base roster registry still treated it like a startup role. Marking it as a meta command cleared the full-suite registration failure. Validation: `ward exec test`, `pre-commit run --all-files` Confidence: high. Surprises: the red check was registry drift, not `syncGitRef` behavior. Follow-ups: none.  </details>

coilyco-ops commented

2026-07-14 07:52:07 +00:00

Author

Owner

Director burn-down status: PR #1241 is mergeable and its head 1801a43d244210a37513b0a648d8d1cd48dcf094 has combined status success (test / test (pull_request)). Native merge from this surface is blocked by ward#1240 because ward agent pr merge coilyco-flight-deck/ward#1241 fails before eligibility checks with the dispatch-broker TCP connection refused error.

Director burn-down status: PR #1241 is mergeable and its head `1801a43d244210a37513b0a648d8d1cd48dcf094` has combined status success (`test / test (pull_request)`). Native merge from this surface is blocked by ward#1240 because `ward agent pr merge coilyco-flight-deck/ward#1241` fails before eligibility checks with the dispatch-broker TCP connection refused error.

coilyco-ops commented

2026-07-14 08:57:19 +00:00

Author

Owner

WARDED_WORKFLOW: #1241

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

Merged main into issue-1239, reran ward exec test and pre-commit run --all-files, and kept the reservation-cache fix intact.

Validation: ward exec test, pre-commit run --all-files

Confidence: high.
Surprises: main had already moved, so the only change here was the merge-forward from origin/main.
Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1241 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default Merged `main` into `issue-1239`, reran `ward exec test` and `pre-commit run --all-files`, and kept the reservation-cache fix intact. Validation: `ward exec test`, `pre-commit run --all-files` Confidence: high. Surprises: `main` had already moved, so the only change here was the merge-forward from `origin/main`. Follow-ups: none.  </details>

coilyco-ops commented

2026-07-14 10:57:33 +00:00

Author

Owner

WARDED_WORKFLOW: #1241

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

The branch was already on the reservation meta-command fix, so this pass was verification only.

Validation: ward exec test, pre-commit run --all-files

Confidence: high.
Surprises: none.
Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1241 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The branch was already on the reservation meta-command fix, so this pass was verification only. Validation: `ward exec test`, `pre-commit run --all-files` Confidence: high. Surprises: none. Follow-ups: none.  </details>

coilyco-ops commented

2026-07-14 10:59:40 +00:00

Author

Owner

Director follow-up after the 2026-07-14 10:57Z verification pass: PR #1241 still reports the old failed pull_request check at head ac60b00fc3, even though the latest engineer comment says ward exec test and pre-commit run --all-files passed locally. ward agent pr rerun coilyco-flight-deck/ward 7878 cannot work on this Forgejo because the host exposes no Actions rerun API. Please retrigger PR #1241 by pushing a no-op/empty commit or equivalent branch update to issue-1239, then wait for the pull_request check and report the fresh status. Do not change the reservation-cache PR scope.

Director follow-up after the 2026-07-14 10:57Z verification pass: PR #1241 still reports the old failed pull_request check at head ac60b00fc34a3f9f34da1574280de6f0103336c2, even though the latest engineer comment says `ward exec test` and `pre-commit run --all-files` passed locally. `ward agent pr rerun coilyco-flight-deck/ward 7878` cannot work on this Forgejo because the host exposes no Actions rerun API. Please retrigger PR #1241 by pushing a no-op/empty commit or equivalent branch update to `issue-1239`, then wait for the pull_request check and report the fresh status. Do not change the reservation-cache PR scope.

coilyco-ops commented

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

Author

Owner

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-14T11:11:10Z). 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#1239 · branch issue-1239 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1239 · ward v0.679.0 · dispatched 2026-07-14T11:11:04Z
Comment thread: 5 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-14T07:45:24Z), @coilyco-ops (2026-07-14T07:52:07Z), @coilyco-ops (2026-07-14T08:57:19Z), @coilyco-ops (2026-07-14T10:57:33Z), @coilyco-ops (2026-07-14T10:59:40Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.679.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1239` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T11:11:10Z). 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#1239` · branch `issue-1239` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1239` · ward `v0.679.0` · dispatched `2026-07-14T11:11:04Z` - **Comment thread:** 5 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-14T07:45:24Z), @coilyco-ops (2026-07-14T07:52:07Z), @coilyco-ops (2026-07-14T08:57:19Z), @coilyco-ops (2026-07-14T10:57:33Z), @coilyco-ops (2026-07-14T10:59:40Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.679.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops closed this issue

2026-07-14 11:18:34 +00:00

coilyco-ops commented

2026-07-14 11:18:57 +00:00

Author

Owner

WARDED_WORKFLOW: #1241

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

The branch was refreshed with a no-op commit to retrigger the stale pull_request check, and the PR is green again.

Validation: ward exec test, pre-commit run --all-files

Confidence: high.
Surprises: Forgejo needed a fresh head before it dropped the old failure.
Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1241 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The branch was refreshed with a no-op commit to retrigger the stale pull_request check, and the PR is green again. Validation: `ward exec test`, `pre-commit run --all-files` Confidence: high. Surprises: Forgejo needed a fresh head before it dropped the old failure. Follow-ups: none.  </details>

Rows
Columns

Fix syncGitRef full-suite failure blocking reservation-cache PR #1236 #1239

Problem

Do

Acceptance

Related