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/bots-queue/cancel-bot-job.ts

@@ -9,7 +9,7 @@ type Params = {
 };
 
 /**
- * Cancels one of the user's pending or running jobs. It's marked failed
+ * Cancels a pending or running job in one of the user's conversations. It's marked failed
  * with `BotJobCancelledError`; a running handler finds out on its next
  * `updateBotJob` (which returns false) and stops. Its task is closed.
  */
@@ -19,7 +19,7 @@ export default async function cancelBotJob({ user_id, job_id }: Params) {
     const res = await BunSQLite.sql<BUN_SQLITE_COBBLE_BOTS_QUEUE>({
         sql: `UPDATE bots_queue SET status = 'failed', last_error = ?, locked_at = NULL, locked_by = NULL, finished_at = ?, updated_at = ?
             WHERE id = ? AND status IN ('pending', 'processing')
-            AND bot_id IN (SELECT id FROM bots WHERE user_id = ?)
+            AND session_id IN (SELECT id FROM bot_sessions WHERE user_id = ?)
             RETURNING *`,
         values: [BotJobCancelledError, now, now, job_id, user_id],
     });