Processed translations

Editor assessment

A standard Crowdin pattern: `chore` for translation sync, a two-part `i18n,client` scope, and the past-tense subject `processed translations` that bends imperative mood but is tolerable for bot output. The compound scope's formatting (no spaces here, spaces elsewhere in the repo) will fragment exact-match filtering — a consistency issue rather than a spec violation, since the spec leaves scope contents to projects. No body, appropriately, and no version impact, which `chore` correctly signals. The header is lowercase, period-free, and compact. It's unobjectionable automation plumbing whose main flaw is contributing to scope-format drift across the log.