assistant: Load no longer changes the preferred model

Load set the preference as well as swapping the model in, so loading a
model from the settings page for any reason made it the assistant's
model too: after loading Qwen there, the canvas kept Qwen instead of
bringing the preferred Gemma back. Load and Prefer are now separate
buttons: Load swaps a model in now and leaves the preference alone, and
Prefer only records which model the canvas loads when it opens.

The canvas header also showed a stale model name after a swap; it now
takes the model from the daemon's ctx event, which carries it from
desktop-assistant f9d4644 on.

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

1 files changed, 5 insertions, 3 deletions

diff --git a/desktop/modules/assistant/README.md b/desktop/modules/assistant/README.md
index 93b8507..004ec05 100644
--- a/desktop/modules/assistant/README.md
+++ b/desktop/modules/assistant/README.md
@@ -15,9 +15,11 @@ to `<name>.toml.off`, which the daemon's `*.toml` glob skips.
 The page also lists llama-server's models with their state. The daemon
 always answers with whichever model is loaded and never asks for one, so
 it never swaps a model out from under another client. Load is the
-deliberate swap: it saves that model as the preferred one (in `Prefs`)
-and asks the router to load it now, polling `/v1/models` until it reports
-`loaded`. Prefer marks the already-loaded model as preferred.
+deliberate swap: it asks the router to load that model now, polling
+`/v1/models` until it reports `loaded`, and leaves the preference alone.
+Prefer is the other, separate choice: the model the assistant should use,
+saved in `Prefs`. A first version made Load also set the preference, so a
+model loaded for another client became the assistant's too.
 
 Opening the assistant canvas (SUPER+Home) loads the preferred model when
 another one is resident, and the canvas header reads "loading <model>…"