Let workers ask each other through the coordinator in chatrooms

A worker asks for another bot's help with ask_crew. The coordinator
reads the request, asks the right bot (in a workspace, only its
members), and sends the answer back into the asking bot's
conversation, waking it. Each exchange is kept as a read-only
chatroom: listed in the main rail after the workspaces, or in the
workspace's rail for requests made there, with live status rows for
each bot while it's open and a Stop button.

Room sessions are hidden from every conversation list, other bots'
words reach the model fenced as data, and turns, nesting and open
rooms are capped. Closed rooms are pruned after a retention period
and past a cap per place (Settings > General).

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

src/data/app-data.ts

@@ -237,6 +237,27 @@ export const AppData = {
      * shortest gap between two runs, so a schedule can't flood the queue.
      */
     CronJobMaxPerBot: 20,
+    /**
+     * Chatrooms (a worker asking another through the coordinator): how many
+     * turns the coordinator gets in one room, how deep rooms may nest (a
+     * bot asked in a room asking someone else), how many rooms one bot may
+     * have open at once for a user, and how many the rail lists.
+     */
+    ChatroomMaxCoordinatorTurns: 6,
+    ChatroomMaxDepth: 2,
+    ChatroomMaxOpenPerBot: 3,
+    ChatroomCoordinatorMaxToolSteps: 6,
+    ChatroomRailLimit: 8,
+    /**
+     * Closed chatrooms are deleted after this many days, and past this many
+     * rooms in one place (a workspace, or bots' own chats) the oldest
+     * closed ones go: the defaults, each with the most an install may set
+     * (`chatroom_keep_days`, `chatroom_max_per_place`, Settings > General).
+     */
+    ChatroomKeepDays: 30,
+    ChatroomKeepDaysMax: 3650,
+    ChatroomMaxPerPlace: 200,
+    ChatroomMaxPerPlaceMax: 10000,
     CronJobMinIntervalMs: 5 * 60 * 1000,
     /**
      * Due schedules queued per tick of the `run-cron-jobs` cron.