i18n-setuplisted

# i18n Setup Follow the project's localization system, keep messages whole, and verify catalogs and layouts as one change. ## 1. Inspect the project and define scope Identify the engine or runtime, build and test commands, current localization library or resource format, source locale, target locales, font pipeline, and supported platforms. Determine whether the request is an audit or includes implementation. Use the project's current, complete source locale as the fallback unless the project or user specifies another. Confirm whether any target locale uses right-to-left layout or grammar that changes around parameters. When it does, read [rtl-and-grammar.md](references/rtl-and-grammar.md) and include that work in scope. ## 2. Inventory player-facing content Sweep the whole project, including: - HUD, menus, tutorial, hints, victory, failure, and pause screens; - validation, recoverable errors, and player-facing system messages; - scene, canvas, sprite, or world-space text outside the main UI layer; - concatenated messages that need parameters; - titles, share text, store or page metadata used by the target build; - text baked into images or sprite sheets, reported as replacement assets. Leave debug logs and internal identifiers unchanged unless they are visible to players. Record each source location so a second sweep can prove extraction is complete. ## 3. Use or establish the message system Follow the existing library's catalog format, namespace, fallback mechanis