Marc-André Bombeck ca04ef01b3 refactor(api): read the remaining settings and admin route bodies through parseJsonBody ...

Admin, coach, consent, chart-overlay, device registration, insights
feedback and provider chain, ECG ingest, onboarding, search and the AI
provider settings move to parseJsonBody with the same message, error
code, status and wide-event action they answered with. A refusal whose
annotate meta is computed from the issues, or puts its keys in another
order than the helper would, keeps that annotate verbatim in onInvalid.

The routes that still call safeJson do something between the read and the
schema: an optimistic-concurrency token split off the body, a count cap
answered first, a refunded quota slot, a conditional read, a non-Zod
check, or the body handed to a service.

2026-10-23 11:29:23 +02:00

..

__tests__

fix(search): admit the search POST at read level through a declared, frozen readOverPost

2026-10-11 14:21:56 +02:00

route.ts

refactor(api): read the remaining settings and admin route bodies through parseJsonBody

2026-10-23 11:29:23 +02:00