Files
HiveGrid-Wireframes/03 Quellen und Referenzen/hivegrid-cloud/docs/improvement-plan/10-compliance-polish/i18n-foundation.md
T

371 lines
23 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# i18n-Foundation (ICU-Plurals, Intl-Helpers, RTL, Locale-Picker)
**Status:** in_progress (hardcoded-extraction-zero; namespace/locale/e2e deferred)
**Task-ID:** #72
**Phase:** 10
**Estimated Effort:** 1 Woche
**Owner:** unassigned
## Problem
`packages/i18n/src/` enthält nur einen Stub (`index.ts` + `index.test.ts` Minimal-Setup). Die App-Layer nutzt fragmentarische Translation-Patterns ohne kohärente Foundation:
- **Keine ICU-MessageFormat-Plurals**: Strings wie „X items selected" werden heute als einzelner String mit String-Concatenation oder ternary gerendert — bricht in Sprachen mit Plural-Forms (Polnisch hat 3, Arabisch 6)
- **Keine Intl-Layer-Helpers**: `formatCurrency`, `formatDate`, `formatNumber` werden mehrfach ad-hoc implementiert in `apps/web/app/utils/intl/*`, `apps/web/app/components/**`
- **Kein Locale-Picker**: User kann seine Sprache nicht aktiv wählen; Tenant-Default-Locale wird nicht respektiert; Browser-Detection ist sporadisch
- **Keine RTL-Foundation**: Tailwind-Config hat keine `rtl:`-Direction-Variants aktiviert; Layout würde in Arabisch/Hebräisch brechen
- **Keine klare Translation-File-Struktur**: Translations liegen verstreut in einzelnen Components oder in einer flachen `de.json`/`en.json`-Datei ohne Namespace-Trennung
- **Keine Storybook-i18n-Decorator**: Components zeigen nur Default-Sprache; Stories in alternativen Sprachen müssen manuell konfiguriert werden
Betroffene Codestellen:
- `packages/i18n/src/index.ts` — Stub erweitern
- `apps/web/app/utils/intl/*` — ad-hoc Helpers konsolidieren
- `apps/web/app/components/**` — Translation-Aufrufe normalisieren
- `apps/web/tailwind.config.ts` — RTL-Variants aktivieren
- `apps/web/app/routes/app.$tenant/settings/profile.tsx` — Locale-Picker hinzufügen
- `apps/web/app/utils/data/.server/appData.ts` — Locale-Determination
## Depends on
- `01-tech-debt-foundation/dep-updates.md` — i18next + Intl-API-Versionen aktuell
## Blocks
Keine harten Blocks. Aber: zukünftige Marketing-Funnel-Email-Templates (Phase 05) und Customer-Self-Service-Features profitieren stark von Multi-Locale-Support.
## Approach
**Sechs koordinierte Sub-Komponenten:**
### (a) Audit Existing Translation-Coverage
Vor Implementation: Audit-Subagent läuft durch `apps/web/app/components` und listet:
- Hardcoded-Strings (Englisch oder Deutsch direkt im JSX)
- Existierende `t('...')`-Aufrufe und welche Translation-Library sie nutzen
- Translation-Key-Konflikte (gleicher Key in verschiedenen Files)
Output: `docs/contributing/i18n-audit-<date>.md` als Baseline.
### (b) ICU-MessageFormat-Setup
Library-Wahl: **i18next + i18next-icu** (oder `@formatjs/intl-messageformat` direkt).
`packages/i18n/src/icu/setup.ts`:
```ts
import i18next from 'i18next';
import ICU from 'i18next-icu';
export const i18n = i18next.use(ICU).init({
fallbackLng: 'en',
supportedLngs: ['de', 'en'],
ns: ['common', 'errors', 'settings', 'billing', 'crm', 'auth', 'email-marketing'],
defaultNS: 'common',
resources: { /* dynamic import in app */ }
});
```
Plurals-Pattern:
```json
{
"items_selected": "{count, plural, =0 {Nothing selected} one {# item selected} other {# items selected}}"
}
```
### (c) Intl-Layer-Helpers in `packages/i18n/src/intl/`
Alle Browser-Intl-API-basiert (keine zusätzliche Dependency):
```ts
// packages/i18n/src/intl/format-currency.ts
export function formatCurrency(amount: number, opts: { currency: string; locale: string; minimumFractionDigits?: number }) {
return new Intl.NumberFormat(opts.locale, {
style: 'currency',
currency: opts.currency,
minimumFractionDigits: opts.minimumFractionDigits,
}).format(amount);
}
// packages/i18n/src/intl/format-date.ts
export function formatDate(date: Date | string, opts: { locale: string; style?: 'short' | 'medium' | 'long' | 'full'; timezone?: string }) {
// ...
}
// packages/i18n/src/intl/format-number.ts
export function formatNumber(value: number, opts: { locale: string; style?: 'decimal' | 'percent'; ... }) {
// ...
}
// packages/i18n/src/intl/format-relative-time.ts
export function formatRelativeTime(date: Date | string, opts: { locale: string; relativeTo?: Date }) {
// "vor 3 Tagen" / "3 days ago"
}
// packages/i18n/src/intl/format-list.ts (Intl.ListFormat: "A, B und C")
export function formatList(items: string[], opts: { locale: string; type?: 'conjunction' | 'disjunction' }) { ... }
```
Tests pro Helper mit mehreren Locales (de, en, ar, ja).
### (d) Locale-Picker + Locale-Resolution
- **UI-Component**: `apps/web/app/components/settings/LocalePicker.tsx` — Select-Dropdown mit `de`, `en`, plus zukunftsfähig (Liste aus `packages/i18n/src/supported-locales.ts`)
- **Storage**: User-Preference in `User.locale` (Prisma-Field, Migration nötig)
- **Resolution-Reihenfolge**:
1. `User.locale` (wenn eingeloggt)
2. `Tenant.defaultLocale` (Tenant-Override)
3. `Accept-Language`-Header-Detection (Browser-Default)
4. App-Fallback `en`
- **Server-Side-Loading**: `apps/web/app/utils/data/.server/appData.ts` lädt Locale, passt SSR-Rendering an
- **Client-Side**: Initial-Render mit Server-Locale, Hydration ohne Flicker
### (e) RTL-Layout-Foundation
- `apps/web/tailwind.config.ts`: Direction-Variants nachrüsten via `tailwindcss-rtl` Plugin (oder native `rtl:` Variant in Tailwind 4)
- Layout-Components (`packages/ui-app/Sidebar.tsx`, `Header.tsx`, etc.) erhalten `rtl:`-Klassen wo direction matters:
- `ml-4 rtl:ml-0 rtl:mr-4` für Margin-Flip
- Icon-Pfeile (Chevron-Right für „Nächstes") werden via `rtl:rotate-180` gespiegelt
- `<html dir="..." lang="...">` wird in `root.tsx` server-side gesetzt basierend auf Locale
- Test: 2 ausgewählte Komponenten (Sidebar, Card) als RTL-Smoke-Tests in Storybook
### (f) Translation-File-Struktur
`packages/i18n/src/locales/{de,en}/{common,errors,settings,billing,crm,auth,email-marketing}.json`:
```
packages/i18n/src/locales/
├── de/
│ ├── common.json # Buttons, Labels, generische UI
│ ├── errors.json # Error-Messages
│ ├── settings.json # Settings-UI
│ ├── billing.json # Billing/Subscription
│ ├── crm.json # CRM-Module
│ ├── auth.json # Login, Registration, Magic-Link
│ └── email-marketing.json
└── en/
└── (same structure)
```
Klare Namespace-Trennung, damit:
- Code-Splitting pro Namespace möglich (Auth-Page lädt nur `common` + `auth`, nicht `crm`)
- Translation-Reviews pro Modul möglich
- Key-Konflikte ausgeschlossen
Loader:
```ts
const resources = {
de: {
common: () => import('./locales/de/common.json'),
// ...
}
};
```
### (g) Storybook-i18n-Decorator (sobald Phase 08 Storybook fertig)
`packages/ui-app/.storybook/preview.tsx` Decorator:
```tsx
import { i18n } from '@toolctrl/i18n';
export const decorators = [
(Story, context) => {
const locale = context.globals.locale;
i18n.changeLanguage(locale);
return <I18nextProvider i18n={i18n}><Story /></I18nextProvider>;
}
];
export const globalTypes = {
locale: {
name: 'Locale',
defaultValue: 'en',
toolbar: {
icon: 'globe',
items: [
{ value: 'de', title: 'Deutsch' },
{ value: 'en', title: 'English' },
]
}
}
};
```
Jede Story kann via Storybook-Toolbar Sprache umschalten — visuelles Review beider Sprachen.
### (h) Dokumentation
`docs/contributing/i18n.md`:
- Wie neue Translation-Keys hinzufügen?
- ICU-Plurals-Pattern
- Namespace-Konvention
- Intl-Helper-Übersicht
- RTL-Considerations beim Komponenten-Bau
- Locale-Picker-Integration
- Storybook-Toolbar-Nutzung
**Warum nicht Alternativen:**
- ❌ **react-intl statt i18next-icu**: i18next ist im Ökosystem etablierter, hat Multi-Backend-Support (Static, Backend-Loaded, lazy)
- ❌ **Eigene Plural-Logik**: ICU-Spec deckt 60+ Sprachen ab; nicht selbst nachbauen
- ❌ **Eine globale Translation-Datei pro Sprache**: bricht Code-Splitting; Namespace-Trennung ist langfristig wartbarer
- ❌ **Sofortige Aktivierung von 10+ Sprachen**: Übersetzungs-Aufwand exorbitant; DE/EN reicht für MVP, Foundation erlaubt schnelle Erweiterung
## Implementation Steps
1. **Audit Existing Translation-Coverage**
- Files: `docs/contributing/i18n-audit-<date>.md`
- Subagent läuft durch `apps/web/app/components`, listet hardcoded Strings, existing `t()`-Calls
- Commit: `10-compliance-polish/i18n: baseline translation coverage audit`
2. **Packages/i18n Setup mit i18next + ICU**
- Files: `packages/i18n/src/icu/setup.ts`, `packages/i18n/src/index.ts` (extend), `packages/i18n/package.json` (add `i18next`, `i18next-icu`)
- Singleton-Instance, Resource-Loader
- Tests: ICU-Plural-Rendering für DE/EN
- Commit: `10-compliance-polish/i18n: setup i18next with icu plurals support`
3. **Intl-Layer-Helpers**
- Files: `packages/i18n/src/intl/format-currency.ts`, `format-date.ts`, `format-number.ts`, `format-relative-time.ts`, `format-list.ts`, plus Tests
- Tests pro Helper mit 4 Locales (de, en, ar, ja)
- Commit: `10-compliance-polish/i18n: add intl format helpers`
4. **Translation-File-Struktur (Namespace-Splits)**
- Files: `packages/i18n/src/locales/de/{common,errors,settings,billing,crm,auth,email-marketing}.json`, `packages/i18n/src/locales/en/{...}.json`
- Initial-Translations migrieren aus existierenden Quellen (Audit-Output Step 1)
- Commit: `10-compliance-polish/i18n: split translations into namespaces`
5. **Locale-Resolution + User.locale-Schema-Migration**
- Files: `packages/db/prisma/schema.prisma` (User.locale Field), Migration, `apps/web/app/utils/data/.server/appData.ts`
- Resolution-Reihenfolge implementiert
- Tests: Mock User/Tenant mit verschiedenen Locales → erwartete Resolution
- Commit: `10-compliance-polish/i18n: add user locale field and resolution logic`
6. **Locale-Picker-Component**
- Files: `apps/web/app/components/settings/LocalePicker.tsx`, `apps/web/app/routes/app.$tenant/settings/profile.tsx` (integration)
- Select-Dropdown, Form-Action updated User.locale
- Tests: Render + Action
- Commit: `10-compliance-polish/i18n: add locale picker in user settings`
7. **RTL-Foundation (Tailwind-Config + Layout-Component-Audits)**
- Files: `apps/web/tailwind.config.ts`, `apps/web/app/root.tsx` (html dir/lang), `packages/ui-app/Sidebar.tsx`, `Header.tsx`, etc.
- `rtl:`-Klassen wo nötig
- Tests: 2 RTL-Smoke-Tests (Sidebar, Card) als Storybook-Stories
- Commit: `10-compliance-polish/i18n: add rtl layout foundation`
8. **Storybook-i18n-Decorator** (nur wenn Phase 08 Storybook bereits fertig)
- Files: `packages/ui-app/.storybook/preview.tsx`
- Decorator + Toolbar-Toggle
- Tests: Visual-Snapshot in DE und EN für 5 Test-Komponenten
- Commit: `10-compliance-polish/i18n: add storybook i18n decorator`
9. **Dokumentation**
- Files: `docs/contributing/i18n.md`
- Workflow, Helpers, Patterns, RTL-Considerations
- Commit: `10-compliance-polish/i18n: document i18n contribution workflow`
## Test Requirements
- **Unit-Tests:**
- ICU-Plural-Rendering für DE (one, other), EN (one, other), PL (one, few, many)
- Intl-Helpers für mind. 4 Locales pro Helper (de, en, ar, ja)
- Locale-Resolution-Logic: alle 4 Resolution-Reihenfolge-Cases
- Locale-Picker-Component: Render + Form-Submit
- **Integration-Test:**
- User-Flow: User loggt sich ein, ändert Locale in Settings, Reload → UI ist in neuer Sprache, `<html lang>` aktualisiert
- **E2E-Test (Playwright):**
- Login DE-User → Dashboard ist in Deutsch
- Locale-Picker auf EN → Reload → Dashboard in Englisch
- Browser-Default-Detection ohne User-Pref → korrekte Default-Sprache
- **RTL-Smoke-Test:** Storybook-Story für Sidebar mit `dir="rtl"` → Layout-Flip visuell verifiziert
- **Coverage-Target:** ≥ 85 % in `packages/i18n/src/`
- **Test-Files:** co-located `<source>.test.ts`; E2E in `tests/e2e/i18n.spec.ts`
**NICHT als completed markieren bevor Locale-Switch-Flow end-to-end (UI + Storage + Reload) auf Staging funktioniert.**
## Acceptance Criteria
- [ ] `packages/i18n/src/icu/setup.ts` initialisiert i18next + ICU
- [ ] Intl-Helpers für Currency, Date, Number, RelativeTime, List
- [ ] Translation-Files in Namespace-Splits (7 Namespaces × 2 Locales = 14 Files)
- [ ] `User.locale` Schema-Migration grün
- [ ] Locale-Resolution: User > Tenant > Browser > Fallback funktioniert
- [ ] Locale-Picker in `/app/$tenant/settings/profile.tsx` funktional
- [ ] Tailwind-RTL-Variants aktiv; 2 RTL-Smoke-Tests grün
- [ ] `<html dir="..." lang="...">` server-side korrekt gesetzt
- [ ] Storybook-i18n-Decorator (wenn Phase 08 fertig)
- [ ] Coverage ≥ 85 % in `packages/i18n/src/`
- [ ] `pnpm lint`, `pnpm typecheck`, `pnpm test` grün
- [ ] `docs/contributing/i18n.md` angelegt
- [ ] `docs/contributing/i18n-audit-<date>.md` als Baseline gespeichert
- [ ] Detail-MD Progress Log aktualisiert
- [ ] PROGRESS.md Status auf `completed`
## Rollback Strategy
- **i18next-ICU-Bug → falsche Plurals**: Helpers haben Fallback auf Basic-i18next ohne ICU (deactivate ICU-Plugin via Feature-Flag)
- **Locale-Picker bricht User-Flow**: Component-Renderer wird auf no-op gesetzt; Default-Locale bleibt aktiv
- **RTL-Variants brechen Layout (LTR-Defaults)**: Tailwind-Config-Commit reverten; RTL bleibt unsupported aber LTR unbeschadet
- **Schema-Migration**: User.locale Field bleibt — Down-Migration optional; Code-seitig wird Field ignoriert wenn Feature deactivated
- **i18n-Files zu groß**: zurück zu globaler JSON-Struktur, Lazy-Load deaktivieren
## Security Notes
- **Translation-Files können XSS-Vektor sein** wenn HTML-haltige Strings unsafe gerendert werden: i18next bietet `react-i18next` mit `Trans`-Component der React-Escaping respektiert; `dangerouslySetInnerHTML` ist verboten in Translation-Rendering
- **Locale-Param in URL**: wenn Locale via URL-Param überschrieben werden kann (`?locale=de`), muss Param-Validation gegen `supportedLngs` laufen — sonst Open-Redirect-ähnliche Klasse
- **RTL-Content kann Bidi-Spoofing**: Punycode-/Bidi-Override-Characters in User-Content (z.B. CRM-Contact-Names) können Display-Spoofing erzeugen; Display-Layer muss Bidi-Override-Characters strippen oder visuell markieren (siehe CVE-2021-42574)
- **Pseudonymization-Map (DSGVO)** muss locale-aware sein: pseudonymisierte User-Names sollten in keiner Sprache real-existing Namen treffen (z.B. „Anonymized User #1234" statt zufälligem string)
## Subagent Recommendations
- **Planning:** `Plan`-Subagent mit dieser Detail-MD + `packages/i18n/src/index.ts` als Input — soll Library-Wahl (i18next vs formatjs) validieren
- **Research:** `Explore`-Subagent für Audit in Step 1 — soll alle hardcoded Strings + existing `t()`-Aufrufe listen
- **Implementation:** Ein `general-purpose`-Subagent pro Implementation-Step (1-9); Translation-File-Migration (Step 4) kann sehr groß werden — eigenen Subagent
- **Tests:** Test-Code direkt mit Implementation; E2E-Tests separater `general-purpose`-Subagent (Step 6/7)
- **Verification:** `gsd-verifier` für Acceptance-Criteria; manuelle Verifikation des Locale-Switch-Flows auf Staging
- **Code-Review:** `gsd-code-reviewer` nach Step 9, Fokus auf XSS-Sicherheit in Translation-Rendering und Bidi-Handling
## Staging-Deployment-Steps
1. Branch `agent/10-i18n-foundation` pushen
2. Coolify-Auto-Deploy auf Staging
3. Prisma-Migration läuft auto via Deploy-Hook
4. **Smoke-Test Locale-Switch**:
- Login als Test-User in Staging
- Navigate `/app/$tenant/settings/profile` → Locale-Picker sichtbar
- Switch von EN → DE → Reload → UI-Strings sind deutsch (Buttons „Speichern", „Abbrechen" etc.)
- Switch zurück zu EN → UI englisch
5. **Browser-Detection-Test**: Inkognito-Browser mit `Accept-Language: de-DE,de` → Anonymer Besuch zeigt deutsche Landing-Page
6. **RTL-Smoke-Test in Storybook**: Storybook auf Staging → Toolbar → Locale auf „ar" (oder dedizierter RTL-Toggle) → Sidebar-Story zeigt RTL-Layout
7. **Intl-Helper-Verifikation in Browser-Console**: `formatCurrency(1234.5, { currency: 'EUR', locale: 'de-DE' })` → `"1.234,50 €"`
## Deviations from Plan
- **Library choice:** chose direct `intl-messageformat` (FormatJS) integration rather than `i18next-icu`. Rationale: the upstream `i18next-icu` plugin requires `i18next@^24` while this repo pins `i18next@^23.16.3`. Wrapping FormatJS in a `formatIcu()` helper + `createUseTranslate()` factory gives us identical pluralisation semantics with no peer-dependency conflict. Migration to `i18next-icu` becomes a no-op when `i18next` is bumped — both libraries delegate to the same CLDR plural rule data.
- **Translation-file split:** the legacy `translations.json` (4381 lines, hundreds of consumers) was NOT migrated wholesale. Instead, the namespace structure is documented in `docs/contributing/i18n.md` and `apps/web/public/locales/README.md`, and two showcase namespaces (`common`, `settings`) were seeded as the template. Full split is the extraction sprint — out of scope for the 1-week foundation budget per agent instructions.
- **Locale-picker UI:** already shipped in `apps/web/app/modules/users/components/UserProfileSettings.tsx` (POSTs to root `setLocale` action → persists `User.locale`). This task added a static-source guard test rather than re-implementing.
- **RTL plugin choice:** stuck with Tailwind's built-in `[dir="rtl"]` attribute selector rather than `tailwindcss-rtl` plugin. The plugin would add a moderate amount of generated CSS for variants we don't use yet; the built-in `rtl:` modifier covers the foundation use-cases and the plugin can be layered in later if needed.
- **Storybook decorator:** wired direction + `<html lang/dir>` only. Did NOT wire full `react-i18next` provider into Storybook because most stories pass copy via props rather than translation keys — the design system tests visual contrast and layout. Adding the provider becomes a one-line addition once stories start using `useTranslation` directly.
- **Concurrent-agent rebase race:** commit 2 (namespace structure + parity tests + `index.test.ts` update) was rolled into the concurrent #56 agent's `dbbc120d` "sync hardcoded-strings test fixtures" commit due to a rebase + stash-pop race during near-simultaneous pushes. File content is correct (both agents' changes coexist), only the commit message under-represents the i18n payload.
- **Extraction-sprint scope (2026-05-20; superseded as current status).** The `i18n-audit.mjs` heuristic originally counted comment-only and gate-excluded seed/codegen/legal-page text, which made its audit floor higher than the enforced runtime gate. As of the 2026-05-26 follow-up slices, `pnpm run verify:hardcoded-strings` is the current source of truth for enforced UI/response copy and reports `jsx-text: 0`, `user-facing-prop-literal: 0`, and `user-facing-response-literal: 0`.
- **Remaining #72 work after the zero floor:** split the legacy `translations.json` surface into the documented namespace structure, broaden locale coverage beyond the current DE/EN paths where product scope requires it, and run an approved Playwright/staging locale-switch proof. Checkout-success, plugin-lifecycle, widget settings, transactional-mail settings, and WorkflowEngine condition-node copy are no longer open hardcoded-copy items.
## Progress Log
- 2026-05-17 19:35 — `210d20fe` — extend packages/i18n with ICU plurals + Intl helpers
- 2026-05-17 19:37 — `dbbc120d` — namespace structure (co-landed with concurrent agent commit, content correct)
- 2026-05-17 19:39 — `5d47960d` — RTL Tailwind variants + smoke test
- 2026-05-17 19:41 — `230aad0d` — i18n-audit script + 2026-05-17 baseline (18 hits / 14 files)
- 2026-05-17 19:44 — `90113b1b` — locale-picker guard test
- 2026-05-17 19:46 — `32bc9956` — 2 example component migrations (audit drops 18 → 15)
- 2026-05-17 19:49 — `1484698f` — Storybook locale toolbar + decorator
- 2026-05-17 19:51 — `76794e30` — bump user-facing-prop-literal baseline 50 → 52 for storybook strings
- 2026-05-17 19:53 — `85edd2d0` — `docs/contributing/i18n.md` migration guide
- 2026-05-17 19:55 — `<this commit>` — PROGRESS.md + detail-md progress log
- 2026-05-20 — extraction sprint: 65 hardcoded JSX-text strings across 42 `apps/web/app` route/module/component files migrated to `ui.autogenerated.*` keys (en values + idiomatic German added to both `translations.json` locale files, resolved via global `i18nT`). Audit `totalHardcodedStrings` 111 → 46. `verify-hardcoded-strings.mjs` baselines locked down: `jsx-text` 85 → 18, `user-facing-prop-literal` 73 → 46 (test updated to match).
- 2026-05-20 — extraction sprint batch 2: 20 further gate-counted strings migrated across 7 admin/route files (table headers, marketing-funnel `Card`/`Breakdown` component-prop titles, 3 interpolated `aria-label`s using `{{value0}}` placeholders). `verify-hardcoded-strings.mjs` baselines were ratcheted down again, and the 2026-05-25 sweep locked the then-current floor at `jsx-text` 1, `user-facing-prop-literal` 8, and `user-facing-response-literal` 63 after extracting sequence email copy, prompt-builder toasts, legacy transactional email registry copy, forgot-password responses, workflow-builder action responses, workflow-run responses, workflow API responses, workflow list/variable responses, onboarding/admin-onboarding responses, tenant feedback validation copy, knowledge-base admin/public response copy, rows import/permission response copy, admin cache response copy, site authentication response copy, admin IP-address action response copy, admin account deactivation copy, feature-flags engine response copy, admin CRM sync response copy, feature-flags create/edit response copy, admin entity-group response copy, formula action response copy, admin entity-view response copy, admin account user/role/subscription response copy, admin knowledge-base base/article/category/section/import/danger response copy, admin onboarding update/activation/steps response copy, admin prompt-builder flow/output/mapping/variable response copy, root theme action response copy, prompt-builder creation/group response copy, and admin pricing/portal/notification/AI-overage copy, workflow input validation, admin entity danger responses, admin AI usage metadata, and metrics API response copy. The remaining gate residual at that point was transactional email-template copy, Storybook dev-tool globals, API/server response strings, `ErrorPage` key+fallback literals, and one false-positive TS type.
- 2026-05-25 — I18N-WORKER lead-capture slice: localized all public `/api/leads/capture` user-facing response errors through `api.errors.leadCapture.*` keys in `translations.json` (en/de) while preserving existing status codes, CORS headers, and empty-body anti-enumeration responses. `verify-hardcoded-strings.mjs` historical `user-facing-response-literal` baseline ratcheted 63 → 54, matching the scanned repository floor.
- 2026-05-26 — i18n zero-floor sync: workflow condition-node copy (`0795f938`), widget settings (`b9b0a072`), transactional-email settings (`15fdbbee`), plugin-lifecycle errors (`1d769248`), checkout-success details (`f42e7342`), and email-sequence stats (`52989482`) finished the remaining enforced UI/response extraction surface. `pnpm run verify:hardcoded-strings` reports `jsx-text: 0`, `user-facing-prop-literal: 0`, and `user-facing-response-literal: 0`; remaining #72 work is namespace/locale architecture and approved E2E locale-switch proof, not unresolved hardcoded UI copy.
## Lessons Learned
_(Optional, am Ende des Tasks für nachfolgende Tasks)_