Nothing in the shipped code starts an LSP server#
Language-server support is fully built but nothing in the app ever starts one, so it stays dark.
A language-server manager with start, restart and shutdown exists in the bundle, but nothing calls it and the LSP tool only reads connection status.
What's wrong with this entry?
The language-server support has a manager with start, restart and shutdown entry points, but none of them are called anywhere in the shipped bundle. The LSP tool only ever reads connection status, so in practice no server is launched and the tool stays dark.
- The manager exposes get, status, connected, ever-connected, wait-for-initialization, initialize, reinitialize and shutdown; only the four read-only ones have callers.
- The tool's own code waits on initialization if status is pending and checks the ever-connected flag to decide whether it is enabled, but nothing triggers the initialization it waits for.
- The initializer additionally returns early unless the
lspServersfeature flag is on, so even a future caller would be gated. - Same shape as the previous build; this is not new in 2.1.243.
[LSP MANAGER] initializeLspServerManager() called
Strings lifted out of the shipped bundle, so the claim above can be checked against them.