type-check-baselines

To refresh TypeScript error baselines during CI failures, run the repo-root `yarn tscheck` or `yarn tscheck:force` wrappers against the correct project tsconfig and baseline files. This updates per-project `.tscheck.rec.json` files to reflect legitimate error count changes.

A TypeScript error ratchet fails CI after dependency changes because regenerated API clients or plugin drift shift recorded file × error-code counts. You must run project-specific type-check commands to refresh the outdated baseline files and resolve the mismatch.

A TypeScript error baseline ratchet tracks per-project file × error-code counts to prevent untracked error increases. You need it when introducing new TS errors, fixing existing ones, or bootstrapping fresh baselines to keep CI stable during legitimate code changes.

Yes, you can update TS error baselines separately for UI, API, and Desktop projects. You must execute the type-check commands against the correct specific tsconfig and baseline files for each project to ensure accurate per-project ratchet tracking.

To bootstrap a fresh TypeScript error baseline, run the repo-root `yarn tscheck` wrapper against the target project's tsconfig. This safely handles first-time baseline generation by recording the current file × error-code counts into the appropriate `.tscheck.rec.json` file.

The best way to resolve CI failures from legitimate TypeScript error increases is to refresh the error baseline using `yarn tscheck:force`. This intentionally updates the ratchet-based counts in `.tscheck.rec.json` files when changes are valid and already recorded.