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/functions/backend/db/bots-queue/stop-bot-jobs.ts

@@ -5,6 +5,7 @@ import insertBotMessage from "../bots/insert-bot-message";
 import setBotFace, { type BotFaceChange } from "../bots/set-bot-face";
 import { abortRunningJob } from "@/src/bots-queue/job-abort-registry";
 import insertBotJobUpdate from "./insert-bot-job-update";
+import recordHookCallResponse from "../bot-hooks/record-hook-call-response";
 import openBotJobsSql from "./open-bot-jobs-sql";
 import stoppedJobReport, { pickReportedJobs } from "./stopped-job-report";
 
@@ -91,6 +92,8 @@ export default async function stopBotJobs({ bot_id, user_id }: Params): Promise<
             });
         }
 
+        await recordHookCallResponse({ job: stopped, status: "failed", response: BotJobStoppedError, now });
+
         /**
          * Recorded as the job's last step, so the working row says why it
          * went quiet.