db-mode config changes apply live in-process

settings and upstream writes now follow a prepare, commit, publish, retire
contract: candidates are built and validated before the database transaction,
published as infallible pointer swaps, and old generations retire after their
readers drain. per-query policy values snapshot once per query; upstream pool,
cache, rate limiter, sessions, api limiter, log sink, blocklist scheduler and
the query-log queue each gained one named live operation. restart_required
shrinks from every scalar key to the bind keys and web.enabled; the admin ui
drops its restart notices for everything else. file mode is unchanged.

admin/src/lib/queries.ts

@@ -328,14 +328,11 @@ export const clientPrefixesPutMutation = (qc: QueryClient) => ({
 	},
 });
 
-// The pool builds its clients at startup, so every upstream write leaves the
-// server owing a restart. The flag it sets lives on /api/config/status, and the
-// shell notice reads it there — hence the second invalidation.
+// An upstream write rebuilds the pool in the running process, so the row list
+// is the only thing it changes: no restart is owed and /api/config/status says
+// the same thing after the write as before it.
 function invalidateUpstreams(qc: QueryClient): Promise<unknown> {
-	return Promise.all([
-		qc.invalidateQueries({ queryKey: queryKeys.upstreams }),
-		qc.invalidateQueries({ queryKey: queryKeys.configStatus }),
-	]);
+	return qc.invalidateQueries({ queryKey: queryKeys.upstreams });
 }
 
 export const upstreamCreateMutation = (qc: QueryClient) => ({