SnapOtter c061ad13ce fix: default theme setting not persisting across sessions (#98) ...

Three disconnected systems caused the theme to never apply from server
settings: the DEFAULT_THEME env var was parsed but never seeded to the
database, the settings store ignored defaultTheme from the API, and the
settings dialog wrote to the DB without updating the active theme store.

- Seed DEFAULT_THEME and DEFAULT_LOCALE env vars into the settings table
  on first startup (ensureDefaultSettings in index.ts)
- Add applyServerDefault() to theme store that applies the server's
  default theme only when the user hasn't made an explicit choice
- Extract defaultTheme from the settings API response and apply it on
  fresh sessions (no localStorage preference)
- Apply theme immediately when admin saves settings
- Allow "system" as a valid DEFAULT_THEME env var value

2026-04-25 22:39:18 +08:00

..

benchmark

chore: deploy to Cloudflare Pages and update branding

2026-04-24 18:06:29 +08:00

e2e

fix: QA sweep — 7 bugs fixed, 17 test corrections

2026-04-25 07:23:58 +08:00

e2e-docker

test: expand coverage to 3,382 tests across all layers

2026-04-24 22:43:14 +08:00

fixtures

fix: PaddleOCR CPU crash, content-aware-resize limits, barcode fixtures

2026-04-24 23:58:06 +08:00

integration

test: major coverage expansion — 18 new test files, ~750 new tests

2026-04-25 21:53:13 +08:00

unit

fix: default theme setting not persisting across sessions (#98)

2026-04-25 22:39:18 +08:00