docs: add Japanese, Chinese, Korean translations

[yimsk]

Summary

• Add Japanese (ja), Simplified Chinese (zh-CN), and Korean (ko) translations for all user-facing documentation
• Update language switch links in all READMEs with mutual cross-links
• Fix nix GOROOT to prevent system Go mismatch

Changes

18 new files (6 per language × 3 languages):

• README.{ja,zh-CN,ko}.md — Full translated READMEs
• docs/keybindings.{ja,zh-CN,ko}.md — Keybindings reference
• docs/services.{ja,zh-CN,ko}.md — Supported services list
• docs/configuration.{ja,zh-CN,ko}.md — Configuration guide
• docs/iam-permissions.{ja,zh-CN,ko}.md — IAM permissions guide
• docs/ai-chat.{ja,zh-CN,ko}.md — AI chat feature docs

2 modified files:

• README.md — Added language switch links (🇯🇵 🇨🇳 🇰🇷)
• flake.nix — Set GOROOT for nix dev environment

Translation conventions

• Japanese: です/ます体, natural prose
• Chinese: Natural Simplified Chinese
• Korean: 합니다/습니다 체 (formal polite)
• AWS service names, CLI commands, YAML/JSON keys, keyboard shortcuts stay English
• Cross-doc links point to translated variants (.ja.md, .zh-CN.md, .ko.md)
• Developer-facing docs (architecture.md, adding-resources.md) not translated

⚠️ Merge with merge commit (not squash) to keep develop in sync

[claude]

PR Review: Documentation Translations (Japanese, Chinese, Korean)

Summary

This PR adds comprehensive translations for user-facing documentation in Japanese (ja), Simplified Chinese (zh-CN), and Korean (ko). The implementation is well-structured and follows consistent patterns across all three languages.

✅ Strengths

Translation Quality

• Natural language flow: All three translations use appropriate formality levels (Japanese: です/ます体, Chinese: natural Simplified Chinese, Korean: 합니다/습니다 체)
• Consistent terminology: Technical terms (AWS service names, CLI commands, YAML keys, keyboard shortcuts) correctly remain in English across all translations
• Cross-linking: All translated documents properly link to their language-specific variants (e.g., keybindings.ja.md, configuration.zh-CN.md)
• Structural consistency: All translations maintain the same structure, headers, and formatting as the original English documents

Implementation Details

• Language switching: Clean implementation with flag emojis (🇯🇵 🇨🇳 🇰🇷) at the top of READMEs for easy navigation
• Complete coverage: 18 new files covering all major user-facing documentation (README, keybindings, services, configuration, IAM permissions, AI chat)
• Selective translation: Appropriately excludes developer-facing docs (architecture.md, adding-resources.md) which are correctly kept in English
• No code changes: Translation-only PR with no changes to application code, reducing risk

Documentation

• Clear PR description explaining translation conventions and rationale
• Appropriate commit messages following conventional commits style

📋 Minor Observations

Potential Issues (Low Priority)

1. flake.nix change mentioned but not included: The PR description mentions "Fix nix GOROOT to prevent system Go mismatch" but I don't see changes to flake.nix in the files list. This appears to be a documentation issue in the PR description rather than a code issue.

2. Resource count discrepancy:

   • English README says "169 resources"
   • Japanese README says "169リソース"
   • Chinese README says "169 个资源"
   • Korean README says "169개 리소스"
   • Services doc header says "163 resources" in Chinese README (line 114: 全部 69 个服务和 163 个资源)

   This inconsistency exists between the main README (169) and the services documentation reference (163). Should verify which is correct and update accordingly.

3. Mixed language in Documentation section: In all three translated READMEs, the last two documentation links remain in English:

   | [Architecture](docs/architecture.md) | 内部設計と構造 |
   | [Adding Resources](docs/adding-resources.md) | コントリビューター向けガイド |

   This is intentional per the PR description (developer-facing docs not translated), but it creates a slightly inconsistent user experience. Consider either:

   • Translating these documents as well, OR
   • Adding a note indicating these are developer docs available in English only

Suggestions

1. Verification checklist: Consider adding a comment or checklist to verify:

   • All internal links work correctly
   • All code examples run properly
   • Numbers and statistics are consistent across all language versions

2. Translation maintenance: Consider documenting how translations will be maintained when English docs are updated. Perhaps add a CONTRIBUTING guideline about updating translations.

3. Language detection: Future enhancement could include automatic language detection based on browser locale or system settings.

🔒 Security Considerations

✅ No security concerns - this is documentation only with no code changes

🎯 Performance Considerations

✅ No performance impact - static documentation files only

🧪 Test Coverage

N/A - Documentation changes don't require test coverage

📊 Code Quality Score: 9/10

Breakdown:

• Translation Quality: ⭐⭐⭐⭐⭐ (5/5)
• Consistency: ⭐⭐⭐⭐ (4/5) - minor resource count discrepancy
• Completeness: ⭐⭐⭐⭐⭐ (5/5)
• Structure: ⭐⭐⭐⭐⭐ (5/5)

Recommendation

✅ APPROVE - This is an excellent contribution that significantly improves accessibility for Japanese, Chinese, and Korean users. The translations are high-quality, well-structured, and properly linked. The minor issues noted are cosmetic and can be addressed in a follow-up PR if needed.

Before Merge:

1. ✅ Verify the flake.nix mention in the PR description - either include that change or update the description
2. ✅ Consider fixing the 169 vs 163 resource count discrepancy
3. ✅ As noted in the PR description, merge with a merge commit (not squash) to keep develop in sync

Great work! 🚀

---

Review generated by Claude Code