Summary
cdidx languages --capability references --json currently returns the same set as --capability graph, while languages --json only exposes symbol_extraction and graph_queries. That makes it hard to audit which languages have searchable text only, symbol extraction only, or reference edges.
Evidence
cdidx languages --capability graph --json and cdidx languages --capability references --json produce the same language list.src/CodeIndex/Cli/QueryCommandRunner.cs filters by LanguageMatchesCapability, but the JSON contract only has symbol_extraction and graph_queries.status --check --json can show indexed languages and graph-supported languages, but not a per-language unsupported reason or extraction gap.
Expected direction
Expose separate capability fields for symbols, references, and graph queries; include unsupported/gap reasons when available; and add filters for missing capabilities so audit runs can list search-only languages directly.
Summary
cdidx languages --capability references --jsoncurrently returns the same set as--capability graph, whilelanguages --jsononly exposessymbol_extractionandgraph_queries. That makes it hard to audit which languages have searchable text only, symbol extraction only, or reference edges.Evidence
cdidx languages --capability graph --jsonandcdidx languages --capability references --jsonproduce the same language list.src/CodeIndex/Cli/QueryCommandRunner.csfilters byLanguageMatchesCapability, but the JSON contract only hassymbol_extractionandgraph_queries.status --check --jsoncan show indexed languages and graph-supported languages, but not a per-language unsupported reason or extraction gap.Expected direction
Expose separate capability fields for symbols, references, and graph queries; include unsupported/gap reasons when available; and add filters for missing capabilities so audit runs can list search-only languages directly.