Module coverage 

Per-language semantic coverage: how many of a language’s file-level call edges are verified, and whether a language server for it can run here. Shared by ctx_graph status, lean-ctx doctor and the dashboard legend.

Structs

GradeCounts

Evidence counts of one language’s file-level calls edges.

NegotiatedBackend

What a backend negotiated for a language at its last start (the initialize handshake), as recorded in <data dir>/semantic-backends.json — across processes, so lean-ctx doctor sees what the MCP server’s backend can do.

ServerStatus

Whether lean-ctx can start a standalone language server for a language.

Functions

coverage_by_language

calls edge evidence grouped by the caller file’s language (the LanguageId spelling: rust, typescript, …), sorted by language.

coverage_lines

One line per language for terminal output, e.g. rust 96/120 verified (80%) · rust-analyzer ✓ · offers definition, references, implementations; no type hierarchy, from coverage_by_language. Sorted by language; deterministic.

negotiated

What the last backend started for language negotiated, if one ever ran.

record_negotiated

Records what a freshly started backend negotiated for language. Written only when it changed; best effort (a status display, not state anything depends on).

server_status

Standalone-server status for a language (LanguageId spelling) in project_root — the server the router would start there (a project’s own TypeScript counts); None when lean-ctx knows no standalone server for it (a JetBrains IDE may still serve it).