i18n-completeness

```bash

bun run check:i18n

```

🔴 Missing Keys (Critical)

• Keys used in code but not present in translation files
• Priority: Critical (causes runtime errors)
• Impact: Displays raw translation keys to users
• Action: Add missing keys to all translation files immediately

📝 Hardcoded Strings (i18n Compliance)

• User-facing strings not using t() function
• Examples: "AI Replay", "Start AI", "Loading..."
• Scope: Production code only (test files excluded)
• Action: Convert to translation keys for proper localization

🔄 Dynamic Key Patterns (Analysis Required)

• Template literal patterns like t(\game.${type}\)
• Analysis: Validates all possible key combinations exist
• Action: Verify all generated keys are defined

⚠️ Unused Keys (Optimization)

• Keys present in translation files but not used in code
• Priority: Medium (cleanup opportunity)
• Action: Remove unnecessary keys to optimize file size

1. Execute Check: Run bun run check:i18n
2. Identify Issues: List Missing/Unused keys
3. Propose Fixes: Present specific correction methods
4. Confirm Execution: Ask user to approve modifications
5. Apply Fixes: Update translation files after approval
6. Verify: Re-run check after modifications

• src/assets/locales/ja.json - Japanese translations (default)
• src/assets/locales/en.json - English translations

• Re-verify usage before key deletion
• Execute consistent operations across all language files
• Validate JSON syntax after modifications
• Confirm no issues with tests and build

• "Check translations"
• "i18n consistency check"
• "Are all translation keys defined?"
• "Find hardcoded strings"
• "Translation cleanup"
• "Localization issues"
• "Missing translation keys"