Publish one authoritative terminal outcome per Ward run #1602

New issue

Closed

opened 2026-07-28 09:21:46 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-28 09:21:46 +00:00

Member

Observation from the recorded dress rehearsal

During the demo run for #1567, Ward posted WARD-WORKFLOW: done, then posted WARD-WORKFLOW: blocked 13 seconds later for the same run. A later recovery run posted done again.

Each message described a different layer, but the issue timeline presented them as equally authoritative terminal outcomes. The operator reasonably read the first done as successful completion.

Desired behavior

Ward should publish one authoritative terminal outcome for each run after the broker and cleanup path reconcile the engineer result with repository and issue evidence.

The engineer result remains provisional until Ward verifies the resolved workflow.
Ward keys the terminal verdict to the run or reservation.
Cleanup can refine the verdict without adding a second conflicting top-level terminal marker.
Ward preserves detailed agent and cleanup reports as supporting evidence.
The issue state and the visible terminal verdict agree.

Acceptance criteria

One run cannot expose both top-level done and blocked outcomes.
A done verdict confirms the workflow's required repository and issue state.
If cleanup changes a provisional result, Ward visibly supersedes the provisional state.
Reservation release reports the reconciled authoritative verdict.
Focused tests cover engineer-done plus cleanup-blocked, engineer-done plus cleanup-done, and recovery after a prior blocked run.

Demo issue: #1567
Related dispatch-health correction: #1576
Earlier salvage signature: #504
Demo review notes: coilysiren/inbox#286

## Observation from the recorded dress rehearsal During the demo run for #1567, Ward posted `WARD-WORKFLOW: done`, then posted `WARD-WORKFLOW: blocked` 13 seconds later for the same run. A later recovery run posted `done` again. Each message described a different layer, but the issue timeline presented them as equally authoritative terminal outcomes. The operator reasonably read the first `done` as successful completion. ## Desired behavior Ward should publish one authoritative terminal outcome for each run after the broker and cleanup path reconcile the engineer result with repository and issue evidence. * The engineer result remains provisional until Ward verifies the resolved workflow. * Ward keys the terminal verdict to the run or reservation. * Cleanup can refine the verdict without adding a second conflicting top-level terminal marker. * Ward preserves detailed agent and cleanup reports as supporting evidence. * The issue state and the visible terminal verdict agree. ## Acceptance criteria * One run cannot expose both top-level `done` and `blocked` outcomes. * A `done` verdict confirms the workflow's required repository and issue state. * If cleanup changes a provisional result, Ward visibly supersedes the provisional state. * Reservation release reports the reconciled authoritative verdict. * Focused tests cover engineer-done plus cleanup-blocked, engineer-done plus cleanup-done, and recovery after a prior blocked run. ## Related evidence * Demo issue: #1567 * Related dispatch-health correction: #1576 * Earlier salvage signature: #504 * Demo review notes: https://forgejo.coilysiren.me/coilysiren/inbox/issues/286

coilyco-ops added the

autonomy

headless

priority

labels

2026-07-29 03:47:43 +00:00

coilyco-ops closed this issue

2026-07-29 05:59:16 +00:00