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 loop-hygiene guard family: the advisory repeat-tool reminder and the per-tool-call timeout policy, for users and maintainers choosing or composing the guards. | package-group |
guard/ — loop-hygiene guard family
English | 中文
Summary
The guard/ group keeps the agent loop productive by watching for two common failure patterns. repeat-tool-reminder notices when the model repeats the exact same tool call and reminds it to change approach or finish, so a stuck loop stops burning time and tokens. timeout-policy puts a time limit on tool calls that declare one, so a hung call returns a clear timed-out error to the model instead of stalling the session. Both ship enabled in the dsh base bundle; a composition can tune or remove them.
Table of Contents
Packages
Two small plugins cover the two patterns; each README below explains when to keep, tune, or remove it.
| Package | What it provides |
|---|---|
repeat-tool-reminder/ |
Reminds the model when it repeats the same tool call, so it changes approach or finishes |
timeout-policy/ |
Times out tool calls that declare a limit, so the model gets a clear error instead of waiting forever |
Related documentation
Start with the tools subsystem reference for the tool-call pipeline, then the reminder's configuration and the timeout-library decision behind the policy.
- Tools subsystem reference — the tool-call pipeline and decisions both guards build on.
- Generated configuration catalog — every accepted field of the repeat-call reminder.
- Timeout deadline library Agent Note — the timing/termination split
timeout-policyenforces.
Dev Note
Working context for maintainers — click to expand
None.