jjbrunton 25b7c6238e feat(admin-api): expose notification_preferences as read-only ...

Resolve the earlier open question by mapping the profile-settings
domain's notification toggles to the existing notification_preferences
table (primary key user_id, no sensitive columns). Read-only, gated on
view_users, with a test covering read access and rejected writes.

2026-08-30 19:04:54 +01:00

..

drizzle

feat(quiz): variety in quiz question selection

2026-08-30 18:21:55 +01:00

src

feat(admin-api): expose notification_preferences as read-only

2026-08-30 19:04:54 +01:00

test

feat(admin-api): expose notification_preferences as read-only

2026-08-30 19:04:54 +01:00

.dockerignore

feat(backend): add standalone data plane

2026-08-28 14:42:11 +01:00

.env.example

perf(api): bound worker pools and add telemetry

2026-08-29 22:43:27 +01:00

Dockerfile

feat(backend): add standalone data plane

2026-08-28 14:42:11 +01:00

drizzle.config.ts

feat(backend): add standalone data plane

2026-08-28 14:42:11 +01:00

package.json

test(coverage): enforce API and app floors

2026-08-29 22:50:07 +01:00

tsconfig.json

feat(backend): add standalone data plane

2026-08-28 14:42:11 +01:00

vitest.config.ts

test(coverage): enforce API and app floors

2026-08-29 22:50:07 +01:00

vitest.integration.config.ts

test(coverage): enforce API and app floors

2026-08-29 22:50:07 +01:00