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/functions/backend/db/cron-jobs/fire-cron-job.ts

@@ -48,6 +48,7 @@ export default async function fireCronJob({ cron_job, now = Date.now() }: Params
         }
 
         const session = await ensureBotSession({
+            user_id: cron_job.user_id!,
             bot_id: cron_job.bot_id!,
             workspace_id: cron_job.workspace_id || null,
         });
@@ -57,7 +58,6 @@ export default async function fireCronJob({ cron_job, now = Date.now() }: Params
             (
                 await grabBotComputers({
                     bot_id: cron_job.bot_id!,
-                    user_id: cron_job.user_id!,
                     workspace_id: cron_job.workspace_id || null,
                 })
             )[0]?.id;