Files
deepseek-harness/packages/typert
imccyu 2b750cfb51 docs(api): document the converged ctx.remote programming surface
- new cookbook page adding-a-remote-api (en/zh): the five-step HOW-TO
  for declaring, failing, registering, consuming, and testing a Remote
  endpoint.
- new Agent Note ctx-remote-failure-vocabulary records this round's
  decisions and alternatives; the 2026-08-02 and 2026-08-10 notes are
  rewritten to the shipped facts (RemoteError vocabulary, $host, the
  retired ApiProxy statements).
- package READMEs pick up the new failure-face contracts
  (typert/protocol, api/gateway, api/remotes,
  test-support/client-runtime), dsh-util-time gains its README and
  registry entries, and stale connection/WorkspaceError/legacy-code
  statements are corrected (ui-settings, ui-settings-models,
  workspace-controller, docs/subsystems/typert incl. the
  TypertGatewayErrorCode type-equiv block).
- packages/AGENTS.md gains the Remote-failure rule bullet; its doc
  budget rises 675 -> 714: the bullet is the compressed remainder
  after relocating detail to the cookbook and the Agent Note.
2026-08-28 22:37:36 +08:00
..
2026-08-28 00:50:12 +08:00
2026-08-28 00:50:12 +08:00
2026-08-28 00:50:12 +08:00

description, kind
description kind
The typert group map: the build-time type-graph generator, runtime registry, Loader integration, and shared Remote protocol that enable typed Host-to-Client calls. package-group

packages/typert

English | 中文

Summary

With the typert group, Client environments can call Host capabilities as typed methods and share generated schemas and reflection without hand-written wire code. A build-time generator turns source type declarations into compiler-independent models and runtime artifacts, a runtime registry stores those artifacts, and a Loader integration registers them automatically in Loader compositions. A shared protocol package supplies the Remote-call declarations — decorators, wire descriptors, codecs, and provider contracts — that business packages, generated artifacts, the Host Gateway, and the Client API all consume. This page maps the four packages; each package README owns its configuration, usage, and limits.

Table of Contents


Packages

Package Role ctx key
generator/ Analyzes source types at build time and generates the reflection, schemas, and Remote descriptors that runtimes load
loader/ Auto-registers generated Typert artifacts from Loader compositions into the runtime registry consumes ctx.loader and ctx.typert
protocol/ Declares the Remote decorators, wire descriptors, codecs, and provider contracts shared by Host and Client
registry/ Stores generated package reflection and live Zod schemas at runtime, plus lookup and Context provider registries ctx.typert


Dev Note

Working context for maintainers — click to expand

None.