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 storage group map: durable non-session data through named backends and the typed domain data form, for users and maintainers navigating the group. | package-group |
packages/storage
English | 中文
Summary
The storage group keeps non-session application data across restarts, including workspace records and session sidecars. Choose storage-json for human-readable files or storage-sqlite for point updates in one database; storage-domain adds schema-validated typed records and change notifications, while storage selects the configured backend. These packages are optional and host-side: they do not expose tools, prompt content, or session events to the model. Use the group when application state must outlive a process, and omit it when the composition has no such data.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
storage |
Connects registered backends with mounted data-form facilities | ctx.storage |
storage-json |
Stores each unit as one human-readable JSON file | registers backend json |
storage-sqlite |
Stores units as JSON documents in one SQLite database | registers backend sqlite |
storage-domain |
Provides schema-validated, change-emitting KV domains over routed backends | ctx.storageDomain |
Related documentation
- Storage subsystem — the authoritative contract: the backend contract, domain declaration, change events, and generated API.
- domain KV storage Agent Note — the design behind the family, the workspace consumer, and the deferred session-backend migration.
- Workspace subsystem — the first consumer of the domain data form.
Dev Note
Working context for maintainers — click to expand
The design Agent Note is still marked proposed while the family ships; its out-of-scope table is the deferred-work list for the migration phase (the log facet, session-backend reuse, cross-process change push). Promote decisions into implemented notes as they land.