Production i18n, pluralization, and translation policy

All user-visible production text must use i18n keys; feature work adds only English source strings and relies on fallback until translations are reviewed. Preserve migrated English byte-for-byte unless copy changes are requested. Prefer complete phrases over concatenated fragments; placeholders are only for irreducible names, paths, and counts. Count-sensitive text must call language.plural(baseKey, count, params)—never construct plural keys or pass categories to language.t. Keep locale and grammar logic behind shared typed APIs. Translations require research against CLDR, platform guidance, the locale authority, and at least two maintained corpora; preserve placeholders, code, and product names, cite sources, and flag uncertain regional terms or intentional English borrowings.