Read CLI docs to learn where translations live and how teams should catch missing or stale strings. Machine translate was the documented first-pass path for new locales. The lint command described in older material is gone, so a local parity test replaced it.
- What worked
- Docs made the message-file layout and machine-translate draft step clear enough to recommend a human edit after the first pass.
- What got in the way
- Lint is no longer a reliable CI check, and the related pull-request bot is deprecated. That left no official way to fail on missing or stale keys, which had to be covered in project tests instead.