namir-ui: no save or recall intent exists, so FR-STATE-030 cannot close

[ErwanLegrand]

crates/namir-ui/src/host.rs:262-293 and src/app.rs:55-59

FR-STATE-030 is a Must ("the user shall be able to save the current state as a named preset and recall it"), and namir-ui is the only GUI. UiSnapshot::unsaved_changes is rendered as "* unsaved changes", but UiIntent has no save, recall, or revert variant -- so the view surfaces a dirty flag the user has no control to resolve. namir-app documents the hole from its side (namir-app/src/host.rs:461: "not a UiIntent today").

Fix: add SavePreset/RecallPreset intents plus the two controls.

[ErwanLegrand]

Fixed in #145 (63afed5, with the recalled-name display corrected in a2e28db).

UiIntent gained SavePreset { name } and RecallPreset { path } (crates/namir-ui/src/host.rs:262, :271), plus UiSnapshot::presets as PresetSummary { name, path } (host.rs:136). The controls are preset_controls (crates/namir-ui/src/app.rs:148-202) — a name box, a Save button disabled on an empty name, and a recall combo listing whatever the host enumerated — rendered from render at app.rs:68. An overwrite is guarded without a modal: the first SavePreset naming an existing preset writes nothing and reports a notice, the same name dispatched again confirms it (host.rs:253-256).

Both shells implement it rather than one: crates/namir-app/src/presets.rs and crates/namir-clap/src/presets.rs, with the location rule hoisted into namir-platform (7378f71) so the two cannot drift. naming_a_preset_and_pressing_save_dispatches_a_save_intent (app.rs:873) drives it through a real frame.

---

Generated by Claude Code