ui: the events list is a slide-over page; the left pane, its divider and the header toggle are gone

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

src/ui_trigger.cpp

@@ -594,10 +594,10 @@ void on_trigger_toggled(GtkToggleButton* button, gpointer user) {
   // unreachable exactly when a user wanted to change them.) What that costs is the reading: the
   // `trigger panel sensitive` line is now a regression guard, and a `0` there means the
   // configuration has been locked out again.
-  // The event-history button is part of trigger mode and the pane it opens is *on demand*; leaving
-  // trigger mode takes the button away and collapses the pane, so going back to streaming is not a
-  // column of stale events beside the plot. Recording is the other half of that answer, so this is
-  // `sync_events_availability()`'s call and not the trigger's alone.
+  // The dock's Events block and the `events` page follow what is recorded or cached, not trigger mode
+  // alone: leaving trigger mode does not empty the cache, and a replay is not in trigger mode at all.
+  // Recording is the other half of that answer, so this is `sync_events_availability()`'s call and not
+  // the trigger's alone.
   sync_events_availability(*app);
   // Arming is a *runtime* control: with trigger mode off there is no engine to arm, and the arm buttons
   // are the one part of this pane that is not a setting. (The body itself stays live -- see above.) Both
@@ -721,7 +721,7 @@ GtkWidget* build_trigger_panel(App& app) {
   gtk_switch_set_active(GTK_SWITCH(app.events_record_switch), app.event_recording);
   gtk_widget_set_tooltip_text(app.events_record_switch,
                               "keep every triggered acquisition in the event cache, with a "
-                              "picture of each; the history button goes with it");
+                              "picture of each; the dock's Events block and page follow it");
   g_signal_connect(app.events_record_switch, "notify::active",
                    G_CALLBACK(on_events_record_toggled), &app);
   // Not `row_for()`: that expands its child, which is what a spin button wants and what a switch must not