Deferred from #2139 (native missing interface CHA dispatch edges). #2139's own body flagged this as a low-priority, separate observation:
Tertiary observation (7 edges): odd zero-line "file calls itself" edges
src/db/connection.ts|wrapInjectedRepo|521|calls|src/db/connection.ts|src/db/connection.ts|0
tests/unit/in-memory-repository.test.ts|tests/unit/in-memory-repository.test.ts|0|calls|tests/integration/triage.test.ts|BrokenRepo.findNodesForTriage|276
A handful of wasm-only edges where the source/target name/line is the file path itself at line 0 (module-level edge?), including one pointing at test-double classes (BrokenRepo, InvalidOptsRepo) defined locally in a different test file. Noted for completeness; lower priority than the two patterns above.
Not investigated as part of #2139's fix (which addressed only the dominant interface-multi-implementer pattern). Needs someone to determine: (1) whether these are legitimate module-level dispatch edges WASM correctly produces and native is missing, or (2) a WASM-side bug producing spurious edges keyed by file-node-as-caller/target.
Deferred from #2139 (native missing interface CHA dispatch edges). #2139's own body flagged this as a low-priority, separate observation:
Not investigated as part of #2139's fix (which addressed only the dominant interface-multi-implementer pattern). Needs someone to determine: (1) whether these are legitimate module-level dispatch edges WASM correctly produces and native is missing, or (2) a WASM-side bug producing spurious edges keyed by file-node-as-caller/target.