fix(react-port): use pinned Jest test discovery - #2659

Summary

Use a verified list from Jest 29.7.0 for conventional test discovery at the immutable Framer Motion 12.42.2 pin. Keep explicit test selectors, inline sources, and compile-only tests in the inventory.

Closes #2658. Both upstream Jest configs select named tests under src. Treating every __tests__ module as a test makes the port preflight require a registration in a support helper.

Validation

• pnpm format:check
• pnpm typecheck
• pnpm test
• All 379 React port tests, including 32 preflight tests, plus targeted formatting, pnpm sync, and git diff --check.
• Pinned Jest --listTests returned 94 client and 3 SSR paths. The independent preflight inventory matched all 97 and extracted 822 static registrations, including two type-test files.
• The real preflight CLI passed license and test evidence for the immutable package-subdirectory URL. Regression controls exercise a missing test, a changed witness, a selected test without registrations, and independent explicit, inline, and type tests.
• Performance review is inapplicable. This is repository tooling.
• Concision review. Reuse the existing pinned profile and Git tree inventory. A general Jest config evaluator would add runner execution or require reproducing Jest's configuration and matching rules.

Risk / follow-ups

The pinned list replaces Jest's convention fallback for this package and commit. Explicit selectors remain additive. The CLI still reports pending intake until the graph's dependencies are classified. Static inventory establishes selection and registrations.

Provenance

• An agent produced this diff (agent-authored)

Codex task · host com-79386

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}