[codex] Expand i18n coverage across main surfaces

✅ merged · #14 · manueljpconde/mikeEU ← manueljpconde/mikeEU · opened 16d ago by manueljpconde · merged 16d ago by manueljpconde · self · +716-174 across 17 files · ↗ on GitHub

From the PR description

Summary

  • Move the language switcher from the sidebar account menu into the Account settings profile section below email.
  • Add catalog-backed translations for assistant chrome, account settings, projects, tabular reviews, workflows, and related modals.
  • Extend all supported locale catalogs (en, pt, es, fr, de) with matching keys for the new translated surfaces.

Why

The i18n rollout left several high-visibility app surfaces with hardcoded English strings. This makes locale switching feel incomplete across the main lawyer-facing workflow.

Validation

  • npm run lint:catalogs --prefix frontend
  • npm test --prefix frontend (55/55)
  • npm run build --prefix frontend
  • docker compose --env-file .env.docker up -d --build frontend
  • curl -I -sS http://localhost:3000/login | head returned 200 OK

Notes

  • Built-in workflow/legal prompt text remains untranslated because it is domain content, not app chrome.
  • Full repo npm run lint --prefix frontend still fails on existing unrelated lint debt; this PR was validated with catalog tests, frontend tests, and production build.

Our analysis

Expand i18n coverage across main lawyer-facing surfaces — read the full analysis →

Think the analysis missed something the PR description covers?

Commits in this PR (1)

SHA Subject Author Date
93b5b2bd Expand i18n coverage across main surfaces Manuel Conde 2026-05-10 ↗ GitHub

Capture this PR into my fork

Download a Markdown prompt that tells Claude how to port every commit in this PR into your working tree. Run it via claude -p < capture-pull-14.md from inside the repo you want the changes in.

⬇ Download capture-pull-14.md