Let bots manage their hooks, with the user confirming what widens them

Bots get list_hooks, pause_hook and delete_hook, which act directly since
they only take away. A new hook, or a new name, brief or filter, or
switching a paused one back on, goes through propose_hook: it stores a
hook_proposals row and puts a [hook-proposal:ID] card in the reply, which
the user it was proposed to confirms or rejects. The card is read from
what Confirm saves, with the bot's reason labelled as its own; confirming
checks everything again and saves through the Hooks modal's helpers. A
new hook's URL is shown on the card once, to the user only, never in the
outcome the bot is told. What calls a hook, its computers and its signing
are never proposed. Only chat replies propose, and a hook call's own run
gets no hook tools, so a caller's payload can't reach them.

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

src/utils/link-computer-refs.ts

@@ -44,11 +44,19 @@ export const FolderRefHrefPrefix = "#folder-";
  */
 export const ProposalRefHrefPrefix = "#proposal-";
 
+/**
+ * The link target a hook proposal ref (`hookProposalRef`) becomes, e.g.
+ * `#hook-proposal-4`. The chat renders it as a chip that opens the card
+ * where the user confirms or rejects the hook.
+ */
+export const HookProposalRefHrefPrefix = "#hook-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]`), folder ref
- * (`[folder:computer:3:seo/raw]`) and proposal ref (`[proposal:7]`) in a message into a markdown link, so it
+ * (`[folder:computer:3:seo/raw]`), proposal ref (`[proposal:7]`) and hook
+ * proposal ref (`[hook-proposal:4]`) 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.
  *
@@ -75,6 +83,10 @@ export default function linkComputerRefs({ text }: { text: string }) {
             /\[proposal:(\d+)\](?!\()/g,
             (_, id: string) => `[proposal ${id}](${ProposalRefHrefPrefix}${id})`,
         )
+        .replace(
+            /\[hook-proposal:(\d+)\](?!\()/g,
+            (_, id: string) => `[hook proposal ${id}](${HookProposalRefHrefPrefix}${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}`)})`,