Tianyi Cui
a7a5be1703
Run the dsh-archive-agent-notes audit over every active Agent Note on current master, judging each record by whether its rationale still guides work rather than by size or age. - Archive 453 implemented bilingual triplets (417,882 English words): completed UI chrome, narrow adapters, closed bug fixes, implementation walkthroughs whose package READMEs, docs pages, generators, or successor notes now carry the useful behavior, and 51 records fully superseded by a later active note. Keep 201 implemented notes whose ownership rules, negative guarantees, durable or wire semantics, security rules, reintroduction conditions, or still-tempting rejected alternatives remain useful. - Reject 7 proposals whose premise is gone or whose work shipped in amended form under other records; delete 2 rejected notes that no longer prevent a plausible mistake. - Retarget every remaining inbound link to the archived path, and repair active prose that named an archived record as the owner of a live fact: parenthetical citations drop, ownership sentences redirect to the README, docs page, or active note that states the fact, and history citations say so. Chinese files link the English archived path because the pairing gate treats the frozen tree as outside the bilingual corpus. - Seal 1,359 new frozen artifacts; existing seals are unchanged and outbound links from archived notes are neither inspected nor repaired. - Regenerate docs/config-catalog.md after the hook-bridge comment edits shifted two source line numbers.
description, kind
| description | kind |
|---|---|
| The lsp group map: language-server code navigation through the LSP seam, its stdio provider, and the model-facing lsp tool, for users and maintainers navigating the group. | package-group |
lsp/ — Language-server code navigation
English | 中文
Summary
The lsp group gives agents precise, language-server-backed code navigation: go to a symbol's definition, find its references, jump to its implementations, or read hover documentation, without the model ever knowing which server answers. The capability is split across three product packages: the dsh-lsp seam (ctx.lsp) that selects a provider by file extension and normalizes results, the dsh-lsp-stdio provider that drives configured local language-server commands, and the model-facing dsh-tool-lsp tool that owns the lsp schema, prompt, and presentation. Only the provider and the tool do anything when loaded; deployments configure server commands and extension mappings explicitly, and the group ships no language server of its own.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
lsp/ |
Defines the code-navigation service: provider selection by file extension, four normalized read-only operations, and structured errors | ctx.lsp |
lsp-stdio/ |
Drives configured stdio language-server commands as providers over ctx.fs and ctx.subprocess |
registers on ctx.lsp |
tool-lsp/ |
Exposes precise code navigation to the model through the lsp tool |
registers on ctx.tools |
Providers register capabilities, not tools: tool-lsp is the only owner of the model-facing name, schema, prompt guidance, and presentation, so swapping a provider never changes how the model asks for navigation.
Related documentation
- LSP navigation subsystem — operations, coordinates, requests and results, and
LspErrorcodes. - Generated tool catalog — the
lspschema the model receives.
Dev Note
Working context for maintainers — click to expand
None.