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/relay-new-job-updates.ts

@@ -9,15 +9,16 @@ type Params = {
 
 /**
  * Pushes `server:bot-job-update` for every job step newer than `after_id`
- * to its owner's sockets on this process. Returns the newest id read.
+ * to the sockets on this process of the user whose conversation the job
+ * is in. Returns the newest id read.
  */
 export default async function relayNewJobUpdates({ after_id, users }: Params) {
     const rows =
         (
             await BunSQLite.sql<BotJobUpdateData & { user_id: number }>({
-                sql: `SELECT u.*, q.task_id, q.session_id, b.user_id FROM bots_queue_updates u
+                sql: `SELECT u.*, q.task_id, q.session_id, s.user_id FROM bots_queue_updates u
                     JOIN bots_queue q ON q.id = u.bots_queue_id
-                    JOIN bots b ON b.id = u.bot_id
+                    JOIN bot_sessions s ON s.id = q.session_id
                     WHERE u.id > ? ORDER BY u.id ASC LIMIT 500`,
                 values: [after_id],
             })