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/harness/tools/bot/extensions/describe-extension-access.ts

@@ -0,0 +1,15 @@
+type Params = {
+    all_bots: boolean;
+    bot_ids: number[];
+    workspace_ids: number[];
+};
+
+/**
+ * Who gets an extension, as refs the chat renders as chips.
+ */
+export default function describeExtensionAccess({ all_bots, bot_ids, workspace_ids }: Params) {
+    const bots = bot_ids.map((id) => `[bot:${id}]`).join(", ") || "none";
+    const workspaces = workspace_ids.map((id) => `[workspace:${id}]`).join(", ") || "none";
+
+    return `${all_bots ? "every new bot gets it; " : ""}bots: ${bots}; workspaces: ${workspaces}`;
+}