fix: issue-scoped director fail closed #1027

Merged
coilyco-ops merged 3 commits from issue-1020 into main 2026-07-10 19:43:12 +00:00
Member

closes #1020
ward.workflow: pull-requests-and-merge

closes #1020 ward.workflow: pull-requests-and-merge
feat(director): add issue-scoped ref path
Some checks failed
test / test (pull_request) Failing after 19s
ed602e394b
Author
Member

WARD-OUTCOME: blocked 🛑

details

workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
blocker: coilyco-flight-deck/ward#1009
CI: test / test (pull_request) failed after 19s on PR #1027.
local checks: ward exec test still fails on the cleanup-blocked asset/config surface, including TestCapabilityGuardfilesExist, TestRunAgentAdvisorFreeformStaysLocal, TestAgentRunningEngineerFromInspectIncludesReservation, TestPartitionReplySpecs, TestAcquireLocalReservationConflictAndForce, TestPrecheckReservation, TestReservationCommentBodyHasMarker, TestReservationClaims, TestReservationRecheckLost, TestReviewerRunnerIncludesStderrDetail, TestUntrustedOwnerErr, TestOwnerAllowed, TestRetiredVerbsErrorAsUnknown, TestAgentsListSurvivesExecMount, TestSelectConfigSourceDefaultsBaked, TestBuildForgejoOpsFromRealBundle, TestMountWardKdlExecFromRealBundle, TestLoadFleetConfigFromBundleSource, TestBuildForgejoOpsWithRealLookingConfigRef, TestBuildForgejoOpsAnnotatesSelectedConfigSource, TestDefaultsAssetsMirrorWardKDL, TestRunDoctorWithValidBundle, TestExecAssetsMirrorWardKDL, TestFleetAssetsMirrorWardKDL, TestOverrideForgejoCreateIssueAddsQuietFlag, TestForgejoGraftInventory, TestOverrideForgejoViewIssueSwapsLeaf, TestOpsAssetsMatchWardKDL, TestOpsForgejoMounts, TestOpsForgejoIssueListAllMounts, TestOpsForgejoIssueCommentDeleteMounts, TestOpsForgejoNamespaceRerooted, TestRunSetupWithUnsetRef, TestRunSetupWithFixtureRef, TestSmartDefaultsBaked, TestTopologyAssetsMirrorWardKDL, TestMountWardKdlExecMountsNewSurfaces, and TestMountWardKdlExecSkipsCollisions.
implementation: the issue-scoped director path is in place, and the replacement branch stays against current main without restoring the deleted source tree.
confidence: high
surprise: the full suite still depends on the source-bundle/specgen cleanup.
follow-up: land #1009 or its replacement bundle fix, then rerun the full test verb and the PR check.

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default blocker: coilyco-flight-deck/ward#1009 CI: `test / test (pull_request)` failed after 19s on PR #1027. local checks: `ward exec test` still fails on the cleanup-blocked asset/config surface, including TestCapabilityGuardfilesExist, TestRunAgentAdvisorFreeformStaysLocal, TestAgentRunningEngineerFromInspectIncludesReservation, TestPartitionReplySpecs, TestAcquireLocalReservationConflictAndForce, TestPrecheckReservation, TestReservationCommentBodyHasMarker, TestReservationClaims, TestReservationRecheckLost, TestReviewerRunnerIncludesStderrDetail, TestUntrustedOwnerErr, TestOwnerAllowed, TestRetiredVerbsErrorAsUnknown, TestAgentsListSurvivesExecMount, TestSelectConfigSourceDefaultsBaked, TestBuildForgejoOpsFromRealBundle, TestMountWardKdlExecFromRealBundle, TestLoadFleetConfigFromBundleSource, TestBuildForgejoOpsWithRealLookingConfigRef, TestBuildForgejoOpsAnnotatesSelectedConfigSource, TestDefaultsAssetsMirrorWardKDL, TestRunDoctorWithValidBundle, TestExecAssetsMirrorWardKDL, TestFleetAssetsMirrorWardKDL, TestOverrideForgejoCreateIssueAddsQuietFlag, TestForgejoGraftInventory, TestOverrideForgejoViewIssueSwapsLeaf, TestOpsAssetsMatchWardKDL, TestOpsForgejoMounts, TestOpsForgejoIssueListAllMounts, TestOpsForgejoIssueCommentDeleteMounts, TestOpsForgejoNamespaceRerooted, TestRunSetupWithUnsetRef, TestRunSetupWithFixtureRef, TestSmartDefaultsBaked, TestTopologyAssetsMirrorWardKDL, TestMountWardKdlExecMountsNewSurfaces, and TestMountWardKdlExecSkipsCollisions. implementation: the issue-scoped director path is in place, and the replacement branch stays against current main without restoring the deleted source tree. confidence: high surprise: the full suite still depends on the source-bundle/specgen cleanup. follow-up: land #1009 or its replacement bundle fix, then rerun the full test verb and the PR check. </details>
merge: refresh issue-scoped director PR against main
All checks were successful
test / test (pull_request) Successful in 24s
a87d3ac652
Author
Member

WARD-OUTCOME: blocked 🛑

details

workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
implementation: issue-scoped director ref path is in place; PR #1027 is mergeable and the stale Known blocker text was removed.
blocked check: ward exec test still fails on TestMountWardKdlExecMountsNewSurfaces.
felt: straightforward until the bundle mount surface turned out to be container-specific.
confidence: medium
surprise: the merge-conflict part was clean; the bundle surface stayed red.
follow-up: fix the exec bundle mount surface, rerun ward exec test, then reclassify.

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default implementation: issue-scoped director ref path is in place; PR #1027 is mergeable and the stale Known blocker text was removed. blocked check: `ward exec test` still fails on `TestMountWardKdlExecMountsNewSurfaces`. felt: straightforward until the bundle mount surface turned out to be container-specific. confidence: medium surprise: the merge-conflict part was clean; the bundle surface stayed red. follow-up: fix the exec bundle mount surface, rerun `ward exec test`, then reclassify. </details>
Author
Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-claude-ward-1027 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness claude (reserved 2026-07-10T19:33:33Z). 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#1027 · branch issue-1027 · harness claude · workflow pull-requests-and-merge
  • Run: engineer-claude-ward-1027 · ward v0.600.0 · dispatched 2026-07-10T19:33:33Z
  • Comment thread: 2 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.600.0).

— Claude (she/her), via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-claude-ward-1027` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness claude` (reserved 2026-07-10T19:33:33Z). 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#1027` · branch `issue-1027` · harness `claude` · workflow `pull-requests-and-merge` - **Run:** `engineer-claude-ward-1027` · ward `v0.600.0` · dispatched `2026-07-10T19:33:33Z` - **Comment thread:** 2 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T10:59:24Z), @coilyco-ops (2026-07-10T16:53:49Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.600.0). </details> </details> <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Merge remote-tracking branch 'origin/main' into issue-1020
All checks were successful
test / test (pull_request) Successful in 30s
85afb34535
# Conflicts:
#	cmd/ward/configsource.go
Sign in to join this conversation.
No description provided.