Cleanup confirms and refreshes; projects switch sessions in place; explain verify.sh, headroom and Mouse-1

docs/SESSIONS.md

@@ -71,3 +71,24 @@ on.
 - `factory`, `office-test-1` and the `harness-demo-*` sessions have one pane each and are
   detached — they *are* the junk, but they are indistinguishable from a deliberately parked
   session by age alone. Hence the pattern, and hence the confirmation.
+
+## Switching sessions, and what "on another machine" means
+
+A session lives on a daemon, and a daemon runs on one machine. Where you *sit* does not matter:
+a client on `.27` can drive a session whose daemon is on `.13`, and that is exactly what happens
+here. So the phrase "a project on another machine" really means "a session on another daemon".
+
+TUIOS has a verb for moving an attached client:
+
+```
+tuios call switch-session '{"name":"office","host":"nixos-desktop"}'
+```
+
+- `name` is the session to show.
+- `host` may be omitted for the local daemon, or named for a machine in the client's `[hosts]`
+  table. A machine that is not in that table cannot be reached this way; attach by hand then.
+
+`Project>project` → **projects** now uses this. Every adopted project is listed with its
+session, machine and folder; `enter` asks once and then switches the client in place. A
+project whose session is on a daemon your client does not know is still listed, and the
+confirmation says which machine it needs.