docs: events in the dock and on its page

The dock's Events block, the events slide-over page, the availability-rule deviation, the probe lines and the removal of the left pane are described; the false remembered-width claim is gone.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

docs/claude/verification.md

@@ -433,14 +433,14 @@ precedent, not an exception.
   config that has seen the first-run tour, which would close the page it opens (see the next-but-one bullet).
   The reading's own entry is in `probe-readings.md`. (Probe name `dock_section_probe`; the variable and the
   `[side-tab-probe]` tag keep their old names so existing scripts keep working. The measurements used to be a
-  dock section the probe scrolled out of view, with padding; the dock now holds only readouts, so there is
+  dock section the probe scrolled out of view, with padding; the dock now holds the readouts and the Events block, so there is
   no scroll and no padding.)
 - `UDPSCOPE_PROBE_CURSORS_MS` and `UDPSCOPE_PROBE_MEASURES_MS` also print the dock's copy of what they read:
   a `dock cursors:` line after every `[cursors-probe]` report and a `dock measures:` line at the
   measures probe's added / settled / final stops. **`same_text=1` on every one** is the assertion that the
   dock and the page show one string; `fits=1` that the Readouts box is no wider than the dock. Entries in
-  `probe-readings.md`. The exit chain also prints one `[readouts]` line (pages registered, the dock's one
-  child, the dock's width, the pages' sensitivity, whether the stream has signals) on every exit-dump run.
+  `probe-readings.md`. The exit chain also prints one `[readouts]` line (pages registered, the dock page's three
+  children, the dock's width, the pages' sensitivity, whether the stream has signals) on every exit-dump run.
 - `UDPSCOPE_PROBE_DOCK_SESSION_MS=2500` with `UDPSCOPE_EXIT_AFTER_MS=8000` -- the session file's `dock` key,
   end to end: the dock hidden, saved and reloaded; shown again; and a file from the previous version
   (`side_tab = "measure"`, no `dock`) loaded without an error. Three `[dock-session]` lines, each `ok=1`;
@@ -721,41 +721,50 @@ as distinct from the fault injection below, which exercises ingest:
   leg of it (`title='Opening <basename>' detail='reading the recording'`, before `waveform loaded:`).
   A run that names its source with `--server` prints **no** `loading:` line at all: every other probe
   here is on that path and must stay on it.
-- **The event cache round-trips, and only where it is available.** `UDPSCOPE_PROBE_EVENTS_MS` reads
-  the pane's availability first, in the state the app starts in -- `[events] live: button_visible=0
-  pane=0 recording=1`, **no pane and no button without trigger mode** -- then turns trigger mode on
-  through the real toggle (`[events] after trigger on: button_visible=1 pane=0`: the button appears,
-  the pane stays collapsed) and clicks the button, waits for a latch, then reads the cache and replays
-  the newest event through the pane's own row:
+- **The event cache round-trips, and only where it is available.** `UDPSCOPE_PROBE_EVENTS_MS` needs a
+  config that has seen the tour (it opens a slide-over page) and a throwaway `XDG_CACHE_HOME`. It reads the
+  availability first, in the state the app starts in -- `[events] live, recording off: available=0
+  dock_sensitive=0 page_sensitive=0 page=none` (the dock block and the page agree, both insensitive and neither
+  hidden) -- then switches recording on (`available=1 dock_sensitive=1 page_sensitive=1`; **trigger mode is not
+  a condition**, and the line after the trigger is turned on reads the same), opens the `events` page with
+  `open_events_page()` (`page=events`, `[events] open alone: page=events page_box=347`), waits for a latch, then
+  reads the cache and replays the newest event through the page's own row:
   `[events] dir=… n=1 newest: dur=2.000000 pre=1.000000 post=1.000000 edge=… signals=4 samples=20001
