fixed plot flicker, measurement cost and toolbar icons

The flicker ("no data" at no constant frequency, worse with the measurements
and cursors panes up) was a torn read of the window's first stamp: acquire()
pins the window to the ring's oldest slot, and reading it at paint time races
the producer lapping it, returning a stamp one ring span too new. x0() is the
origin every trace point is reconstructed from, so one torn read produced a
refused neighbours(), a filter that dropped three quarters of the points, and
a polyline shifted off its axis. It is cached by acquire() under the lock now.

EventSeries::neighbours() answered from the (x - x0)/dx grid, whose drift from
the real arrival stamps arrives as a constant offset in seconds -- a doubling
share of the screen per zoom step, which is the "zooming into a held event
clips it more from the left" report. Both series binary-search the stamps now.

The measurements pane went through the LOD pyramid rather than reading its
window raw (19.7 ms per recompute to 1.2 ms, 0.1% of a 2 M-sample window) and
recomputes on a cadence; the math engine lost a per-slot heap allocation, a
per-sample source lookup by name and a fetch_add that cost more than the
arithmetic it counted.

The cursors pane's mix mode drew a line per *named* slot, so a slot holding a
signal that can never produce a channel -- the stream's timestamp -- got a row
that could only read "--", and such names were re-saved every session. It
counts bound traces now and apply_layout() refuses them.

Four toolbar icons are drawn for this app and compiled in as a GResource: the
stock ones were a record dot for the trigger and three magnifiers for cursors,
measurements and math.

New probes and dump lines for all of it (trace ink, measure cost, math cost,
event zoom, toolbar icons); README and CLAUDE.md record what they cure.

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

src/channel.hpp

@@ -102,6 +102,19 @@ class ChannelBuffer final : public plot::data::Series {
   f64 epoch_ = 0.0;
   f64 dt_ = 1.0;
   u64 published_ = 0;
+  /// The stamp of the window's **first** sample, read once by `acquire()` -- which runs on the
+  /// consumer under `ScopeModel::mutex()`, the same lock the producer's pushes hold, so the
+  /// slot cannot be overwritten under the read. Everything else on this object is read at
+  /// *paint* time with no lock, and this one slot is the ring's oldest: the one the producer is
+  /// about to overwrite. Reading it there returned a stamp a whole ring-span too new whenever
+  /// the producer lapped it between the bounds check and the copy -- and `x0()` is the origin
+  /// the renderer reconstructs every trace point from (`gather[i] + series.x0()`), so one such
+  /// read moved the entire polyline a ring-span off its axis (an invisible trace) or, caught
+  /// inside the renderer's increasing-suffix filter, made it drop most of the points. That is
+  /// the "live plot flickers as if there were no data" defect. The cached value is also the
+  /// *right* answer rather than merely a stable one: it is the stamp sample `window_base`
+  /// actually carries, where the clamp answered with whatever slot happened to be oldest now.
+  f32 window_x0_ = 0.0f;
   plot::data::MinMaxPyramid pyramid_;
 };