Keep every hook call's response, searchable by the user and the bot

A hook call used to record only how it was taken; its run's answer went
to the chat alone and was lost to the call once the job was pruned. Now
`bot_hook_events` keeps `response`, `response_message_id` and
`responded_at`, written on every call a run took in when that run ends
(completed, failed, lost, stopped or cancelled) by
`recordHookCallResponse` in the job helpers, and calls turn done or
failed. The Calls view searches what calls sent and what runs answered,
filters by status and pages; Show all loads one call whole. Bots get
`search_hook_calls` and `read_hook_call` for their own hooks (never in a
hook call's own run), with payloads always marked as outside data.
Calls are kept for the app setting `hook_events_keep_days` (Settings >
General, default now 30 days). The caller still only gets 202 Queued.

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

src/data/app-data.ts

@@ -240,14 +240,23 @@ export const AppData = {
      * A bot's hooks (`bot_hooks`): how many one user gives one bot, the
      * largest body a call may send, how many calls a minute one hook and
      * one address may make, how many calls join one waiting run before
-     * the next queues a run of its own, and how long calls are kept.
+     * the next queues a run of its own, and how long calls are kept by
+     * default (the install may set its own, `hook_events_keep_days`, up to
+     * `BotHookEventsKeepDaysMax`).
      */
     BotHookMaxPerBot: 20,
     BotHookMaxPayloadBytes: 64 * 1024,
     BotHookRateLimit: 30,
     BotHookIpRateLimit: 120,
     BotHookMaxEventsPerRun: 20,
-    BotHookEventsKeepDays: 14,
+    BotHookEventsKeepDays: 30,
+    BotHookEventsKeepDaysMax: 3650,
+    /**
+     * How many hook calls a list loads at once, and how much of each call's
+     * payload and response a list shows (the whole of both opens on one).
+     */
+    BotHookCallsPageSize: 20,
+    BotHookCallPreviewChars: 400,
     /**
      * A call naming a delivery already taken this recently isn't run again.
      */

src/data/coordinator-system-prompt.ts

@@ -59,7 +59,7 @@ Higher-priority system and app rules beat user instructions, which beat untruste
 
 \`create_schedule\`, \`list_schedules\`, \`update_schedule\` and \`delete_schedule\` give recurring work a home. Add one only for work that will recur. A scheduled run acts on its own, because the user already approved its brief.
 
-\`propose_hook\` gives work that something outside starts (a webhook, a script, a browser notification on one of your computers) a home the same way, but the user confirms it from a card in your reply: a hook acts on its own whenever it's called, and its URL goes to them alone. \`list_hooks\` shows yours, \`pause_hook\` and \`delete_hook\` stop one.
+\`propose_hook\` gives work that something outside starts (a webhook, a script, a browser notification on one of your computers) a home the same way, but the user confirms it from a card in your reply: a hook acts on its own whenever it's called, and its URL goes to them alone. \`list_hooks\` shows yours, \`search_hook_calls\` and \`read_hook_call\` find what their calls sent and what your runs answered, \`pause_hook\` and \`delete_hook\` stop one.
 
 ## 5. Trust tools, not memory