Add test intelligence graph edges

[sameer2191]

Summary

• extract common JavaScript/TypeScript, pytest, Go, JUnit, Rust, and Swift test cases as graph nodes
• add TESTS edges from test cases to referenced functions, methods, classes, and route paths
• document test-to-code graph support in the README, agent guide, research notes, and package metadata

Validation

• npm run build
• node --test --experimental-sqlite dist/tests/indexer.test.js
• npm run verify
• npm run package:check
• npm pack --dry-run
• npm run audit:prod
• git diff --check
• rg recruiter/career wording scan returned no matches

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8295801934

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Delete stale TESTS edges during incremental rebuilds

Because TESTS is inserted here as a derived, whole-graph edge but store.deleteDerivedEdges() does not remove TESTS, incremental rebuilds can retain obsolete test coverage. For example, after an initial test links to a unique createOrder, adding another createOrder in a different unchanged endpoint file makes addTestEdges suppress the ambiguous edge, but the old row remains because neither the test nor original target file was deleted.

Useful? React with 👍 / 👎.