Let the coordinator manage skills, MCP servers and tools, behind a confirm card

- Coordinator tools in its own chat (super admin only): list_extensions,
  set_extension_access, delete_extension, and update_skill /
  update_mcp_server / update_custom_tool for what can't change where
  anything is sent (on/off, names, arguments, left-out tools)
- Adding a skill, MCP server or tool, or changing a skill's words, a
  server's URL or headers or a tool's kind or config, goes through
  propose_skill / propose_mcp_server / propose_custom_tool: stored in
  extension_proposals with the bot's background check, shown as a
  [proposal:ID] chip that opens a card with Confirm and Reject
- The card's facts are worked out by the app from what Confirm saves: the
  host, every {{env.KEY}} and whether it's saved, the config; for a skill
  its links, hosts, tool names, mentions of secrets and a diff against
  the saved runbook
- Confirming decides once and checks again; a server or tool missing a key
  is saved switched off, and the outcome is posted to the bot in chat
- Never from a bot: stdio servers, a URL whose host a template decides,
  envs in a prompt tool, a key's value

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

src/dict/custom-tool-dict.ts

@@ -64,19 +64,28 @@ export const ReservedToolNames = [
     "create_schedule",
     "create_workspace",
     "delegate_task",
+    "delete_extension",
     "delete_schedule",
+    "list_extensions",
     "list_schedules",
     "load_skill",
+    "propose_custom_tool",
+    "propose_mcp_server",
+    "propose_skill",
     "report_run_failed",
     "search_computers",
     "send_message",
     "set_bot_workspace_instructions",
+    "set_extension_access",
     "set_picture",
     "set_workspace_computer",
     "start_task",
+    "update_custom_tool",
     "update_instructions",
+    "update_mcp_server",
     "update_memory",
     "update_schedule",
+    "update_skill",
     "update_workspace",
 ] as const;