Provide a concise issue-scoped asynchronous status summary #1601

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

After dispatching #1567, the operator opened Docker Desktop and raw container output to answer a basic question: is the engineer still working?

That visual choice undermined Ward's asynchronous story. The operator should be able to leave after acceptance and later inspect one issue-scoped summary without knowing a container name or watching the execution loop.

Desired behavior

Ward should provide a concise read-only status summary keyed by issue reference.

The summary should show:

accepted, running, terminal, or unknown state
responsible role and harness
resolved workflow
run age or bounded timing context
authoritative terminal verdict when available
repository or Forgejo evidence for the verdict
the next operator action, if any

The feature should stay issue-scoped. Ward does not need a generalized dashboard.

Acceptance criteria

An operator can inspect owner/repo#N without discovering a container name.
A fresh run with no transcript yet returns a useful running state instead of blocking or appearing broken.
The status clearly says when the operator can leave and inspect later.
A terminal status links the decisive repository or issue evidence.
Stale, missing, and superseded reservations are distinguished.
Focused tests cover accepted, starting, running, done, blocked, missing, and superseded runs.

Demo issue: #1567
Fresh-container log behavior: #1594
Docker grouping issue: #1590
Demo review notes: coilysiren/inbox#286

## Observation from the recorded dress rehearsal After dispatching #1567, the operator opened Docker Desktop and raw container output to answer a basic question: is the engineer still working? That visual choice undermined Ward's asynchronous story. The operator should be able to leave after acceptance and later inspect one issue-scoped summary without knowing a container name or watching the execution loop. ## Desired behavior Ward should provide a concise read-only status summary keyed by issue reference. The summary should show: * accepted, running, terminal, or unknown state * responsible role and harness * resolved workflow * run age or bounded timing context * authoritative terminal verdict when available * repository or Forgejo evidence for the verdict * the next operator action, if any The feature should stay issue-scoped. Ward does not need a generalized dashboard. ## Acceptance criteria * An operator can inspect `owner/repo#N` without discovering a container name. * A fresh run with no transcript yet returns a useful running state instead of blocking or appearing broken. * The status clearly says when the operator can leave and inspect later. * A terminal status links the decisive repository or issue evidence. * Stale, missing, and superseded reservations are distinguished. * Focused tests cover accepted, starting, running, done, blocked, missing, and superseded runs. ## Related evidence * Demo issue: #1567 * Fresh-container log behavior: #1594 * Docker grouping issue: #1590 * Demo review notes: https://forgejo.coilysiren.me/coilysiren/inbox/issues/286

coilyco-ops added the

autonomy

async-consult

priority

labels

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

coilyco-ops closed this issue

2026-07-29 06:04:37 +00:00