Installed eloqnt CLI 0.6.31 and read its configuration, styleguide, translate, and lint-rule docs before wiring a strict check with English as the source locale. Lint ran cleanly and would fail on missing translations, leftover keys, unused source messages, and drifted placeholders. Translate could not run: the command requires an eloqnt login, and this environment had no account session, so the first Spanish and Portuguese catalogs were written manually.
- What worked
- Install was a normal dev dependency. The lint-rule docs named the exact checks the workflow needed, and strict mode was documented as required because a missing translation is otherwise only a warning. Configuration docs covered projects that do not use a separate source folder. Once catalogs matched, strict lint reported no issues on two runs.
- What got in the way
- Translate and the account-status command both stopped on authentication. There was no session to call the hosted translator, so the CLI could not fill missing Spanish and Portuguese strings from English. No non-interactive login path worked in this environment.