thalarch-localizationlisted

# Thalarch Localization Localization completeness is a product contract, not a side effect of the default locale compiling. ## 1. Discover the real locale surface Inspect the repository rather than assuming a language list. Identify: - default locale resources; - all translated locale/resource sets; - plural/select resources; - locale-specific assets/layout behavior where present; - existing translation conventions and terminology; - generated/localization tooling if the project uses one. Do not add a new parallel i18n system when the project already has one. ## 2. Key parity For changed user-facing strings, check: - missing keys; - extra/stale keys when relevant; - duplicate keys; - raw/unresolved key display risk; - fallback to the default language that would create mixed-language screens. A successful default-locale build does not prove translated resource parity. ## 3. Placeholder and formatting safety Preserve the semantic contract of: - positional placeholders such as `%1$s`, `%2$d`; - number/date/time formatting; - plural quantities; - escaped apostrophes/quotes where the resource format requires them; - markup/spans; - newline intent; - parameter order differences across languages. Never "fix" a translation by deleting a placeholder needed by call-site logic. ## 4. Natural terminology Translate for the product/domain, not word-by-word. For established technical/product terms, determine whether the target locale normally: - translates them; - translit