Add MCP servers and custom tools for bots

Two new settings pages, MCPs and Tools. Super admins define them; super
admins and admins attach them to bots, to workspaces (every bot there),
or to every bot. Bots get them in chat replies and tasks.

- Custom tools: a JSON-schema of arguments plus an HTTP request, a script
  on the bot's computer, or a prompt, templated with {{args.x}} and
  {{env.KEY}}, secrets redacted from results.
- MCP servers: remote (URL and headers) or stdio commands run on the host
  with a setup command and an isolated env, in a per-process pool. Tools
  are listed into a cache and connect on first call.
- Add, edit, access and try open in modals.
- Markdown, JSON and command fields use twui's AceEditor (CodeEditor),
  its scripts loaded on demand.

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

src/data/app-data.ts

@@ -181,6 +181,22 @@ export const AppData = {
      * One MCP tool call gives up after this long without progress.
      */
     McpToolTimeoutMs: 5 * 60 * 1000,
+    /**
+     * MCP servers set up in Settings, under MCPs: a stdio server runs in
+     * `DATA_DIR/<McpDataDir>/<id>` (its setup installs there, so it
+     * survives updates), its setup command may take `McpSetupTimeoutMs`,
+     * and it's stopped after `McpStdioIdleMs` without a call.
+     */
+    McpDataDir: "mcp",
+    McpSetupTimeoutMs: 10 * 60 * 1000,
+    McpStdioIdleMs: 10 * 60 * 1000,
+    /**
+     * A custom tool (Settings, under Tools) gives up after its own timeout,
+     * `CustomToolDefaultTimeoutMs` when it has none, never past
+     * `CustomToolMaxTimeoutMs`.
+     */
+    CustomToolDefaultTimeoutMs: 60 * 1000,
+    CustomToolMaxTimeoutMs: 10 * 60 * 1000,
     /**
      * `search_computers`: how long the command may run on each computer,
      * and how much of each computer's output the bot reads.