Share one crew across the install, keep user memory per user

Bots, workspaces and computers now belong to the install. Users reach
workers only through bot_users (assigned by a super admin or admin) and
workspace_users; the coordinator and main computer are one per install,
and only the super admin sees the coordinator. Conversations are per
user (bot_sessions.user_id), jobs run for the session's user, and live
updates go only to who should see them.

A bot's core memory is now general knowledge shared by every user it
works for; what it learns about a user lives in bot_user_memories.

One-off scripts move existing installs over: move-bot-memory-to-owners
(run first), then share-crew.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

src/live-relay/index.ts

@@ -10,8 +10,8 @@ import type { LiveRelayCursor } from "./types";
 /**
  * Keeps this process's sockets current with work done anywhere: every
  * `AppData.LiveRelayPollMs` it reads new bot messages, new job steps and
- * changed bots from the database and pushes them to their owners'
- * sockets here. The process that did the work pushes at once
+ * changed bots from the database and pushes them to the sockets here
+ * of the users they're for. The process that did the work pushes at once
  * (`pushBotNotice`); this catches the rest, e.g. a job run by another
  * server on the same database. Clients ignore what they already have.
  * Runs in every server process, ungated.