Translate

Workflow

Run the i18n diff to list missing keys.
- Command: cd play && npm run i18n:diff
- Single locale: cd play && npm run i18n:diff -- <locale>
If multiple locales are missing the same keys, prefer a single, scripted/batched edit across locale files to reduce context churn (e.g., a small node/sed script), then spot-check one locale.
Open the reported locale files under play/src/i18n/<locale>/ only as needed to confirm structure.
For each missing key:
- Look at the en-US translation first. If unsure, look at the fr-FR translation too.
- If unsure, ask the user precisions before translating.
Re-run the diff command until it reports no missing translations.

en-US is the source of truth. Use it to find the canonical string and structure.
Preserve formatting, placeholders, and variable names exactly (e.g., {name}, {count}).
Keep file formatting consistent with the existing module (4 spaces, newline at EOF).

Run the i18n diff to list missing keys.
- Command: cd play && npm run i18n:diff
- Single locale: cd play && npm run i18n:diff -- <locale>
If multiple locales are missing the same keys, prefer a single, scripted/batched edit across locale files to reduce context churn (e.g., a small node/sed script), then spot-check one locale.
Open the reported locale files under play/src/i18n/<locale>/ only as needed to confirm structure.
For each missing key:
- Look at the en-US translation first. If unsure, look at the fr-FR translation too.
- If unsure, ask the user precisions before translating.
Re-run the diff command until it reports no missing translations.

en-US is the source of truth. Use it to find the canonical string and structure.
Preserve formatting, placeholders, and variable names exactly (e.g., {name}, {count}).
Keep file formatting consistent with the existing module (4 spaces, newline at EOF).