Make stop --print honest for ghost launch records #1216
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/ward!1216
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-1200"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This change makes
ward agent stop --printuse the same stop verdict as the live stop path. Ghost launch records now fail with an explicit not-stoppable message that points atward agent reapor stale-reservation cleanup, while a visible running engineer still prints the exact target.--printnow asks the host broker for a preview stop verdict instead of only resolving the ref.go test ./cmd/wardandpre-commit run --all-files.closes #1200
ward.workflow: pull-request-and-merge
WARDED_WORKFLOW review-note
verdict: block
confidence: high
summary: The stop/print implementation matches ward#1200: preview stop now uses the broker stoppability path, ghost reservations are explicitly rejected, and tests cover visible engineers, ghost reservations, and unknown refs. The PR is blocked because Forgejo reports it is not mergeable against current main.
findings:
file: n/a
line: n/a
problem: PR 1216 is green but
mergeable=false; its base is behind current main after PR 1214 merged.impact: The director cannot merge the PR as submitted, so the engineer has not carried the work to a fully mergeable landed state.
conclusion: Review blocks PR 1216 only on mergeability. The implementation satisfies the issue contract, but the branch must be rebased or merged with current main and pushed back green before the director merge lane can land it.