fix(activity): runs keep their true outcome and spend, the page reaches every kept row, a closing dialog leaves the server log alone

Backend
- A run's outcome write sits outside the job's own try: a database blip after a run that
  succeeded no longer records it as failed (the row waits for the next start's sweep).
- An interrupted run keeps what it spent (the sweep sums its quota rows, as finish does).
- The Scheduler's ad-hoc row says running while any backfill runs, not only the newest.
- recent_runs reads each job's last runs off its index instead of ranking the whole table.
- An interval change is stored with its audit row in one transaction, then rescheduled.
- One API instance per database is the stated contract (.env.example, jobruns).
- Turning full history on for a channel already complete records no run.
- Migration 0109 round-trips interrupted and ad-hoc runs; the run words' DB CHECKs are
  test-held to the enums; the account filter is one helper for the four activity reads.
- An audit row says how many of its request's log lines are still kept.

Frontend
- An "All" period reaches every row still kept (runs and admin actions outlive 90 days).
- Back/Forward is followed in place by the server log: a closing dialog no longer turns
  Live off; a pivot still opens a fresh log.
- Runs moved over from the audit log read their one-liner in the reader's language.
- Filter choices or accounts that failed to load say so beside the filters, with a retry.
- An old server-log link keeps its account, text and range; a remembered retired page
  opens its tab.
- A request whose lines are gone says so instead of linking to an empty list.
- The log lines and the history rows share one row frame, and the server log one list
  frame with the other tabs; an empty list is announced; each day's quota is readable.

frontend/src/lib/api/admin.ts

@@ -105,6 +105,8 @@ export interface AuditRow {
   after: Record<string, unknown> | null;
   /** The request the change was made in — its log lines are one pivot away. Null on older rows. */
   request_id: string | null;
+  /** How many of that request's log lines are still kept (they go after days, the row after months). */
+  log_lines: number;
 }
 
 /** A page of a history list (audit log, runs), newest first; `next_cursor` continues it. */
@@ -142,7 +144,8 @@ export interface RunRow {
   summary: string | null;
   result: JobResult | null;
   error: string | null;
-  failure: { code: string; [key: string]: unknown } | null;
+  /** A failure the job named (`progress.JobFailed`): its reason, and the values it is said with. */
+  failure: { failure: string; [key: string]: unknown } | null;
   quota_units: number;
   /** How many stored log lines the run left (WARNING and up only). */
   log_lines: number;
@@ -249,8 +252,10 @@ function queryString(values: object): string {
 export type JobResult = { [key: string]: number | string | JobResult };
 
 /** How a run ended — the server's `RunStatus` (app/runstatus.py) minus `running`. `interrupted`:
- *  the process stopped mid-run (a deploy, a crash), and its next start closed the row. */
+ *  the process stopped mid-run (a deploy, a crash), and its next start closed the row. The values are
+ *  held to the server's by backendIds.contract.test (through RUN_STATUSES, typed as `RunStatus`). */
 export type RunOutcome = "ok" | "error" | "skipped" | "interrupted";
+export type RunStatus = RunOutcome | "running";
 
 /** One past run, as the row's history dots show it. */
 export interface RunBrief {