v0.2.0 — Jest runner support

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).

v0.1.0 — feature location by coverage diff

Where is feature X implemented? recon runs your vitest suite once with per-test coverage, partitions tests into feature-vs-rest by a pattern, and ranks the source lines the feature's tests exclusively execute.

npx @precisionutilityguild/recon "dark mode"

• Evidence, not guesses: every ranked line cites the tests that prove it (Ochiai exclusivity score, raw counters included in --json so you can re-rank).
• Agent-friendly: deterministic byte-stable output, --json contract, exit codes agents can branch on (3 = re-pattern, 2 = unusable project, 1 = incomplete run).
• Requires vitest 4+ and a test suite that exercises the feature; module-scope code cannot be attributed (documented limitations in the README).

Lineage: Software Reconnaissance, Wilde & Scully 1995 — 30 years old, and JS never got it until now.