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/admin/bots/[bot_id]/(partials)/message-thread.tsx

@@ -14,6 +14,10 @@ type Props = {
      * The latest step of the bot's active task, shown while it works.
      */
     progress?: string | null;
+    /**
+     * This session has an active task.
+     */
+    has_task?: boolean;
 };
 
 /**
@@ -22,7 +26,7 @@ type Props = {
  * While the bot works on a reply or a task, a status row sits under the
  * last one.
  */
-export default function MessageThread({ bot, messages, progress }: Props) {
+export default function MessageThread({ bot, messages, progress, has_task }: Props) {
     const groups = groupMessages({ messages });
 
     return (
@@ -40,7 +44,12 @@ export default function MessageThread({ bot, messages, progress }: Props) {
                         group={group}
                     />
                 ))}
-                <BotThinkingRow bot={bot} progress={progress} />
+                <BotThinkingRow
+                    bot={bot}
+                    progress={progress}
+                    awaiting_reply={messages[messages.length - 1]?.author == "user"}
+                    has_task={has_task}
+                />
             </Stack>
         </Stack>
     );