[Frontend] Complete real i18n for es and tl and guard parity in CI

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

The settings page states that only English is fully translated, yet messages/es.json and messages/tl.json have the same keys as English, which means they likely hold English copy. Spanish and Tagalog users see English. There is also no locale switcher wired and no guard preventing future key drift.

Acceptance criteria

• Provide genuine es and tl translations for all 95 keys (no English fallthrough left in place)
• Wire a working locale switcher in settings that persists the choice and updates the URL locale segment
• Add a CI check that fails when locales drift from the en key set (missing or extra keys)
• Remove the coming soon i18n notice once switching works

Files to touch

• messages/en.json, messages/es.json, messages/tl.json
• i18n.config.ts
• src/app/[locale]/settings/page.tsx
• .github/workflows/ci.yml (parity check) or a scripts/ checker

Out of scope

• Adding new locales beyond es and tl
• RTL support

[legend4tech]

Hello, I’m Legend4Tech, a full-stack developer and top open-source contributor, previously a fellow at OnlyDust. I’m interested in contributing to this issue and would be happy to help implement a solution, fix bugs, or improve features as needed. I’m ready to follow the project’s workflow and coding standards to ensure smooth collaboration.

[grantfox-oss]

🦊 GrantFox — @legend4tech has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.