Problem
Extractor plugin and pattern-config loading failures are difficult to discover during indexing. Several paths catch load failures defensively, but users do not get a clear status signal that a plugin or pattern file was skipped.
Impact
During code search audits it is hard to tell whether custom extractors are active, ignored, malformed, or partially loaded, which slows debugging and weakens confidence in coverage.
Expected
Expose plugin and pattern-load diagnostics in cdidx status --json and the MCP status response, including loaded counts, skipped files, and bounded error summaries.
Problem
Extractor plugin and pattern-config loading failures are difficult to discover during indexing. Several paths catch load failures defensively, but users do not get a clear
statussignal that a plugin or pattern file was skipped.Impact
During code search audits it is hard to tell whether custom extractors are active, ignored, malformed, or partially loaded, which slows debugging and weakens confidence in coverage.
Expected
Expose plugin and pattern-load diagnostics in
cdidx status --jsonand the MCP status response, including loaded counts, skipped files, and bounded error summaries.