fix(cli): add dev.usePseudotranslator to config schema (v1.14)

[cherkanovart]

Summary

• Extends I18nConfig schema to v1.14 with a dev.usePseudotranslator optional field
• Updates CLI setup to check both --pseudo flag and dev.usePseudotranslator config for provider selection and auth skipping
• Addresses the review feedback on fix(cli): respect dev.usePseudotranslator config to skip API validation #1984: the setup.ts changes are correct but have no effect without the schema update, since Zod strips unknown keys during parsing

Context

PR #1984 correctly modified setup.ts to check ctx.config?.dev?.usePseudotranslator, but the I18nConfig schema (v1.13) has no dev field — Zod's safeParse() strips it during parsing, so the value is always undefined at runtime.

This PR adds the missing schema definition so the config value actually reaches the CLI.

Test plan

• Existing config spec tests pass (v0 through v1.13 upgrade paths unaffected)
• New tests for parsing config with and without dev field
• TypeScript compiles cleanly after spec package build

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added dev.usePseudotranslator configuration option to enable pseudo translator mode directly from your config file, complementing existing CLI flags.
  • CLI now recognizes and applies the pseudo translator setting from configuration files.

• Tests

  • Extended test coverage to verify configuration schema updates and dev settings field parsing.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f0d52f and d96871a.

📒 Files selected for processing (4)

• .changeset/pseudo-config-schema.md
• packages/cli/src/cli/cmd/run/setup.ts
• packages/spec/src/config.spec.ts
• packages/spec/src/config.ts

---

📝 Walkthrough

Walkthrough

Introduces configuration version 1.14 with a new dev.usePseudotranslator flag, updates CLI setup to recognize this config field for pseudo-translation mode, extends the config schema with devSettingsSchema, and adds public parsing utilities to the spec module.

Changes

Cohort / File(s)	Summary
Changeset Documentation .changeset/pseudo-config-schema.md	Changelog entry documenting patch updates to @lingo.dev/_spec and lingo.dev packages, noting CLI setup fix for dev.usePseudotranslator schema support.
Config Schema & Definitions packages/spec/src/config.ts	Introduces v1.14 config definition with optional dev field containing usePseudotranslator flag; updates LATEST_CONFIG_DEFINITION reference; exports new parseI18nConfig() function and defaultConfig constant.
Config Tests packages/spec/src/config.spec.ts	Adds tests verifying dev.usePseudotranslator config parsing and version field preservation; includes test for absent dev field resulting in undefined.
CLI Setup Logic packages/cli/src/cli/cmd/run/setup.ts	Extends localization provider selection to treat ctx.config.dev.usePseudotranslator equivalent to ctx.flags.pseudo; tightens authentication condition to skip when pseudo mode or dev.usePseudotranslator is active.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

• fix(cli): respect dev.usePseudotranslator config to skip API key validation #1983: PR directly addresses the same dev.usePseudotranslator feature for treating config field equivalent to --pseudo flag in CLI setup.

Possibly related PRs

• fix(cli): show correct status messages for vNext provider #1968: Modifies the same setup.ts file to adjust provider-selection and authentication conditionals.
• feat(cli): add localizableKeys config option to bypass untranslatable… #2004: Modifies the same config schema file (packages/spec/src/config.ts) for schema version definitions and public API exports.

Suggested reviewers

• AndreyHirsa
• vrcprl

Poem

🐰 A config field hops into v1.14,
Dev.usePseudotranslator, oh how quite neat!
No flags needed when config's in place,
Pseudo-mode now runs at its own pace,
The schema's updated, the CLI's aware—
All set! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding dev.usePseudotranslator to the config schema with the version bump to v1.14.
Description check	✅ Passed	The description covers the summary, changes, and testing plan thoroughly. All required template sections are present and appropriately filled with relevant details about the schema extension and CLI updates.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/pseudo-config-schema

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}