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 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 |
Related documentation
- Typert subsystem reference — the literal public contracts recorded from protocol and registry types.
- API Gateway reference — how the generated Remote descriptors become running Host-to-Client calls.
- Remote-call Agent Note — the architecture and transport decisions behind Remote calls.
- Package workspace map — every group in the workspace and what each owns.
Dev Note
Working context for maintainers — click to expand
None.