-  rate=10000 seq=1 thumb_bytes=230454 recorded=1 pane=1`, then
-  `[events] activated row0: replaying=1 thumbnail=1 thumb_size=108x36 thumb_visible=1` (the size is
-  what says the picture is *on screen*: a paint-able alone is not), `[events] replayed: channels=4
-  samples=20001 replaying=1 waveform=1` and `[events] live again: replaying=0 waveform=0`. It ends on
-  the pane's availability, through the trigger panel's switch: `[events] recording off, trigger off` and
-  `[events] recording off, trigger on` -- once the cache holds events (the probe's own run has written
-  some by this point) both read `button_visible=1 pane=1 recording=0`, because a button that shows the
-  cache must not go away with the switch that wrote it; against an *empty* cache the same two lines read
-  `button_visible=0 pane=0`, which is the empty column the item exists to prevent. **`samples` must equal the
-  export's row count for the same window** (`20001` for a 2 s event at 10 kS/s), `thumb_bytes` must be
-  a real BMP (`54 + 480*160*3`-ish, i.e. hundreds of kB, not 0), `thumbnail` must be 1 (the row loaded
-  the picture) and the last line must read `replaying=0` -- a replay with no way back is a one-way
+  rate=10000 seq=1 thumb_bytes=230454 recorded=1 page=1 plot_w_stable=1 plot_w=756/756` (**`plot_w_stable=1`**: the
+  first latch did not move the plot, which the old pane did), then
+  `[events] activated row0: replaying=1 page=events … thumbnail=1 thumb_size=138x46 thumb_visible=1` (the size is
+  what says the picture is *on screen*: a paint-able alone is not), the dock's reading of the same cache --
+  `[events] dock events: rows=N pane_rows=N same_titles=1 sensitive=1 dock_w=268 on_screen=1 … at=after pane
+  replay` -- then **one click on a dock row**, `[events] dock replay: clicked=1 replaying=1 waveform_changed=1`,
+  and the dock read again (`marked=1`, `expected_marked=1`: exactly one filled marker, on the replayed record),
+  `[events] replayed: channels=4 samples=20001 replaying=1 waveform=1` and `[events] live again: replaying=0
+  waveform=0`. It ends on the availability, through the trigger panel's switch: `[events] recording off,
+  trigger off` and `[events] recording off, trigger on` -- once the cache holds events (the probe's own run has
+  written some by this point) both read `available=1 dock_sensitive=1 page_sensitive=1`, because a block that
+  shows the cache must not go away with the switch that wrote it; against an *empty* cache (and on the E-1608,
+  which never latches) the same two lines read `0 0 0` with the page still open -- insensitive, never hidden.
+  **`samples` must equal the export's row count for the same window** (`20001` for a 2 s event at 10 kS/s),
+  `thumb_bytes` must be a real BMP (`54 + 480*160*3`-ish, i.e. hundreds of kB, not 0), `thumbnail` must be 1 (the
+  row loaded the picture) and the last line must read `replaying=0` -- a replay with no way back is a one-way
   door. It then **waits for a second latch** (bounded: twelve retries) and drives the two group layouts
   through the buttons: `[events] compare buttons: cached=2 selected=2 compare=1 accumulate=1` (the
   buttons read the selection), `[events] halve`… `[events] halves a_first=20001 a_second=0 b_first=0
   b_second=20001` -- **the two halves of the ring, and the reading that says a comparison's gap is a
   gap: the first event's channel is finite only in the first half and the second's only in the second**
   -- `[events] compare: kind=1 rows=4 channels=8 samples0=40002 traces0=2 traces1=2 window=4.000
-  recording=1 pane=1` (`samples0` must be exactly the stamps pushed, **not more**: a live producer left
-  running pushes its own four signals into the group's eight channels), `[events] compare plots:
+  recording=1 page=events` (`samples0` must be exactly the stamps pushed, **not more**: a live producer left
+  running pushes its own four signals into the group's eight channels), the dock line `members=2 … at=comparison
+  up` (the hollow markers on the group's members, which only the dock shows), `[events] compare plots:
   area_b=1 rows_a=1 rows_b=1 x_a=[-2.000,0.000] x_b=[-2.000,0.000] same_x=1` (the second plot exists, is
   on screen, mirrors the row count, and both are on one x window), then the sync -- the probe sets a y
   range nobody would arrive at by accident on the *first* plot and reads the second a few frames later:
   `[events] compare sync: y_a=-3.500 y_b=-3.500 mirrored=1` -- and `[events] accumulate: kind=2 rows=1
   channels=8 samples0=33045 selected=2 traces0=8 window=2.000` (`traces0=8`: the four signals the layout
   holds plus one layer each for the second event, **in the same row**, which is what an accumulation
-  means). Run it with a throwaway
-  `XDG_CACHE_HOME` and `UDPSCOPE_EXIT_AFTER_MS` long enough for the second latch (20 s).
+  means). The exit dump adds `events pane: compare=1 accumulate=1 list=1 nested=1` and the readouts line's
+  `dock_children=3`. Run it with a throwaway
+  `XDG_CACHE_HOME` and `UDPSCOPE_EXIT_AFTER_MS` long enough for the second latch (20 s). The dock row cap
+  (24) is only exercised by a cache that has filled past it: `max_ok=1`.
 - **A waveform round-trips.** Export from a live run (`UDPSCOPE_EXPORT_MS` with
   `UDPSCOPE_EXPORT_PATH`, against the mock at 10 kS/s), then open that file with `--open` and an
   exit dump. The load must print