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/utils/link-computer-refs.ts

@@ -37,11 +37,18 @@ export const FileRefHrefPrefix = "#file-";
  */
 export const FolderRefHrefPrefix = "#folder-";
 
+/**
+ * The link target a proposal ref (`proposalRef`) becomes, e.g.
+ * `#proposal-7`. The chat renders it as a chip that opens the card where
+ * the super admin confirms or rejects the MCP server or tool.
+ */
+export const ProposalRefHrefPrefix = "#proposal-";
+
 /**
  * Turns every computer ref (`[computer:3]`) and take-over ref
  * (`[take-over:3:browser]`), bot ref (`[bot:3]`), workspace ref
- * (`[workspace:2]`), file ref (`[file:12]`) and folder ref
- * (`[folder:computer:3:seo/raw]`) in a message into a markdown link, so it
+ * (`[workspace:2]`), file ref (`[file:12]`), folder ref
+ * (`[folder:computer:3:seo/raw]`) and proposal ref (`[proposal:7]`) in a message into a markdown link, so it
  * survives markdown rendering as a link the chat can swap for a button,
  * chip or download.
  *
@@ -64,6 +71,10 @@ export default function linkComputerRefs({ text }: { text: string }) {
             /\[workspace:(\d+)\](?!\()/g,
             (_, id: string) => `[workspace ${id}](${WorkspaceRefHrefPrefix}${id})`,
         )
+        .replace(
+            /\[proposal:(\d+)\](?!\()/g,
+            (_, id: string) => `[proposal ${id}](${ProposalRefHrefPrefix}${id})`,
+        )
         .replace(/\[file:(\d+)\](?!\()/g, (_, id: string) => `[file ${id}](${FileRefHrefPrefix}${id})`)
         .replace(/\[folder:([a-z]+):(\d+):([^\]\n]+)\](?!\()/g, (_, volume: string, owner: string, path: string) =>
             `[${path}](${FolderRefHrefPrefix}${encodeURIComponent(`${volume}:${owner}:${path}`)})`,