ui: the signal list is the signals slide-over page, opened by a + badge or g

docs/claude/invariants-gtk-and-chrome.md

@@ -229,8 +229,8 @@ Part of [CLAUDE.md](../../CLAUDE.md). These are rules that cost a defect to lear
   replaced an `AdwViewSwitcher` over an `AdwViewStack`, whose four text tabs did not fit 320 px (and a source
   can add more); a source kind's own panels are slide-over pages, not dock sections. The reason is the one
   this trap teaches: sections competing for one 320 px column each left every one of them short of room, and
-  a scroller gives each its natural height. `m` and `g` scroll the dock to the cursors and to the signal list
-  (`dock_show_section()`). A *feature's* on/off is no longer a visibility at all -- the
+  a scroller gives each its natural height. `m` scrolls the dock to the cursors (`dock_show_section()`); the signal list is
+  not a dock section but the `signals` slide-over page, which `g` and the `+` badge open. A *feature's* on/off is no longer a visibility at all -- the
   **cursors'** toggle sets its pane's **body** insensitive -- the readout has nothing to show with the
   instruments off -- and the *body* and not the pane, because the pane's heading carries its own switch
   (see the next bullet). The **trigger's body is deliberately never disabled**: a trigger is configured
@@ -643,7 +643,8 @@ The `Help` submenu, the contextual help's "?" and the guided tour, and the traps
   and in a view with a `page_stack` a stop that names a page is kept when the stack is mapped -- a wrong
   page leaves the stack mapped, so the page switch reveals it, while a collapsed pane leaves it unmapped
   too and the stop is dropped. So the dock's stop is dropped in a window narrow enough to overlay it, and
-  the main window's tour is four steps there (`[toursurface] collapsed: ... steps=4`). The filter
+  the main window's tour is five steps there (`[toursurface] collapsed: ... steps=5`: the signals stop names
+  the `signals` slide-over page, which does not depend on the dock either). The filter
   lives in `tour_begin()`, not in each window's `start_tour()`, so the two windows cannot drift
   into two rules.
 - **The chooser's tour needs an overlay over its *whole* window, and `AdwWindow`'s content is