chore: Fix app

agents-docs/features/app-i18n.md

@@ -1,7 +1,14 @@
 # App i18n
 
+> **Status:** Active
+> **Last updated:** 2026-07-05
+
 Client-side UI string localization for the product client (`toju-app`), using the same `@ngx-translate/core` stack as the marketing website.
 
+## Migration status
+
+Only **English** ships today (`SUPPORTED_APP_LOCALES = ['en']`). The catalog workflow and `translate` pipe are in place, but many components still use hardcoded strings — new user-visible copy should use i18n keys; migrate adjacent strings when touching a component. There is no locale preference UI yet.
+
 ## Responsibilities
 
 - Bundle locale JSON under `toju-app/public/i18n/`.
@@ -60,3 +67,14 @@ The sync script also extracts `theme.registry.*` labels/descriptions from `theme
 - `toju-app/src/app/core/i18n/app-i18n.rules.spec.ts`
 - `toju-app/src/app/core/i18n/app-i18n.service.spec.ts`
 - `toju-app/src/app/core/i18n/app-i18n.testing.ts` — `provideAppI18nForTests()` / `initializeAppI18nForTests()` for Vitest injectors
+
+## Related
+
+- `toju-app/AGENTS.md` — i18n usage rules for agents
+- Marketing site i18n is separate: `website/public/i18n/`
+
+## Changelog
+
+| Date | Change |
+|------|--------|
+| 2026-07-05 | Documented partial migration status and locale UI gap |