assistant: opening the canvas loads the preferred model

A preferred model that only took effect from the settings page did
nothing the next time another client had swapped it out. On this
desktop one model and one client run at a time, so opening the canvas
is when the assistant's model should come back: if the preferred one is
neither loaded nor loading, it is loaded, and the canvas header says so
until the router reports it in. The daemon still never asks for a model;
with no preference set nothing changes.

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

1 files changed, 7 insertions, 0 deletions

diff --git a/desktop/modules/assistant/README.md b/desktop/modules/assistant/README.md
index 07cc7ad..93b8507 100644
--- a/desktop/modules/assistant/README.md
+++ b/desktop/modules/assistant/README.md
@@ -19,6 +19,13 @@ 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.
 
+Opening the assistant canvas (SUPER+Home) loads the preferred model when
+another one is resident, and the canvas header reads "loading <model>…"
+until it is in. This desktop runs one model and one client at a time, so
+opening the assistant is when its model should come back; the daemon still
+never asks for a model itself. With no preferred model set, nothing is
+swapped.
+
 The daemon reads all of this only at startup, so after a change the page
 says so and offers Restart, which runs `assistant.sh restart`; a daemon that
 does not come back shows the script's status, whose log tail says why.