Add workspaces, computers, bot memory and the bots queue

- Schema: workspaces (+ workspace_bots, workspace_computers), containers,
  computers, bot_computers, bots.memory, workspaces.system_prompt, and
  bots_queue as a bun-sqlite isQueue table
- Main computer (and its container record) ensured with the coordinator on
  signup, seed and /admin/bots; the coordinator's access to it is locked
- Effective computer access: direct grants plus workspace computers
- Full bot prompt: core instructions, workspace prompts, then memory;
  bots can rewrite their memory and system prompt
- Queue helpers on the native BunSQLite.queue API, plus a handler that
  heartbeats, serializes per computer, recovers after restarts, reports
  lost jobs, supports cancelling and pushes outcomes over the WebSocket
- Enable SQLite foreign keys at startup so schema cascades fire
- Prune finished jobs daily

Co-Authored-By: Claude Opus 5.5 <[email protected]>

src/utils/compose-bot-prompt.ts

@@ -0,0 +1,41 @@
+type WorkspacePrompt = {
+    name?: string | null;
+    system_prompt?: string | null;
+};
+
+type Params = {
+    system_prompt?: string | null;
+    memory?: string | null;
+    workspaces?: WorkspacePrompt[];
+};
+
+/**
+ * The full prompt a bot runs with (markdown): its own core instructions,
+ * then the shared context of each workspace it's in, then its memory.
+ * Empty parts are left out.
+ */
+export default function composeBotPrompt({
+    system_prompt,
+    memory,
+    workspaces = [],
+}: Params) {
+    const parts: string[] = [];
+
+    if (system_prompt?.trim()) {
+        parts.push(system_prompt.trim());
+    }
+
+    for (const workspace of workspaces) {
+        if (!workspace.system_prompt?.trim()) continue;
+
+        parts.push(
+            `# Workspace: ${workspace.name?.trim() || "Untitled"}\n\n${workspace.system_prompt.trim()}`,
+        );
+    }
+
+    if (memory?.trim()) {
+        parts.push(`# Memory\n\n${memory.trim()}`);
+    }
+
+    return parts.join("\n\n");
+}