coilyco-flight-deck/ward
2
0
Fork 0
Code Issues 106 Pull requests 1 Projects Releases 737 Packages Wiki Activity Actions 1

Repair failed promote run after PR #1421 #1426

Merged
coilyco-ops merged 1 commit from issue-1423 into main 2026-07-15 12:25:46 +00:00
Conversation 2 Commits 1 Files changed 1 +5 -1
coilyco-ops commented 2026-07-15 12:19:46 +00:00
Member
Copy link

This keeps the broker-request regression from leaving a dirty dispatch tree behind in the temp HOME path. The test now removes both the raw and redacted dispatch artifact subtrees after verifying the launch path, which matches the failure mode the promote run surfaced.

  • What changed: broadened cleanup in TestRunHostDispatchBrokerRequestClearsBrokerEnvWhileLaunchRuns.
  • Why: CI run 8530 failed in cmd/ward after PR #1421, and the cleanup path only cleared one side of the broker artifact tree.
  • Test/CI: go test ./... -count=1 passes locally.

closes #1423
ward.workflow: pull-request-and-merge

This keeps the broker-request regression from leaving a dirty dispatch tree behind in the temp HOME path. The test now removes both the raw and redacted dispatch artifact subtrees after verifying the launch path, which matches the failure mode the promote run surfaced. - What changed: broadened cleanup in `TestRunHostDispatchBrokerRequestClearsBrokerEnvWhileLaunchRuns`. - Why: CI run 8530 failed in `cmd/ward` after PR #1421, and the cleanup path only cleared one side of the broker artifact tree. - Test/CI: `go test ./... -count=1` passes locally. closes #1423 ward.workflow: pull-request-and-merge
Tighten dispatch artifact cleanup in broker request test
All checks were successful
test / test (pull_request) Successful in 56s
Details
6e2edc14c4
coilyco-ops closed this pull request 2026-07-15 12:23:17 +00:00
coilyco-ops commented 2026-07-15 12:24:22 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T12:23:17Z has no newer ward acknowledgement yet

This action is blocked until the feedback is visibly acknowledged.

— Claude (she/her), via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> manual close/update snapshot at 2026-07-15T12:23:17Z has no newer ward acknowledgement yet This action is blocked until the feedback is visibly acknowledged. </details> <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
coilyco-ops commented 2026-07-15 12:24:22 +00:00
Author
Member
Copy link

WARDED_WORKFLOW: blocked 🛑

details

manual close/update snapshot at 2026-07-15T12:23:17Z has no newer ward acknowledgement yet

This action is blocked until the feedback is visibly acknowledged.

— Claude (she/her), via ward agent

WARDED_WORKFLOW: blocked 🛑 <details><summary>details</summary> manual close/update snapshot at 2026-07-15T12:23:17Z has no newer ward acknowledgement yet This action is blocked until the feedback is visibly acknowledged. </details> <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
coilyco-ops reopened this pull request 2026-07-15 12:25:40 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
pressure-test
Cold-read release pressure-test findings and coordination

  
sunday-sprint
Burn-down by Sunday 2026-06-07

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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!1426
No description provided.