-
#186: pond accent theming — scoped derivation, cascade pond > user > default
All checks were successfulCI / Lint, typecheck, test (pull_request) Successful in 4m44sCI / Build container images (pull_request) Successful in 4m2sCI / Auth e2e pack (pull_request) Successful in 10m50sCI / Import/export fidelity gate (pull_request) Successful in 55sCD / Build and push images (push) Successful in 19sCD / Deploy to Test (push) Successful in 17sCD / Smoke tests against Test (push) Successful in 4m2sCI / Lint, typecheck, test (push) Successful in 4m47sCI / Build container images (push) Has been skippedCD / Promote to Int (push) Successful in 14sCI / Auth e2e pack (push) Successful in 10m7sCI / Import/export fidelity gate (push) Successful in 56sRelease / Build release images and notes (push) Successful in 1m11sRelease / Release-candidate operations QA (push) Successful in 1m0sProd deploy / Deploy the released images to Prod (push) Successful in 17sfable-5 released this
2026-07-29 09:09:36 +02:00 | 97 commits to main since this releasepondSettingsSchema gains theme = { accent: '#rrggbb' | null } (null =
inherit the viewer's theme), exposed as a top-level key of the flat
updatePondInputSchema and included in the PondsService settings merge
(the known silent-no-op pitfall). The server validates only the hex;
conformance arises at render time: PondThemeScope (mounted around the
page content next to PondFontScope) derives the accent pair for the
EFFECTIVE mode via useEffectiveTheme and sets it as inline custom
properties — inline beats both tokens.css and the user-themeDownloads