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/pages/api/admin/bots/send-message.ts

@@ -17,8 +17,8 @@ import type {
 } from "@moduletrace/bunext/types";
 
 /**
- * Posts a message from the session user to one of their own bots, in its
- * own chat or in a workspace it's in, and queues the bot's reply, which
+ * Posts a message from the session user to a bot they chat with, in its
+ * own chat or in a workspace, and queues the bot's reply, which
  * arrives over the WebSocket. The message goes in the conversation's
  * active session (the next one when it's full) and also to the user's
  * other open tabs. Files are uploaded first (`upload-attachment`) and
@@ -57,6 +57,7 @@ export const handler: BunextAPIRouteHandler<APIResponseObject> = async ({
 
         const media = await grabAttachableMedia({ user_id: Number(user.id), media_ids });
         const session = await ensureBotSession({
+            user_id: user.id,
             bot_id: bot.id,
             workspace_id: conversation.workspace_id,
             rollover: true,