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 human-collaboration capability family: slash commands, one-shot approvals, permission presets, and the question/answer seam that lets a running agent pause for a human decision. | package-group |
interaction/ — the human-collaboration plane
English | 中文
Summary
The interaction/ group covers the ways a person can guide a running agent. Use slash commands for immediate actions that do not require a model round trip, one-shot approvals for sensitive operations, permission presets to choose sandbox and approval behavior together, and questions when the agent needs information or a decision. Interactive applications expose these capabilities to people; automation handles its own approvals through ACP. The package map below distinguishes each capability and links to its full behavior and configuration.
Table of Contents
Packages
Each package README and its subsystem reference own the exhaustive contracts.
| Package | Role | ctx key |
|---|---|---|
commands/ |
Lets users type slash commands that run directly against an agent without a model round trip | ctx.commands |
user-approval/ |
Asks composed answerers for one-shot allow/reject decisions and fails closed without one | ctx.approval |
permission-presets/ |
Bundles sandbox mode with an approval policy into one user-facing Permissions selector | ctx.permissionPresets |
user-questions/ |
Defines the validated question schema and scoped answerer waterfall an agent pauses on | ctx.userQuestions |
tool-ask-user/ |
Exposes the ask_user_question tool so the model can ask the human for a decision |
registers on ctx.tools |
Related documentation
Start with the subsystem references for the shared vocabularies, then the neighboring automation and composition surfaces.
- Commands subsystem — command registry semantics and the
ctx.commandsCordis surface. - Approval subsystem — request/outcome vocabulary, the answerer waterfall, and per-session policy.
- Permission presets subsystem — the preset table and the knob write-through.
- User interaction subsystem — question vocabulary, answerer waterfall, and presentation intent.
- ACP group — the automation-only transport that answers approval requests for its own agents.
Dev Note
Working context for maintainers — click to expand
None.