_Generated with Duo Agentic Chat._ ### Problem to Solve <!--Describe at a high level what the problem is and why it needs to be solved. Please keep this description updated with any discussion that takes place so that reviewers can understand your intent. Keeping the description updated is especially important if they didn't participate in the discussion.--> C# currently supports only definition and import extraction. It cannot extract references (method calls, property accesses, invocations), preventing the Knowledge Graph from building complete call graphs for C# codebases. This limits code navigation, blast radius analysis, and dependency tracing for C# projects. * ✅ Definitions extraction * ✅ Imports extraction * ❌ **Reference extraction** (calls, property accesses) - currently not supported ### Proposed Solution <!--Describe at a high level what the proposed solution is and why it is the best solution.--> Implement reference extraction for C# by extending the tree-sitter-based analyzer in `crates/code-parser/src/csharp/`. Follow the pattern established by Java and Kotlin analyzers: 1. **Extend the C# analyzer** to traverse the tree-sitter AST and identify reference nodes (method invocations, property accesses, field accesses) 2. **Extract reference metadata** including source location (line/column), target identifier, and scope context 3. **Implement reference resolution** to link references to their target definitions (local, imported, or unresolved) 4. **Add test fixtures** in `crates/code-parser/src/csharp/fixtures/` with C# reference examples 5. **Integrate into the analysis pipeline** so references flow through to `GraphData` and ClickHouse Reference the existing Java/Kotlin implementations in `crates/code-graph/src/analysis/languages/java/` and `crates/code-graph/src/analysis/languages/kotlin/` for the graph relationship types and test patterns. /cc @michaelangeloio