fixed event/live transition

docs/claude/probe-readings.md

@@ -992,6 +992,7 @@ configuration that carries settings, is the defect this exists for — a saved h
 [events] activated row0: replaying=1 pane=1 pane_w=240 pane_box=228 tick=0 window=2.000 axis=[-1.600,0.400] marker=0.000 thumbnail=1 thumb_size=138x46 thumb_visible=1 rows_kept=1 selected=2/2
 [events] replayed: channels=3 samples=20001 replaying=1 waveform=1
 [events] live again: replaying=0 waveform=0
+[events] live restored (after replay): window=0.500000 (want 0.500000) trigger=1 (want 1) channel='square' (want 'square') level=0 (want 0) enabled=1 armed=1 pinned=0 held=0 mode=2 pending=0 gen=10/5
 [events] recording off, trigger off: button_visible=1 pane=1 pane_w=240 tick=1 recording=0
 [events] recording off, trigger on: button_visible=1 pane=1 pane_w=240 tick=1 recording=0
 [events] compare buttons: cached=2 selected=2 compare=1 accumulate=1
@@ -1000,6 +1001,7 @@ configuration that carries settings, is the defect this exists for — a saved h
 [events] compare sync: y_a=-3.500 y_b=-3.500 mirrored=1
 [events] accumulate: kind=2 rows=1 channels=8 samples0=32964 selected=2 traces0=8 window=2.000
 [events] group left: replaying=0 kind=0 waveform=0
+[events] live restored (after a group): window=0.500000 (want 0.500000) trigger=1 (want 1) channel='square' (want 'square') level=0 (want 0) enabled=1 armed=1 pinned=0 held=0 mode=2 pending=0 gen=22/16
 ```
 
 `thumb_size` is the built size of the row's picture: `kEventThumbW` wide, and as tall as the *stored*
@@ -1016,6 +1018,21 @@ header — `480` wide and `44 * signals` tall — and `row_drawn=1` says the row
 The probe therefore needs a cache a **previous** run populated: it fires ~4.5 s in, before this run's
 first latch.
 
+`[events] live restored (…)` is the way *back*, read once per way into a file view — after a plain
+replay and after a group — and four of its fields are a **pair**: the value now, and the value the
+live view held before the file view opened over it. The probe captures that expectation itself
+(`capture_live_expectation()`, `App::dbg_live_*`) rather than asking the restore path for it: a
+reading taken from the mechanism under test asserts nothing. The window is set to 0.5 s just before
+the event is opened precisely so the pair can disagree — with the event's own span there would be
+nothing to tell "restored" from "untouched".
+
+Both lines are read a *later* step, not in the handler that pressed *Live*: the restore waits for the
+restarted client's first CONFIG, so it is performed by a tick ~900 ms on. `pending=0` is what says it
+happened; `gen=a/b` is the generation now against the one *Go live* read. A **stuck `pending=1`** is
+not a reading about the restore but about the stream behind it — the generation never moved, or the
+channel list came back empty, which is how a session file poisoned by a save taken during a group
+produced `pending=1 channels=0` and a live view with nothing on it.
+
 | field | value it must read | the defect a wrong reading names |
 | --- | --- | --- |
 | `n`, `stem`, `seq` | one entry per latch, named by its time and the run's counter | two events in one second overwriting each other, or a cache that is never written |
@@ -1032,6 +1049,9 @@ first latch.
 | `axis`, `marker`, `pane_box` (in `activated row0`) | `[-pre, +post]` of the event just opened, `marker=0.000`, and a `pane_box` close to `pane_w` | an opened event framed on something other than its own pin; a trigger line left **parked** (a large negative) rather than on the edge, which is a file opened without its marker; or a pane whose *rendered* width is 0 while the divider says 240 -- the position is what was asked for, `pane_box` is what the pane actually got, and a divider at 240 with a zero-width pane is still no pane |
 | `rows_kept`, `selected` (in `activated row0`) | `rows_kept=1` and `selected=N/N` -- the counts either side of the activation equal | the list **rebuilt** by the activation. It is the row *object* that is compared, not its index: a rebuilt list has a row 0 too, and only identity tells a list that was left alone from one that was torn down under the user's scroll position and their comparison selection. `mark_events_on_screen()` must rewrite the titles in place |
 | `replaying` (last line) | 0 | a replay with no way back: *Live* must start a fresh client and thread |
+| `window`, `trigger`, `channel`, `level` (in `live restored`) | each equal to its `(want …)` | the way back out of a file view discarding what the live view was set to. One wrong half names which writer won: a `window` that reads the **session file's** value is the deferred `apply_layout()` beating the restore; `trigger=0` is the toggle the file view switched off and nobody switched back; an empty or shifted `channel` is an index restored instead of a name, after a rebuild renumbered (or a group renamed) the channels; and a `level` that moved on its own is `rebuild_trigger_signals()` re-defaulting it because `trigger_level_touched` was not restored with the configuration |
+| `pending`, `gen` (in `live restored`) | `pending=0`, and the two generations different | the restore still waiting. It is gated on the stream's first CONFIG, so `pending=1` says the channel list the stored trigger name needs never arrived -- with `channels=0` behind it, a session file that enabled nothing |
+| `pinned`, `held`, `mode` (in `live restored`) | `pinned=0`, **or** `pinned=1` with `held=1` | a file's pin surviving the way back, which is a live view that cannot be navigated. `apply_time_window()` drops it; the second reading is the legitimate case -- a restored trigger that was *on* can latch again before the probe reads, and a held capture is pinned, correctly |
 | `pane_w` | the divider's position: 0 while the pane is closed, its remembered width (240 by default) while it is open | the pane reserving a column while closed (a paned hands its start child its minimum unless the position says otherwise), or a width that is not remembered |
 | `tick` | 1 in live mode, **0** once a file is on screen | the signal list still offering "acquire this signal" for samples that are already stored |
 | `window` (in `activated row0`) | the **event's** span -- the probe sets 0.5 s just before the click, so reading the event's span says opening it framed it | a replay that leaves the previous window alone, or one that restates it every frame instead of once |