feat(analyzers): syntactic IMPORTS + derived OVERRIDES + tree-sitter resolver name→def fix

[DvirDukhan]

Prerequisites (merge order)

Merge in order — this PR is stacked on:

1. refactor(analyzers): extract TreeSitterAnalyzer base class (T15 #663) #690 — TreeSitterAnalyzer base class (T15)
2. feat(analyzers): tree-sitter Python symbol resolver (T18 #689) #691 — tree-sitter Python symbol resolver (T18)

Base: #691.

---

What

Three graph-quality improvements on top of the T18 tree-sitter resolver (#691):

1. Syntactic IMPORTS edges (File→File). Python import resolution with no LSP — dotted-module-parts matching against an exact+suffix file index. Base build_import_index/resolve_imports hooks added to the analyzer base class; source_analyzer.link_imports wires them after first_pass (once every file has a graph id).
2. Derived OVERRIDES edges. graph.derive_overrides(max_depth=3) derives OVERRIDES from EXTENDS + DEFINES via Cypher MERGE, run after second_pass.
3. Tree-sitter resolver name→def pairing fix (CALLS precision). ts_resolver.py::_index_file built the per-module symbol table by zip-ing two independently-grouped QueryCursor.captures() lists (@name, @def). Decorated defs shift @def positions, mis-pairing names with defs, so imported-call resolution attached CALLS edges to the wrong target (phantom edges whose token never appears at the call site). Fixed via per-match iteration using a _matches() helper wrapping QueryCursor.matches(), applied across all four indexing loops (top-level funcs, classes, assigns, class methods). Adds 2 regression tests (10 top-level funcs, 8 classes) asserting each imported call resolves to the def whose name matches exactly; 16/16 resolver tests pass.

Why

IMPORTS/OVERRIDES edges improve coverage for all consumers and feed search_code hybrid-ranker centrality (cross-file in-degree). The resolver fix corrects CALLS-edge accuracy — the graph's core "who calls X" capability.

Impact (CALLS resolver fix)

Deterministic graph-vs-jedi-oracle caller-accuracy bench, n=40, paired (identical harness, only the resolver differs):

repo	broken macro-F1	fixed macro-F1	median F1	exact-match
uxarray	0.178	0.713	0.0 → 0.94	0.09 → 0.50
arkouda	0.031	0.262	0.0 → 0.12	0.0 → 0.04

Stack

• Base: feat(analyzers): tree-sitter Python symbol resolver (T18 #689) #691 (T18 tree-sitter Python resolver)
• Additive on top of feat(analyzers): tree-sitter Python symbol resolver (T18 #689) #691 (IMPORTS/OVERRIDES +201/-0; resolver fix +97/-26 incl. tests).

Notes

Lineage note: the IMPORTS/OVERRIDES content was authored on the pre-T18 mcp-smoke-combined branch and cherry-picked here. The old jedi-era resolve_path/resolve_type artifacts from that lineage were intentionally dropped during the cherry-pick (T18 removed them); only the 5 new import-resolution methods + base hooks + _extract_type_target (from #691) remain.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

[coderabbitai]

Warning

Review limit reached

@DvirDukhan, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 2 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2c78cf31-4911-484f-9a75-c6a2f7971b60

📥 Commits

Reviewing files that changed from the base of the PR and between c4d3454 and f54f818.

📒 Files selected for processing (7)

• api/analyzers/analyzer.py
• api/analyzers/python/analyzer.py
• api/analyzers/python/ts_resolver.py
• api/analyzers/source_analyzer.py
• api/graph.py
• tests/analyzers/test_tree_sitter_base.py
• tests/analyzers/test_ts_python_resolver.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dvirdukhan/analyzer-import-override-edges

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

The base branch was changed.

[Copilot]

Pull request overview

Improves graph quality and analyzer performance by adding syntactic Python IMPORTS edges, deriving OVERRIDES edges from existing hierarchy relations, and fixing tree-sitter resolver name→definition pairing to improve CALLS accuracy.

Changes:

• Add analyzer hooks + orchestrator wiring to create IMPORTS (File→File) edges after first_pass.
• Add Graph.derive_overrides(max_depth=3) to derive OVERRIDES edges after second_pass.
• Fix tree-sitter Python resolver indexing to iterate per-query match (avoids capture misalignment) and add regression tests.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
api/analyzers/analyzer.py	Adds base hooks (needs_lsp, import index + import resolution defaults) to support static resolvers and import linking.
api/analyzers/source_analyzer.py	Skips Python LSP startup when analyzer can resolve statically; wires link_imports() and derive_overrides() into analysis pipeline.
api/analyzers/python/analyzer.py	Adds env-var-selected tree-sitter resolver and implements Python-only syntactic import resolution (build_import_index/resolve_imports).
api/analyzers/python/ts_resolver.py	Implements project-wide tree-sitter Python symbol resolver; fixes capture pairing via per-match iteration.
api/graph.py	Adds derive_overrides() Cypher query to create OVERRIDES edges post-resolution.
tests/analyzers/test_ts_python_resolver.py	Adds resolver unit/regression tests and env-var integration tests for LSP bypass behavior.

Comments suppressed due to low confidence (2)

tests/analyzers/test_ts_python_resolver.py:9

• pytest is imported but never used in this test module, which will fail ruff check (F401) if linting is enabled for tests.

import pytest

api/graph.py:508

• The WITH DISTINCT sub, sup, length(x) AS depth clause can yield multiple rows for the same (sub,sup) when there are multiple inheritance paths, and whichever row hits MERGE first will set e.depth (not necessarily the shortest distance). Aggregating to min(length(x)) makes depth deterministic and reflects the closest override.

               RETURN collect(callee)"""

        res = self._query(q, {'func_id': func_id})

        return res.result_set[0][0]

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.