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/pages/admin/bots/[bot_id]/(partials)/markdown-link.tsx

@@ -5,6 +5,7 @@ import {
     BotRefHrefPrefix,
     ComputerRefHrefPrefix,
     FileRefHrefPrefix,
+    ProposalRefHrefPrefix,
     TakeOverRefHrefPrefix,
     WorkspaceRefHrefPrefix,
 } from "@/src/utils/link-computer-refs";
@@ -13,6 +14,7 @@ import BotRefChip from "./bot-ref-chip";
 import ComputerRefChip from "./computer-ref-chip";
 import FileRefChip from "./file-ref-chip";
 import FolderRefChip from "./folder-ref-chip";
+import ProposalRefChip from "./proposal-ref-chip";
 import TakeOverChip from "./take-over-chip";
 import WorkspaceRefChip from "./workspace-ref-chip";
 
@@ -21,7 +23,8 @@ import WorkspaceRefChip from "./workspace-ref-chip";
  * becomes its switch button, a take-over request a button that opens the
  * computer, a bot it named a link to that bot's conversation, a workspace
  * a link to that workspace, a file it saved a chip that downloads it, a
- * folder it named a chip that opens it in the files browser; anything else
+ * folder it named a chip that opens it in the files browser, an MCP server
+ * or tool it proposed a chip that opens the confirm card; anything else
  * opens in a new tab.
  */
 export default function MarkdownLink({ href, children }: ComponentProps<"a">) {
@@ -64,6 +67,12 @@ export default function MarkdownLink({ href, children }: ComponentProps<"a">) {
         if (file_id) return <FileRefChip file_id={file_id} />;
     }
 
+    if (href?.startsWith(ProposalRefHrefPrefix)) {
+        const proposal_id = Number(href.slice(ProposalRefHrefPrefix.length));
+
+        if (proposal_id) return <ProposalRefChip proposal_id={proposal_id} />;
+    }
+
     const folder_ref = parseFolderRefHref({ href });
 
     if (folder_ref) return <FolderRefChip spec={folder_ref.spec} path={folder_ref.path} />;