### 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 and C++ are common languages across the industry, and should be supported by Orbit. Example: Embedded vertical with firmware development. #### Challenges **Preprocessor Complexity** C/C++ preprocessor directives (#include, #define, #ifdef) significantly impact code structure. Macros can expand to arbitrary code, and conditional compilation creates multiple code paths. Full expansion requires build context that the parser doesn't have. **Header/Implementation Separation** Declarations in headers are separated from definitions in source files. Linking declarations to implementations requires cross-file analysis and understanding of include paths, which varies per build configuration. **Symbol Resolution Ambiguity** Function overloading (C++), templates, name mangling, and namespace scoping create ambiguity in symbol identification. A single name can refer to multiple entities depending on context, scope, and template instantiation. **Dialect Variations** C has multiple standards (C89, C99, C11, C17), and C++ has even more (C++98, C++11, C++17, C++20, C++23). Compiler-specific extensions further complicate parsing. **Include Path Resolution** System headers, relative includes, and project-specific include paths are build-dependent. The parser cannot reliably resolve `#include <stdio.h>` or `#include "config.h"` without project configuration. ### Proposed Solution Build a C/C++ parser and indexer that extracts code structure (functions, classes, variables, includes) and relationships (who calls whom, what includes what) so the Knowledge Graph can index and search my codebase intelligently. <!--Describe at a high level what the proposed solution is and why it is the best solution.-->