namir-clap: GUI meters bind to a telemetry reader captured once at editor-open

[ErwanLegrand]

crates/namir-clap/src/gui.rs:170, src/ui_host.rs:64, 101

set_parent snapshots telemetry_reader() at editor-open time. Two consequences:

• A host that opens the editor before the first activate() (common) gets None, so drain_meters returns at its first line for the editor's entire life and both meters read -inf permanently.
• After any deactivate/reactivate -- including the restart the plugin itself requests for latency -- activate installs a fresh ring (audio.rs:156-159) while the GUI keeps draining the retired one, freezing the meters.

Untested: every ClapUiHost test either passes None or wires a hand-made ring directly, so neither transition is exercised.

Fix: add a generation counter bumped by set_telemetry_reader, and have drain_meters re-clone from SharedInner when its own generation is behind.

[ErwanLegrand]

Fixed in #145 (63afed5).

SharedInner gained telemetry_generation, bumped after every set_telemetry_reader (crates/namir-clap/src/shared.rs:145-148, :245-253, with the store ordered before the bump so a reader seeing the new generation never fetches the retired ring). ClapUiHost::rebind_telemetry_if_stale (ui_host.rs:113-122) re-clones when its own generation is behind and resets the held peaks with it; drain_meters calls it first (ui_host.rs:135). gui.rs no longer snapshots a reader at set_parent (gui.rs:168).

Both transitions are now tested rather than sidestepped: an_editor_opened_before_the_first_activation_still_gets_meters (ui_host.rs:373) and a_reactivation_rebinds_the_meters_to_the_new_ring (ui_host.rs:397).

---

Generated by Claude Code