Let outside services and computers' browser notifications give bots work

A bot hook (bot_hooks) is a secret URL, POST /api/hooks/<token>, whose
calls queue the hook's brief plus the raw body as a task, per user and
bot like a routine. Only the token's hash is kept (shown once, rotatable);
an optional HMAC-SHA256 signing secret is stored encrypted. Calls are
rate limited per address and per hook, recorded in bot_hook_events
(pruned daily), deduplicated by delivery id, and a call while the last
run still waits joins its brief instead of queueing another. The payload
is fenced data and HookRunNote tells the bot never to take instructions
from it; failed runs retry like routines.

A hook can instead watch a computer's browser notifications: the app
installs a small watcher that owns org.freedesktop.Notifications on the
sandbox's session bus, so Chrome hands it every notification (it only
looks for that service at start-up, so Chrome is restarted once, never
mid-task), and it posts each one to its hooks, optionally filtered.
Computers reach the app at COMPUTER_APP_URL or the app container's name.

Users make hooks in the conversation's Hooks modal and manage them all
on /admin/routines; bots never create or change hooks.

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

src/functions/backend/db/bot-hooks/record-bot-hook-failure.ts

@@ -0,0 +1,21 @@
+import BunSQLite from "@moduletrace/bun-sqlite";
+
+type Params = {
+    hook_id: number;
+    /**
+     * The run's job: only the hook's latest run records its failure.
+     */
+    job_id: number;
+    error: string;
+};
+
+/**
+ * Keeps why a hook's latest run failed in `last_error`, so its row shows
+ * it. The next run that's queued clears it.
+ */
+export default async function recordBotHookFailure({ hook_id, job_id, error }: Params) {
+    await BunSQLite.sql({
+        sql: `UPDATE bot_hooks SET last_error = ?, updated_at = ? WHERE id = ? AND last_job_id = ?`,
+        values: [`Last run failed: ${error}`, Date.now(), hook_id, job_id],
+    });
+}