[jm-rivera]

tsconfig.json included motion-kit/, and motion-kit/render.tsx imports about 29 app modules through @/, so a product change that broke motion-kit's types failed next build and the production image build in deploy/Dockerfile. The root config now excludes motion-kit, and motion-kit/tsconfig.json extends it as a second project. pnpm typecheck runs tsc --noEmit && tsc --noEmit -p motion-kit, so CI still checks motion-kit, and next build lists no motion-kit file. motion-kit/next-types.d.ts references Next's types for the app's *.module.scss imports; the name avoids the next-env.d.ts pattern .gitignore ignores in every directory.

The four Chrome-backed tests in motion-kit/test/capture.test.ts and motion-kit/test/motion-kit.test.ts skipped when no browser started, so a runner without Chrome dropped them unseen. motion-kit/test/browser.ts holds the shared decision: startBrowser() returns the browser or the launch error, and hasBrowser(t, browser) fails the test with that error when CI is set and skips with it otherwise. GitHub's ubuntu-latest image ships Chrome, so ci.yml is unchanged.

With CHROMIUM_PATH=/nonexistent/chrome, node --test motion-kit/test/*.test.ts passes 14 and skips 4 locally, and fails those 4 under CI=1. A type error added to motion-kit/spec.ts fails pnpm typecheck and passes a root-only tsc --noEmit.