Render run list miniatures from compact per-stage route evidence
This commit is contained in:
+11
@@ -543,6 +543,17 @@ rapid changes are coalesced to at most a few frames per second per run.
|
||||
once-per-second poll: the Android app consumes these pushes instead, while the
|
||||
TUI still polls in this release.
|
||||
|
||||
Run-list summaries and subscribe snapshots additionally carry compact
|
||||
`graph_evidence: {complete: true, visits: [...]}`. Each visit contains only
|
||||
`sequence`, `stage`, `status`, `outcome` and `target`: the last visit of each
|
||||
stage and each distinct taken route, ordered by sequence. Repeated loops do not
|
||||
grow the summary indefinitely, and private step inputs, outputs, transcripts
|
||||
and diagnostics are excluded from this projection. Live `run_event.graph_visits`
|
||||
preserves changed visits across coalescing (unlike the single latest `step`).
|
||||
Clients merge these by sequence and retain last-stage/distinct-route evidence.
|
||||
Missing evidence from an older peer means unknown, not that every stage shares
|
||||
the overall run result. These fields are additive; older peers ignore them.
|
||||
|
||||
In the run inspector, `n`/`p` select the next/previous recorded execution visit,
|
||||
including repeated visits in loops, from any pane. Selection stops at the last
|
||||
visit or overview; it does not wrap. The selected stage has a full-row highlight;
|
||||
|
||||
Reference in New Issue
Block a user