Repository navigation
Description
Wire wave 2 and wave 3 into the one server. Waves 2 and 3 each wrote a module with pure functions; none is reachable until the router lists it and the capability table announces it. This is the same job as the first wire issue (#12248) for the later modules. It touches specs/lsp/server.t27 only, so the Queen runs it after the wire wave 1 issue has merged and after the module issues it wires. Part of the LSP epic, Refs #12209 (wave 3, wiring). Only .t27: no code in any other language, not even scratch probes or a loader; see skill only-t27.
Depends on the wire wave 1 issue (#12248) merged, and on each wave 2 and wave 3 module it wires: specs/lsp/status.t27, views.t27, t27f_view.t27, edit_helpers.t27, check.t27, config.t27, lint.t27, inactive.t27, docs.t27, live_eval.t27, perf.t27, mcp.t27, hdl_hierarchy.t27, hw_hints.t27. Wire only the ones already merged; leave the others listed as pending in the capability table.
Prior art:
- rust-analyzer
main_loop.rsas one table of handlers: https://github.com/rust-lang/rust-analyzer - The honest-capabilities rule from the router issue (LSP: router and honest capabilities (specs/lsp/server.t27) #12217): a capability is announced only when its handler exists and its tests pass.
Boundary
- specs/lsp/server.t27
User Scenarios
- Given the status, views, edit-helper and check modules are merged, when a client initialises, then the server announces exactly the
t27/*methods of those modules and no others. - Given a module is listed
pending, when a client sends its method, then the answer isMethodNotFoundand the capability is absent frominitialize. - Given the configuration changes at runtime, when
workspace/didChangeConfigurationarrives, then the lint profile, the check command, the target andeval.enabledall update fromspecs/lsp/config.t27. - Given the user saves a file, when the save notification arrives, then the check-on-save run starts once, diagnostics from the check merge with live diagnostics by source, and the status shows the run.
- Given a module's test count falls below its stated minimum, when the wiring test runs, then it fails and names the module.
Requirements
- FR-001: The module MUST add each merged wave 2 and wave 3 module to the router table and to the capability table in one place, with a field
wired: yes | pending. - FR-002: The wiring test MUST enumerate the capability table and assert that every announced capability has a handler, and every handler has at least one request in the test.
- FR-003: The module MUST keep the client-facing extension methods under the
t27/prefix and MUST list them in the generated capability matrix (the conformance issue builds it). - FR-004: The module MUST NOT add a new provider flag defaulting to true; a flag is true only when
wiredisyes. - FR-005: A merge order MUST be recorded in the issue as a list of the module issues with their state at the time of the wiring.
Success Criteria
- At least 20 new tests in
specs/lsp/server.t27pass on top of the existing ones, run on the lab witht27c test-report(exit 0), including the pending-method refusal. - A negative control wires a module whose handler is missing and asserts the wiring test fails.
git diff --name-only masterlists onlyspecs/lsp/server.t27(0 files in other languages).
Activity
gHashTag commentedon Nov 17, 2026
Referenced spec exists: specs/lsp/server.t27.