Processed translations

Editor assessment

Crowdin-style translation syncs are fine as `chore`, but this header has hygiene issues. The comma-joined scope `i18n,client` is a two-token scope whose exact formatting matters: elsewhere in the same repo scopes appear with spaces (`learn, i18n`), so tooling doing exact-match filtering will treat them as distinct groups. The subject `processed translations` is a past-tense noun phrase rather than an imperative; `process translations` would conform. Lowercase, no trailing period, and short length are fine, and no body is expected for bot output. Since translation content doesn't affect the shipped runtime API, no bump implications arise — which is exactly what `chore` communicates. Adequate for automation, inconsistent for humans.