namir-ui: the intent round-trip test bypasses the frame path it claims to cover

[ErwanLegrand]

crates/namir-ui/src/app.rs:396-414

dispatched_intents_from_a_frame_reach_the_host claims in its doc comment to verify a SetParam "round-trips to the host via NamirUi::frame's real UiHost::dispatch path", but the body calls namir_ui.host.dispatch(...) directly -- no frame is run, render is never entered, and the assertion only re-tests RecordingHost's Vec::push. The one glue path it purports to cover (render -> collect intents -> dispatch) is untested.

Fix: drive headless_frame with a click on a real control and assert the intent landed in host.dispatched.

[ErwanLegrand]

Fixed in #145 (6644aeb). dispatched_intents_from_a_frame_reach_the_host (crates/namir-ui/src/app.rs:691) no longer calls host.dispatch itself. It runs real NamirUi::frame passes over a shared egui::Context: frame 0 renders and locates the gate.threshold_db control by the value text render painted, frame 1 presses on it and asserts nothing is dispatched (a press with no movement is not a change), frame 2 drags right and asserts exactly one SetParam for that key landed in host.dispatched with a raised value.

The glue path is now the thing under test — dropping the dispatch call from frame() fails it, which the old body survived.

---

Generated by Claude Code