task: Graph queries & trace_path resolution #594

Scope

Umbrella tracker for graph query & trace_path resolution — cases where the graph contains the right nodes/edges but the query-side traversal returns empty or incomplete caller/callee sets. The edges exist; the answer is wrong.

Sub-issues

• trace_path silently accepts invalid direction values and returns empty results #480 — trace_path returns empty for all functions despite traversable CALLS edges (v0.8.1, macOS arm64)
• trace_path data_flow mode doesn't surface arg expressions; NestJS DI patterns defeat ~70% of caller resolution #514 — trace_path data_flow mode doesn't surface arg expressions; NestJS DI patterns defeat ~70% of caller resolution
• trace_path / reverse-dependency returns an INCOMPLETE caller set when a symbol is duplicated by an ambient .d.ts declaration (callers silently split by import style) #546 — trace_path / reverse-dependency returns an INCOMPLETE caller set when a symbol is duplicated by an ambient .d.ts declaration (callers silently split by import style)

Acceptance

Per item: a reproduce-first test on a public fixture showing the expected caller/callee set, then the traversal returns it. #480 in particular needs a root-cause test (edges present, traversal yields nothing) before any fix.

Why one task

These all live in the traversal/query layer (BFS over CALLS, symbol identity / dedup, data-flow arg resolution) rather than extraction. Grouping keeps the query-correctness work coherent.

Added 2026-06-29 (triage)

• C/C++ CALLS edges are attributed to the File/Module, not the enclosing function — callers are file-level, callees are empty (Python is correct) #694 — C/C++ calls have file-level callers and empty callees
• Inconsistencies/bugs in the vscode codex extension #658 — Cypher projection aliases collapse to one returned column
• get_architecture and query tools always return "project not found" on Linux — store never opened (strace confirms no .db openat) #640 — query tools report project not found while list_projects sees the DB
• Crash when calling query_graph #627 — query_graph crash on Windows
• [bug] query_graph hangs on whole-graph OPTIONAL MATCH (no execution timeout / degradation) on large graphs #601 — unbounded OPTIONAL MATCH can hang without an execution timeout

Added 2026-06-30 (triage)

• query_graph / search_graph return "project not found" inconsistently; DBs valid on disk but CLI looks up wrong inode #704 — query tools report project not found although list_projects sees populated DB; likely path-normalized shadow DB
• get_architecture hotspots report inflated fan_in that contradicts actual graph in-degree (same-name collision across languages) #725 — get_architecture hotspot fan_in aggregates same-name symbols instead of node-level in-degree

Added 2026-07-09 (triage)

• query_graph Cypher: coalesce() in WHERE rejected (unexpected operator) #874 — query_graph Cypher: coalesce() in WHERE rejected (unexpected operator)
• CALLS edges fall back to File/Module node when enclosing_func_qn is unset — trace_path returns empty (root cause for #694/#480/#686/#678/#523) #763 — CALLS edges fall back to File/Module when enclosing_func_qn is unset — root cause behind C/C++ CALLS edges are attributed to the File/Module, not the enclosing function — callers are file-level, callees are empty (Python is correct) #694/trace_path silently accepts invalid direction values and returns empty results #480/Go services get 0 cross-repo edges (Fiber route paths empty, gRPC not captured) #686/cross-repo-intelligence: 0 edges for FastAPI backend — Route.path empty, router prefix stripped #678/cross-repo-intelligence returns 0 edges for a byte-identical call/route #523

(#797 var-length path semantics → PR #883; #875 aliased imports → fixed by #979.)

Added 2026-08-03 (triage)

• check_index_coverage: echoed scope has its first min(len,8) bytes zeroed (payload is correct; . is exempt) #1381 — check_index_coverage corrupts the echoed scope prefix
• search_graph: Route nodes have empty file_path, so label=Route + file_pattern always returns 0 — and the hint blames the label #1366 — Route file_path filtering returns zero and emits a misleading hint
• trace_path(outbound): qualified_name resolves to a different start node than the bare name — returns unrelated callees (incl. markdown Section nodes), or empty despite existing CALLS edges #1365 — trace_path resolves qualified names through an unrelated bare-name node
• query_graph: multi-key ORDER BY silently drops LIMIT (6326 rows / 117 KB instead of 5) on v0.9.1-rc.1 #1334 — multi-key ORDER BY silently drops LIMIT