coilyco-flight-deck/ward

Fork 0

Replace closed-unmerged ward#1019 dirty-only Goose residual PR #1021

New issue

Closed

opened 2026-07-10 10:27:59 +00:00 by coilyco-ops · 4 comments

coilyco-ops commented

2026-07-10 10:27:59 +00:00

Member

Problem

ward#1006 produced PR ward#1019 for the dirty-only Goose residual landing path, but the PR is now closed with merged=false and the carried issue remains open.

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

PR ward#1019 targeted closes #1006 and attempted the dirty-only Goose residual landing path.
The PR head 8a1fdc67a7b7bab14ba55c31936b23b6df58b709 reported test / test (pull_request)=failure, target /coilyco-flight-deck/ward/actions/runs/1619/jobs/0, description Failing after 15s.
The job log included failures in cmd/ward, including TestCapabilityGuardfilesExist, TestBacklogRefreshReservationStates, and missing .ward/ward-kdl/* source bundle paths.
PR ward#1019 is closed unmerged, so it cannot satisfy ward#1006 or the original ward#998 path.

Do

Inspect PR ward#1019, its failed Actions run 1619, and the original ward#1006 contract.
Produce a replacement fix that lands the dirty-only Goose residual behavior through a mergeable, green PR.
Account for the current .ward/ward-kdl/* source-bundle test failures. If they are fixed by ward#1014, rebase after that lands; if not, include the required source-bundle repair or file a narrower blocker with evidence.
Do not treat a closed-unmerged PR as success.

Acceptance

The replacement PR is mergeable against current main.
test / test (pull_request) passes or the issue comment names the exact remaining failing check.
ward#1006 and ward#998 close only after a landed fix reaches main.

## Problem `ward#1006` produced PR `ward#1019` for the dirty-only Goose residual landing path, but the PR is now closed with `merged=false` and the carried issue remains open. Live evidence from the director surface on 2026-07-10 UTC: * PR `ward#1019` targeted `closes #1006` and attempted the dirty-only Goose residual landing path. * The PR head `8a1fdc67a7b7bab14ba55c31936b23b6df58b709` reported `test / test (pull_request)=failure`, target `/coilyco-flight-deck/ward/actions/runs/1619/jobs/0`, description `Failing after 15s`. * The job log included failures in `cmd/ward`, including `TestCapabilityGuardfilesExist`, `TestBacklogRefreshReservationStates`, and missing `.ward/ward-kdl/*` source bundle paths. * PR `ward#1019` is closed unmerged, so it cannot satisfy `ward#1006` or the original `ward#998` path. ## Do * Inspect PR `ward#1019`, its failed Actions run `1619`, and the original `ward#1006` contract. * Produce a replacement fix that lands the dirty-only Goose residual behavior through a mergeable, green PR. * Account for the current `.ward/ward-kdl/*` source-bundle test failures. If they are fixed by `ward#1014`, rebase after that lands; if not, include the required source-bundle repair or file a narrower blocker with evidence. * Do not treat a closed-unmerged PR as success. ## Acceptance * The replacement PR is mergeable against current `main`. * `test / test (pull_request)` passes or the issue comment names the exact remaining failing check. * `ward#1006` and `ward#998` close only after a landed fix reaches `main`. Related: coilyco-flight-deck/ward#1006, coilyco-flight-deck/ward#998, coilyco-flight-deck/ward#1019, coilyco-flight-deck/ward#1014.

coilyco-ops added the

headless

labels

2026-07-10 10:27:59 +00:00

coilyco-ops commented

2026-07-10 10:44:13 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-1021 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T10:44:13Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force 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#1021 · branch issue-1021 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-1021 · ward v0.580.0 · dispatched 2026-07-10T10:44:13Z
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.580.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-1021` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T10:44:13Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` 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#1021` · branch `issue-1021` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-1021` · ward `v0.580.0` · dispatched `2026-07-10T10:44:13Z` - **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.580.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-10 10:56:09 +00:00

fix(goose): dirty-only residual landing #1026

coilyco-ops commented

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

Author

Member

WARD-OUTCOME: blocked 🛑

details

workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
status: blocked on coilyco-flight-deck/ward#1009; test / test (pull_request) failed
failing checks: TestCapabilityGuardfilesExist, TestDefaultsAssetsMirrorWardKDL, TestFleetAssetsMirrorWardKDL, TestExecAssetsMirrorWardKDL, TestOpsAssetsMatchWardKDL, TestRunDoctorWithValidBundle, TestSmartDefaultsBaked, TestTopologyAssetsMirrorWardKDL, TestMountWardKdlExecMountsNewSurfaces, TestMountWardKdlExecSkipsCollisions, TestOpsForgejoMounts, TestForgejoGraftInventory, TestOverrideForgejoCreateIssueAddsQuietFlag, TestOverrideForgejoViewIssueSwapsLeaf, TestRunSetupWithUnsetRef, TestRunSetupWithFixtureRef
felt: the Goose residual fix is in; the repo-wide source-bundle cleanup still blocks merge
confidence: medium
surprise: the reap-focused tests passed, but the package run still trips on missing .ward/ward-kdl/* bundle paths
follow-up: land the bundle cleanup in #1009, then rerun this PR

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default status: blocked on coilyco-flight-deck/ward#1009; `test / test (pull_request)` failed failing checks: `TestCapabilityGuardfilesExist`, `TestDefaultsAssetsMirrorWardKDL`, `TestFleetAssetsMirrorWardKDL`, `TestExecAssetsMirrorWardKDL`, `TestOpsAssetsMatchWardKDL`, `TestRunDoctorWithValidBundle`, `TestSmartDefaultsBaked`, `TestTopologyAssetsMirrorWardKDL`, `TestMountWardKdlExecMountsNewSurfaces`, `TestMountWardKdlExecSkipsCollisions`, `TestOpsForgejoMounts`, `TestForgejoGraftInventory`, `TestOverrideForgejoCreateIssueAddsQuietFlag`, `TestOverrideForgejoViewIssueSwapsLeaf`, `TestRunSetupWithUnsetRef`, `TestRunSetupWithFixtureRef` felt: the Goose residual fix is in; the repo-wide source-bundle cleanup still blocks merge confidence: medium surprise: the reap-focused tests passed, but the package run still trips on missing `.ward/ward-kdl/*` bundle paths follow-up: land the bundle cleanup in #1009, then rerun this PR </details>

coilyco-ops commented

2026-07-10 16:43:32 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-1021 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-10T16:43:31Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#1021 · branch issue-1021 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-1021 · ward v0.584.0 · dispatched 2026-07-10T16:43:31Z
Comment thread: 1 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-10T10:58:15Z)
- stripped: @coilyco-ops (2026-07-10T10:44:13Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-1021` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T16:43:31Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` 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#1021` · branch `issue-1021` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-1021` · ward `v0.584.0` · dispatched `2026-07-10T16:43:31Z` - **Comment thread:** 1 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T10:58:15Z) - stripped: @coilyco-ops (2026-07-10T10:44:13Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.584.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 17:04:28 +00:00

Author

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
felt: the source-bundle repair exposed the real backlog-feed mismatch cleanly
confidence: high
surprise: the director mock wanted typed feeds while the generic issue feed stayed public
follow-up: merge PR #1026

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default felt: the source-bundle repair exposed the real backlog-feed mismatch cleanly confidence: high surprise: the director mock wanted typed feeds while the generic issue feed stayed public follow-up: merge PR #1026 </details>

coilyco-ops closed this issue

2026-07-10 17:05:13 +00:00