Summary

Two members of the "value-position reference produces no edge" family (#2257, #2260):

1. A JSX element is not a reference to its component. <Header /> produced no edge to Header.
2. An identifier passed as a call argument is not a use. Factory.create(AppModule) produced no edge to AppModule.

Both are structural, not edge cases: every React component used only as JSX read as dead, and NestJS's module/controller registration pattern (NestFactory.create(AppModule)) relies entirely on the second pattern — depressing caller coverage and inflating dead-code counts across every React/NestJS repo in the org rollout.

Changes

Both patterns are extracted as value-ref dynamic calls — the existing mechanism already used for object-literal property values, instanceof operands, and logical-or/ternary fallbacks (#1771/#1895/#2257):

• JSX element reference (handleJsxElementRef): a JSX opening/self-closing element's tag name is credited as a reference to the component it renders, gated on JSX's own capitalization convention — lowercase (<div>, <span>) is an intrinsic DOM element, never a symbol reference; a member_expression name (<Namespace.Component />) credits the base object identifier.
• Call-argument identifier reference (extractCallArgumentIdentifierRefs): a capitalized bare identifier passed as a call argument is credited as a reference to whatever it names.

Why capitalized-only for call arguments

This restriction isn't stylistic — it's load-bearing. Issue #1741 is an existing regression guard proving that crediting an arbitrary lowercase DATA argument (e.g. analyzeDrift(communities, communityDirs)) as any kind of reference risks the global-fallback resolver binding it to an unrelated same-named function elsewhere in the repo, fabricating a call edge and, transitively, a phantom cycle. My first pass at this fix did exactly that and broke 13 existing tests locally before I caught it. A class/component reference passed by value is overwhelmingly PascalCase in JS/TS convention, so restricting to capitalized identifiers satisfies #2389's request without reopening #1741 — verified all 13 previously-broken tests pass again with this restriction in place.

Engine parity

Mirrored in crates/codegraph-core/src/extractors/javascript.rs.

The WASM query-based extraction path required new tree-sitter query patterns scoped to only the javascript/tsx grammars — plain .ts (no JSX) has no JSX node types at all, so folding them into the shared TypeScript pattern set would throw at Query() compile time and break all .ts parsing. These patterns are duplicated in both src/domain/parser.ts and the isolated wasm-worker-entry.ts (which intentionally keeps its own copy to avoid importing parser.ts's non-worker-safe process-global caches) — I initially only updated parser.ts and the fix silently didn't work through the real WASM worker pool. A new query-vs-walk parity test case for a capitalized JSX tag catches exactly this class of omission; verified it fails against the pre-fix wasm-worker-entry.ts before confirming it passes with the fix.

Verification

• cargo fmt -- --check / cargo clippy --workspace --all-targets -- -D warnings: pass
• npx vitest run tests/parsers/javascript.test.ts: 382/382 pass (8 new tests added, all 13 previously-regressed callback-extraction tests still pass with the capitalization restriction)
• npx vitest run tests/engines/query-walk-parity.test.ts: 25/25 pass (3 new JSX/call-argument parity cases added; verified they fail against the pre-fix wasm-worker-entry.ts and pass against the fix)
• cargo test --package codegraph-core extractors::javascript: 299/299 pass (6 new Rust tests added, including a regression guard mirroring bug(resolver): identifier-arg dynamic call resolution fabricates false edges/cycles on name collision (e.g. communities.ts phantom cycle) #1741)
• npx vitest run tests/parsers/ tests/engines/: 1120/1128 pass (8 skipped, pre-existing)
• npx vitest run tests/integration/: 1483/1487 pass (2 skipped, 2 todo, pre-existing)
• npm run lint: pass
• Manually reproduced both of the issue's exact fixtures against a freshly built native addon (napi build) and the WASM engine: Header/AppModule now both show "Used in: ..." on both engines, with identical node/edge counts

Closes #2389