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 hooks group map: run existing Claude Code and Codex shell-hook configs during agent runs, for users and maintainers navigating the group. | package-group |
packages/hooks
English | 中文
Summary
The hooks group lets agent runs reuse shell hooks written for Claude Code or Codex. Point the matching integration at an existing hooks.json to run supported command hooks when sessions start, prompts arrive, tools run, or runs stop. These hooks can block prompts or tool calls with model-visible messages, add conversation context, or require the run to continue. Choose this group to preserve existing hook configurations; each integration supports only the command-hook subset documented by its source tool.
Table of Contents
Packages
| Package | Role | Shape |
|---|---|---|
hook-protocol |
Shared hook engine both bridges use; never configured directly | library |
hooks-claude-code |
Run your existing Claude Code hooks.json hooks during agent runs |
plugin |
hooks-codex |
Run your existing Codex hooks.json hooks during agent runs |
plugin |
Related documentation
- Interception extension-points Agent Note — the typed-Decision surface the bridges program against.
- Hook bridges Agent Note — the bridge design and its decision mapping.
- Hook protocol library Agent Note — what the shared library owns and why.
Dev Note
Working context for maintainers — click to expand
None.