task: Graph queries & trace_path resolution

[DeusData]

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 returns empty for all functions despite traversable CALLS edges (v0.8.1, macOS arm64) #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