feat(i18n): add eloqnt lint to catch translation errors

[amannn]

Hey! I'm the maintainer of next-intl and I've recently been working on eloqnt/cli, a linter for translation files. I've been running it against public repos to see whether their catalogs carry errors.

On the Umami repo, it found 83 errors across the 53 translated locales:

• inconsistent-args: 57
• unreachable-plural-case: 16
• superfluous-key: 9
• inconsistent-exact-plurals: 1

The largest group is message.share-url, where the English string was reworded and lost its argument, but 37 locales still interpolate {target}:

en-US: Your website stats are publicly available at the following URL:
es-ES: Esta es la URL pública para {target}.

All four call sites (WebsiteShareForm, BoardShareDialog, LinkShareForm, PixelShareForm) call t(messages.shareUrl) without values, so in those 37 locales next-intl fails with MISSING_FORMAT_VALUE and renders the key instead of the sentence.

This PR fixes all 83 and adds the linter so they don't come back. The handful of strings where source text had changed meaning were regenerated with eloqnt translate.

Up to you if you're interested in adopting eloqnt/cli, but you might want the translation fixes in this PR to fix runtime errors and more.

Related:

• I found your check-missing-messages.js does a similar thing, eloqnt lint goes a bit further though
• It seems like your ga-ES.json contains Galician, ga is however Irish (Gaeilge)—maybe this should be fixed too?

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

@amannn is attempting to deploy a commit to the Umami Software Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

This PR adds Eloqnt translation linting to CI and repairs ICU argument and plural inconsistencies across the locale catalogs.

• Adds .eloqnt/config.ts, the lint:i18n package script, and a CI lint step.
• Adds @eloqnt/cli and its transitive dependencies.
• Updates affected translations to match the source catalog's interpolation and plural structure.

Confidence Score: 4/5

The PR appears safe to merge, with only non-blocking lockfile cleanup recommended to avoid unrelated dependency churn.

The translation and CI changes have no identified behavioral defect, but the generated lockfile modifies existing build-tool resolutions beyond the dependency graph needed for the new linter.

Files Needing Attention: pnpm-lock.yaml

Important Files Changed

Filename	Overview
.eloqnt/config.ts	Configures the en-US source catalog, inferred JSON locales, and disables orphan detection for dynamically mapped message keys.
.github/workflows/ci.yml	Runs translation linting after dependency installation and before tests and builds.
package.json	Adds the Eloqnt lint script and CLI development dependency.
pnpm-lock.yaml	Locks the new CLI and its transitive dependencies but also contains unrelated dependency-resolution and platform-metadata churn.
public/intl/messages/ga-ES.json	Corrects localized ICU argument structure to remain compatible with source-message call sites.
public/intl/messages/km-KH.json	Corrects localized ICU argument structure to remain compatible with source-message call sites.

_{Reviews (1): Last reviewed commit: "feat(i18n): add `eloqnt lint` to catch t..." | Re-trigger Greptile}

[greptile-apps]

Unrelated lockfile resolution churn

Adding @eloqnt/cli also changes existing build-tool resolutions, including tsup's @swc/core version, and removes platform metadata throughout the lockfile. Regenerate it with the repository's CI pnpm version so the dependency change remains scoped and future updates stay auditable.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[amannn]

@franciscao633 I've just rebased this PR, are you by chance interested?