feat(i18n): add Dutch as an eighth end-to-end locale

Adds messages/nl.json (AI-initial, informal je/jij register, full key
parity with en.json) and registers nl everywhere the locale list lives:
config, loaders, Intl/date-fns mapping, zod enums, OpenAPI spec, scripts,
the managed-profile picker and the notification locale guards.

Dutch follows the Korean pattern for the AI surfaces (English body plus a
Dutch reply-language footer, no safety-contract matrix) and gets its own
banks in the outbound safety screen (dose, risk, causal, continuation),
the prose-grounding and citation-coverage tables, the reference-range
prose and the no-key fallback copy, each with Dutch test fixtures.

PHQ-9 / GAD-7 / WHO-5 are not marked validated for nl yet: the Dutch
wording has not been read against the published forms, so Dutch readers
get the English items plus the existing note until it has.
This commit is contained in:
Rob de Graaf committed 2026-10-19 11:06:55 +02:00
1 parent 01bf8fbb64
commit c6f61fad33
83 files changed
+13832 -74

No files matched your search

+4 -2
View File
@@ -1,4 +1,4 @@
import { de, enUS, es, fr, it, ko, pl } from "date-fns/locale";
import { de, enUS, es, fr, it, ko, nl, pl } from "date-fns/locale";
import type { Locale as DateFnsLocale } from "date-fns";
import type { Locale } from "@/lib/i18n/config";
@@ -6,7 +6,7 @@ import type { Locale } from "@/lib/i18n/config";
/**
* Map the app locale → the date-fns locale so the calendar's month / weekday
* names match the UI language. Defaults to enUS for anything unmapped.
* Imported only by the calendars, which load on demand, so the seven
* Imported only by the calendars, which load on demand, so the eight
* locales never ride a page's first load.
*/
export function resolveDateFnsLocale(locale: Locale): DateFnsLocale {
@@ -23,6 +23,8 @@ export function resolveDateFnsLocale(locale: Locale): DateFnsLocale {
return pl;
case "ko":
return ko;
case "nl":
return nl;
default:
return enUS;
}