Localization completeness check

--- name: localization-completeness-check description: "A way of working for any change that touches user-facing text. Use when adding or editing strings, translations, dates, numbers or plurals in a product." --- Whenever a change adds, edits or removes text a user can see, treat localization as part of the change, not a follow-up. Checks to run, in order: 1. Hardcoded text. Find user-facing strings that are written directly in the interface instead of the translation files. Move them and give each a stable, descriptive key. 2. Completeness. Compare every supported language against the source language. List keys that are missing, unused or still in the source language by mistake. 3. Placeholders. Confirm each translation keeps the same variables as the original, with the same names. A missing or renamed placeholder is a bug. 4. Plurals and grammar. Check counts such as "1 item" and "2 items" use proper plural forms. Languages differ in how many forms they need, so never build plurals by adding an "s". Avoid sentences assembled from fragments, since word order differs between languages. 5. Formatting. Dates, times, numbers, currencies and units should use the user's locale formatting rather than fixed patterns. 6. Fallback. State what happens when a key is missing: it should fall back to the default language, never show a raw key. 7. Layout. Warn when translated text may be much longer (often 30 percent or more) and could break buttons, menus or tables. Check right-to-left languages if supported. 8. Consistency. Terms like product features should be translated the same way everywhere; list conflicts. Output: a short report with sections for Must fix, Should fix and Looks fine, naming each key or screen concerned. Do not translate text you cannot verify; mark machine-style translations as needing review by a fluent speaker. Keep changes small and do not alter unrelated text.

Overall: Must fix 2, Should fix 1. Must fix - Checkout screen: the label "Pay now" is written directly in the interface. Move it to a key such as checkout.pay_now. - Cart summary, German file: the placeholder {count} is missing, so the item count would not show. Should fix - Item count uses a simple "s" ending. Use proper plural forms so languages with more than two forms work. - Order date is shown in a fixed month/day/year pattern. Use the locale format. Looks fine - Missing keys fall back to the default language and never show a raw key. Note: the French and Spanish strings for the new banner look machine-written and should be reviewed by a fluent speaker.