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 durable image attachment capability family: what you can do with image attachments, and where your images are stored. | package-group |
attachment/ — durable attachment capability family
English | 中文
Summary
The attachment/ group provides durable image attachments: attach images to prompts and commands, and the harness saves them on your machine, shows them again in conversation history, and sends them to the model in later turns. The shipped dsh composition enables this with no setup. The capability and its storage are split across two packages, described below. Stored images survive restarts and are never deleted automatically, and only raster image formats are supported.
Table of Contents
Packages
These two packages provide durable image attachments; each README describes what you can do with its part.
| Package | Role | ctx key |
|---|---|---|
attachment/ |
Image attachments for prompts and commands that persist and come back in history | ctx.attachments |
attachment-local/ |
Stores your attached images on this machine below DSH_HOME |
registers on ctx.attachments |
Related documentation
Start with the subsystem reference for the service contract, then the capability-seam table and the configuration surface of the local backend.
- Attachment subsystem reference — service contract, payload types, and the
ctx.attachmentsCordis surface. - Capability seams — the Service Definition / Service Provider / Consumer split this family follows.
- Generated configuration catalog — every accepted field of the local backend.
Dev Note
Working context for maintainers — click to expand
None.