code-intelligence

When LSP returns empty reference results, apply a degradation gate to fall back to text search tools like rg or semantic search. Disclose that LSP results were unreliable so the fallback routing remains transparent and deterministic across languages.

Choose between LSP and ripgrep for symbol navigation by checking language-server availability. Use LSP for semantic accuracy when available, and route to ripgrep text search when the LSP server is degraded or entirely unavailable to maintain workflow efficiency.

You need semantic search for code intelligence tasks when LSP is unavailable or returns unreliable results and standard text search lacks the context to gather accurate references. It serves as a structured fallback within the degradation gate.

Yes, code intelligence routing works across all programming languages by dynamically matching the task with the correct analysis tool. It adapts based on whether a language server is available, falling back to rg or semantic search when LSP support is absent.

LSP fails to gather references when the language server is degraded or lacks full project indexing. Handle the fallback by triggering the degradation gate to route to rg or semantic search, and disclose the fallback details to ensure workflow transparency.

An LSP server is required for primary semantic analysis, but the routing workflow explicitly handles environments where it is missing. If LSP is unavailable, the degradation gate automatically routes codebase discovery tasks to text search or semantic search alternatives.