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/dict/bot-queue-dict.ts

@@ -38,6 +38,13 @@ export type BotJobUpdateKind = (typeof BotJobUpdateKinds)[number]["value"];
  */
 export const BotReplyJobTitle = "Thinking";
 
+/**
+ * The bot's status line while a task runs. Everyone who sees the bot sees
+ * it, so it never names the task: each user sees their own task's title
+ * and steps in their conversation.
+ */
+export const BotTaskStatusLine = "Working on a task";
+
 /**
  * The bot's status line while its job waits for a rate-limited model.
  */