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

Surface broker dispatch logs on advisor dispatch #1405

Merged
coilyco-ops merged 1 commit from issue-1336 into main 2026-07-15 11:27:26 +00:00
Conversation 0 Commits 1 Files changed 2 +32 -18
coilyco-ops commented 2026-07-15 11:25:51 +00:00
Member
Copy link

This change makes the advisor ref-dispatch path surface the broker response line instead of dropping into fire-and-forget, so the dispatcher sees the same log path and decision context as the engineer path.

  • What changed: advisor broker dispatch now waits for the launch response and prints the structured broker line with the log path.
  • Why: the dispatch decision was only reliably visible in host logs for one path, which made downstream triage inconsistent.
  • Tests: updated the advisor-path regression and kept the promptness coverage; go test ./cmd/ward passed.

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

This change makes the advisor ref-dispatch path surface the broker response line instead of dropping into fire-and-forget, so the dispatcher sees the same log path and decision context as the engineer path. - What changed: advisor broker dispatch now waits for the launch response and prints the structured broker line with the log path. - Why: the dispatch decision was only reliably visible in host logs for one path, which made downstream triage inconsistent. - Tests: updated the advisor-path regression and kept the promptness coverage; `go test ./cmd/ward` passed. closes #1336 ward.workflow: pull-request-and-merge
Surface broker dispatch logs on advisor dispatch
All checks were successful
test / test (pull_request) Successful in 1m8s
Details
2523a2c20f 
closes #1336

ward.workflow: pull-request-and-merge
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!1405
No description provided.