Turtle
e7def469e1
* feat(i18n): key translation pairing records by heading section Replace the whole-file blob hashes in *.i18n.yaml with one entry per heading section that still holds language-specific content, keyed by the English heading-slug path. Blocks identical across the pair (generated table rows, code blocks, shared regions) stay out of the hash, so edits to different sections and identical regenerations merge with Git's default text merge, including on GitHub. Remove the dsh-translation-pairing merge driver, its resolver command and installer wiring; gen-translation-brief recovers last-confirmed text from commit history. Migrate all active records, archive the superseded Agent Note, and record the replayed conflict reduction in the new one. * test(i18n): refresh translation prompt snapshot for the terminology note * feat(i18n): exclude only code blocks and generated regions from pairing records Replace byte-equality masking with an explicit rule: a record hash skips fenced code blocks and BEGIN/END GENERATED regions, the two kinds of content the pairing gate already requires to be identical on both sides. Move generated data into regions written into both pages: gen-config-catalog renders both languages and the record with per-package regions labelled by code identifiers; gen-module-graph keeps its table in a region; gen-doc-graphs splices the event matrix regions into the Chinese page. Add a generic region splice beside the region grammar.
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 lets agents navigate code through configured language servers: go to definitions, find references and implementations, and read hover documentation. Use lsp-stdio to connect local stdio language-server commands and extension mappings, and tool-lsp to make those operations available to the model. The shared lsp package keeps provider choice and normalized results consistent, so changing servers does not change model requests. Deployments must supply and configure their language servers; this group ships none.
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.