LSP status indicator: 'rust-analyzer...' initializing text never updates after init completes

[JDonaghy]

Symptom

The status bar / LSP indicator shows `rust-analyzer...` (the initializing-with-trailing-ellipsis variant) and never transitions to the running / indexed state, even after rust-analyzer finishes initializing and is happily serving hover / completion / definition requests.

Expected

Per Session 243 (`PROJECT_STATE.md` memory): `LspStatus::Initializing(name)` downgrades to `LspStatus::Running(name)` once `server_has_responded == true` AND semantic tokens have arrived (or workspace indexing completes). The status text should drop the `...` ellipsis once that happens.

Reality

Hover (`K`), completion, and other LSP-driven features all work — confirming rust-analyzer responded — but the indicator stays in the initializing state.

Likely cause

Either:

1. `LspManager::server_has_responded` isn't being marked `true` from the response handlers (hover / definition / completion paths missed the `mark_server_responded()` call).
2. The render-side downgrade in `Engine::lsp_status_for_buffer` checks `BufferState.semantic_tokens.is_empty()` and rust-analyzer isn't returning semantic tokens for this buffer (or they're not populating the cache).

Files

• `src/core/lsp.rs` — `mark_server_responded` calls; verify hover / definition / completion all hit it.
• `src/core/lsp_manager.rs` — `lsp_status_for_language`.
• `src/core/engine/lsp_ops.rs` — `Engine::lsp_status_for_buffer` downgrade path.

Surfaced by

#223 Tooltip pilot smoke test (unrelated to the pilot itself).

[JDonaghy]

Implementation notes (2026-05-17, coordinator)

The status bar shows "rust-analyzer..." (initializing) indefinitely even after the server finishes indexing. The LspStatus should transition from Initializing(name) to Running(name) once the server responds.

Likely root cause: lsp_manager.rs has server_has_responded: HashMap<LspServerId, bool> and mark_server_responded() — check whether this is actually called on all response types, or only on some. The render side downgrades Running to Initializing when semantic_tokens is empty, so also check whether semantic tokens are being populated after the full index completes.

Files: src/core/lsp_manager.rs (status tracking), src/core/lsp.rs (response handling), possibly src/render.rs (status bar display logic — read only, check the downgrade condition).

Do NOT touch: src/gtk/, src/tui_main/.

[JDonaghy]

Fixed in 0b967c2 with a known trade-off: the indicator now briefly transitions to Initializing only between handshake completion and the first semantic-tokens response. For projects with a noticeable indexing phase (rust-analyzer on a fresh cargo project), the indicator goes bright before workspace indexing actually completes. Tracked properly in #450 — use $/progress notifications as the indexing-complete signal.