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 |
|---|---|
| Package map for the SDK family: JSON-RPC protocol plus the TypeScript client and server used by out-of-process SDKs. | package-group |
sdk/ — drive a Harness runtime from another process
English | 中文
Summary
The SDK family lets another process drive a complete DeepSeek Harness runtime over newline-delimited JSON-RPC. Its protocol package defines the public messages, the TypeScript client launches dsh with a named profile and ordered patches, and the server accepts SDK requests over stdio. Clients can open sessions, send prompts, and observe session events, agent status changes, and subagent completions. The TypeScript client and Python SDK use the same protocol, and these packages do not create developer projects or define another application.
Table of Contents
Packages
Each package README describes what you can do with its part of the stack.
| Package | Role |
|---|---|
protocol/ |
Wire protocol: the newline-delimited JSON-RPC transport and the named request, result, and notification types |
client/ |
TypeScript client that spawns a runtime subprocess and drives agent turns through the high-level and protocol-level APIs |
server/ |
jsonrpc plugin that serves out-of-process SDK clients over stdio |
Related documentation
Start with the Python SDK (the sibling implementation of the client contract), then the runnable application and the decision records behind the group's boundary.
- Python SDK — the Python counterpart that speaks the same protocol and ships a bundled runtime.
- SDK application bundle — the
dsh --profile sdkapplication that boots the JSON-RPC server. - Architecture — why the packaged Python client launches the same named profiles.
- SDK project toolchain removal — why this group never creates, configures, or builds developer projects.
- SDK subagent provider — a harness-internal consumer of the TypeScript client.
Dev Note
None.