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/cancel-bot-job.ts

@@ -2,6 +2,7 @@ import BunSQLite from "@moduletrace/bun-sqlite";
 import type { BUN_SQLITE_COBBLE_BOTS_QUEUE } from "@/db/types/db";
 import { BotJobCancelledError } from "@/src/dict/bot-queue-dict";
 import AppError from "@/src/utils/app-error";
+import recordHookCallResponse from "../bot-hooks/record-hook-call-response";
 
 type Params = {
     user_id: number | string;
@@ -37,5 +38,7 @@ export default async function cancelBotJob({ user_id, job_id }: Params) {
         });
     }
 
+    await recordHookCallResponse({ job, status: "failed", response: BotJobCancelledError, now });
+
     return job;
 }