No way to save a preset or add a library folder from the interface (FR-STATE-030, FR-LIB-010)

[ErwanLegrand]

Two Must requirements whose user-facing mechanism does not exist. Both are currently carried as **PARTIAL** rows, which reads as verification debt; they are feature gaps.

FR-STATE-030 — save and recall a named preset

The requirement is that a user can save the current state as a named preset and recall it, interchangeably between the standalone app and the CLAP plugin.

• UiIntent (crates/namir-ui/src/host.rs) has exactly seven variants — SetParam, ResetParamToDefault, LibraryQueryChanged, LoadLibraryEntry, RescanLibraryRequested, CancelScanRequested, DismissNotice. None saves or loads a preset.
• AppHost::save_state / load_state exist in crates/namir-app/src/host.rs, and their own doc comment says outright that this is "not a UiIntent today". Their only caller in the tree is a test.
• namir-clap has no equivalent at all.

The document format is built and tested (namir-state, docs/04-state-and-preset-format.md, xtask preset). What is missing is any way for a user to reach it. "Save my tone and get it back" is the flagship story for the U2/U3 user classes.

FR-LIB-010 — nominate one or more library directories

Library roots are hard-coded to <config_dir>/Library by namir_worker::library::LibraryService::open_at/open_default. AppSettings has no roots field, and there is no add-root or remove-root intent. A user with their NAM captures and IRs anywhere else has no way to point Namir at them short of moving their files.

Scope

Both need the same shape of work: new UiIntent variants, new UiSnapshot fields, and bridges in both product shells (namir-app/src/host.rs and namir-clap/src/ui_host.rs, which implement UiHost independently by design). FR-LIB-010 additionally needs roots persisted in settings, and a directory picker — which must respect NFR-PORT-030's "no blocking dialog on an audio-affecting path" clause.

These are two of nine unbuilt user surfaces found in a sweep of the 66 partials; see also #26 (audio-device panel). Together they are large enough to be a milestone phase rather than exit-checklist items.

[ErwanLegrand]

A second, latent half of this that no ledger names — and it would bite the moment the save control in this issue gets wired.

namir-app never constructs a FileRef anywhere. A grep for FileRef across crates/namir-app/src/ returns zero occurrences.

So if a save-preset control were added tomorrow against the existing AppHost::save_state, the standalone would write a state document carrying no model or IR identity at all — and FR-STATE-060 ("recall the identity of the loaded model and IR files") and FR-STATE-070 (file-reference resolution) would be silently unmet in the shell that just gained the feature. The failure would look like a working save that quietly forgets which amp you had loaded.

This matters for sequencing: the FileRef construction is a prerequisite of the save path, not a follow-up to it.

A related gap on the plugin side, also currently untracked: crates/namir-clap/src/worker_jobs.rs and shared.rs set library_relative: None on every FileRef they build, because LibraryEntry does not carry root identity back. FR-STATE-070's first resolution candidate is therefore never recorded — in the shell where project portability matters most, since a DAW project is the thing that travels between machines.

Note this is not the gap FR-STATE-070's **PARTIAL** row names. That row names the missing "option to locate it manually". The library_relative hole is separate and unrecorded.

---

Generated by Claude Code

[ErwanLegrand]

PARTIAL. FR-STATE-030's surface is built; FR-LIB-010's is not. Leaving open on the second half.

Landed (#145, 63afed5, 7378f71). UiIntent gained SavePreset { name: String } and RecallPreset { path: PathBuf } (crates/namir-ui/src/host.rs:262, :270), and UiSnapshot gained presets. Both shells bridge them independently: crates/namir-app/src/host.rs:885/:918 and crates/namir-clap/src/ui_host.rs:204/:211. The layering is a name, not a path — where a named preset lives is a namir-platform question that D-5.1 puts out of namir-ui's reach — and the preset-location rule was hoisted into namir-platform (7378f71) so both shells agree without either crate knowing.

Two gaps inside the landed half, both recorded rather than left to be rediscovered:

• Overwrite protection is the confirm-by-repeat protocol (first SavePreset on an existing name writes nothing and reports a notice; the same name again writes), since NFR-PORT-030 rules out a modal on that row. namir-app implements it. namir-clap's ClapUiHost still saves on the first press — stated in UiIntent::SavePreset's own doc comment.
• docs/03-test-plan.md:90 still books FR-STATE-030 **PARTIAL**: no artifact loads an app-written .namirpreset into the plugin or a plugin-written blob into the app, so "interchangeable between the standalone application and the CLAP plugin" is unspanned in both directions.

Not landed — FR-LIB-010. Verified on the merged tree: UiIntent has no add-root or remove-root variant, namir-ui/src/host.rs contains no roots field, and both shells still open through LibraryService::open_at/open_default against the hard-coded <config_dir>/Library. docs/03-test-plan.md:59 states it in the same terms. A user with captures elsewhere still has no way to point Namir at them.

---

Generated by Claude Code