Enforce locale key parity and English fallback in i18n

[priscaenoch]

Problem

The i18n layer ships three locales — src/i18n/locales/en.ts, es.ts, and ko.ts — that must stay in sync. Nothing verifies they share the same set of translation keys, so a key added to en.ts but not to es.ts/ko.ts will surface as a missing/blank string for those users, and there is no guaranteed fallback to English for missing keys.

What needs to be done

• Ensure the i18n lookup falls back to the English string when a key is missing in the active locale.
• Add a check (unit test or script) that fails when the non-English locales do not have the same key set as en.ts.
• Wire that check into CI so drift is caught on pull requests.
• Fill in (or explicitly mark) any keys currently missing from es.ts/ko.ts.

Files

• src/i18n/index.ts, src/i18n/locales/*.ts
• CI workflow

Acceptance deliverables

• Missing keys fall back to English rather than rendering blank.
• CI fails when locales diverge in their key sets.
• All CI checks pass; the change cannot be merged until CI is green.

Tests to pass

• Test: es/ko key sets match en.
• Test: a missing key resolves to the English string.

[1CryptoQueen]

I'm excited to apply for this issue. I've worked with i18n localization before and I understand the importance of keeping translation keys in sync across all supported languages.

My approach:

1. Audit the current locale files. I'll compare en.ts against es.ts and ko.ts to identify every missing key and document them.

2. Update the i18n configuration in src/i18n/index.ts to add a proper fallback to English for any missing keys. I'll make sure the fallback is clean and doesn't introduce any performance issues.

3. Write a comprehensive test that compares key sets across all three locale files. This test will fail immediately if any key is missing from es.ts or ko.ts and clearly indicate which keys are missing and which file they're missing from.

4. Integrate this test into the CI workflow so it runs on every pull request. I'll make sure the CI output is clear and easy to understand so maintainers know exactly what needs fixing.

5. Fill in all missing keys in es.ts and ko.ts. For any keys that are genuinely ambiguous or hard to translate, I'll explicitly mark them and leave clear comments so the community can help fill them in later.

I can have the first draft of the PR ready within 24-48 hours. I'll write clean, well-documented code and make sure all acceptance criteria are met and all tests pass.
Thanks for considering my application. Looking forward to contributing to this project.

[grantfox-oss]

🦊 GrantFox — @1CryptoQueen has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #49)
2. Your PR will be reviewed by the octraban maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@1CryptoQueen's PR #61 was approved and merged by @priscaenoch.

🏆 @1CryptoQueen: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (48 total points). Track your full progress on GrantFox.

👏 Great work, @1CryptoQueen! Keep contributing to octraban.