v4: settings are stored on the server, starting with the style, the color scheme and the digest switches — every setting lived in the browser's localStorage, so it didn't follow an account to another browser and the server couldn't read it, which the digests need (whether to send each, and in which style). user_settings (migration 0019) holds one row per user who changed anything, the defaults otherwise, and GET/PATCH /api/users/me/settings read and change it (settings-service, model/settings, validators/settings, shared/settings). AuthProvider reads the settings into the session alongside the user, on mount and on focus, so a change made elsewhere arrives; useSettings changes them at once and puts them back if the server refuses. ThemeProvider now sits inside AuthProvider: a signed-in user's choice comes from their settings and is mirrored to localStorage for index.html's first-paint script, a visitor's stays in the browser, and an account with no choice yet takes the one this browser had, once. Until anyone picks a style, the instance's GERBEUR_DEFAULT_STYLE applies, written into index.html's default-style tag along with email-enabled (src/config/instance.ts), and a browser no longer stores the default as if it had been chosen, so changing the instance's style reaches everyone who never picked one. The settings tab gets an Email section with the weekly digest and monthly recap switches, disabled with a note when the server has no SMTP. The style and scheme names moved to shared/theme.ts in the previous commit; the default feed tab and sounds stay in the browser for now. 223 backend tests (new: settings defaults, patches, isolation, refusals and cascade; index.html's new tags) and 658 frontend tests (new: useSettings, the account's theme winning and a browser's carried over, settings read into the session, the digest switches) pass, and tsc, eslint, doc:lint, deno check, deno lint and deno fmt are clean.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

api/model/settings.ts

@@ -0,0 +1,55 @@
+/**
+ * Checks the rows `settings-service.ts` reads from `user_settings`, and turns
+ * them into the {@link UserSettings} the settings endpoints answer.
+ *
+ * @module
+ */
+
+import type { SQLOutputValue } from "node:sqlite";
+import type { UserSettings } from "../../shared/settings.ts";
+import { isColorScheme, isStyleName } from "../../shared/theme.ts";
+
+/**
+ * Stored by `updateSettings` and read back by `getSettings`. A user without a
+ * row has the defaults.
+ */
+export interface UserSettingsRow {
+  user_id: string;
+  /** A style name, or null for the instance's. */
+  style: string | null;
+  color_scheme: string | null;
+  /** 0 or 1. */
+  digest_weekly: number;
+  /** 0 or 1. */
+  digest_monthly: number;
+  updated_at: string;
+  [key: string]: SQLOutputValue;
+}
+
+/**
+ * Checks whether `obj`, a row `getSettings` selected, is a
+ * {@link UserSettingsRow}.
+ */
+export function isUserSettingsRow(obj: unknown): obj is UserSettingsRow {
+  return !!obj && typeof obj === "object" &&
+    "user_id" in obj && typeof obj.user_id === "string" &&
+    "style" in obj && (obj.style === null || typeof obj.style === "string") &&
+    "color_scheme" in obj &&
+    (obj.color_scheme === null || typeof obj.color_scheme === "string") &&
+    "digest_weekly" in obj && typeof obj.digest_weekly === "number" &&
+    "digest_monthly" in obj && typeof obj.digest_monthly === "number" &&
+    "updated_at" in obj && typeof obj.updated_at === "string";
+}
+
+/**
+ * Converts a row to the {@link UserSettings} the client gets. A style or
+ * scheme the code no longer knows, as after one is removed, reads as unset.
+ */
+export function settingsRowToApi(row: UserSettingsRow): UserSettings {
+  return {
+    style: isStyleName(row.style) ? row.style : null,
+    colorScheme: isColorScheme(row.color_scheme) ? row.color_scheme : null,
+    digestWeekly: row.digest_weekly === 1,
+    digestMonthly: row.digest_monthly === 1,
+  };
+}