Marc-André Bombeck 4dbad48d89 fix(admin): persist the assistant flags sent to the settings route ...

`adminSettingsSchema` validates five `assistant*` booleans and the strict
schema refuses anything else, but the route's `booleanFields` list never
carried them. Sending one alone answered 422 "No valid fields"; sending one
alongside a real field answered 200 and dropped it. The schema comment says
the entry exists so an operator scripting their settings over the single
route can carry the values, so the route is brought up to the contract
rather than the contract cut down to the route.

The flags are echoed in the GET and PUT payloads as raw column values — the
master-over-sub resolution stays with `/settings/assistant-flags`, which
owns that shape and was never affected.

2026-09-03 02:02:22 +02:00

..

__tests__

fix(admin): persist the assistant flags sent to the settings route

2026-09-03 02:02:22 +02:00

assistant-flags

Remove the Health-Score explainer switch, which switched nothing

2026-07-31 08:06:07 +02:00

module-availability

style: apply prettier across the tree

2026-06-19 22:20:31 +02:00

web-push-vapid/generate

feat(medications,measurements): derive write provenance from transport and surface it

2026-07-23 21:15:17 +02:00

route.ts

fix(admin): persist the assistant flags sent to the settings route

2026-09-03 02:02:22 +02:00