recon now locates features on Jest (30+) projects as well as vitest.
npx @precisionutilityguild/recon --runner jest "dark mode"
- Runner auto-detection: jest config in package.json, a jest config file, or a declared jest dependency selects the Jest runner; --runner overrides.
- The full gate set from the culprits substrate comes along: Jest below 30 refused up front with the found version named; custom test environments, non-circus runners, and projects configs refused rather than mis-attributed; retries and docblock overrides detected via the collection-count guard.
- Same output contract on both runners: identical test-name shapes, identical partition and Ochiai exclusivity ranking, runner named in --json.
- Field-proven before release: on jest-community/jest-extended (901 tests, ts-jest), feature patterns ranked the implementing matcher file #1 with source-mapped TypeScript lines.
Part of a family: culprits (which line is the bug) · recon (where does feature X live) · diffbisect (which hunks broke the test).