Files
deepseek-harness/.agents/notes/implemented/architecture/2026-08-10-remote-event-delivery.i18n.yaml
T
Turtle e7def469e1 feat(i18n): key translation pairing records by heading section (#5036)
* 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.
2026-09-23 22:32:06 +08:00

41 lines
1.8 KiB
YAML

# Bilingual-pair consistency record for 2026-08-10-remote-event-delivery.md (docs/i18n/README.md): per heading
# section, a hash of its English and Chinese blocks outside code blocks and generated regions.
# After editing either side, bring the other along and re-record with:
# pnpm run verify-translation-pairing --write .agents/notes/implemented/architecture/2026-08-10-remote-event-delivery.md
/agent-note-remote-event-delivery-ctx-remote-on:
en: 4b64b9fab76b5185
zh: 57a11b8a480a49dd
/agent-note-remote-event-delivery-ctx-remote-on/problem:
en: d3016e40cefe047f
zh: 83e83c25a13383e5
/agent-note-remote-event-delivery-ctx-remote-on/decision:
en: 83f6f48ce1fc517b
zh: abcfcd1c0eb777ea
/agent-note-remote-event-delivery-ctx-remote-on/decision/consumer-contract-dsh-typert-protocol:
en: 8f30b121dd59a3a3
zh: 92a5e0e63936c393
/agent-note-remote-event-delivery-ctx-remote-on/decision/the-allowlist-one-declaration-read-by-both-faces:
en: ce8c2e030baf7049
zh: bb6beb40228e40ae
/agent-note-remote-event-delivery-ctx-remote-on/decision/wire-protocol-api-gateway-remote-mux:
en: 5c89d238a469e79f
zh: d0cf485f0d245e7d
/agent-note-remote-event-delivery-ctx-remote-on/decision/the-apps-web-browser-e2e-belongs-to-the-host-face:
en: a29e07b8013f7f9f
zh: 4f066efa96f2d22f
/agent-note-remote-event-delivery-ctx-remote-on/decision/change-inventory:
en: 49fc44d242a87b69
zh: 42c4c36296849a88
/agent-note-remote-event-delivery-ctx-remote-on/alternatives-considered:
en: b75743ab277c1557
zh: e8e05f41ce1bc2f3
/agent-note-remote-event-delivery-ctx-remote-on/verification:
en: 4ec0e1c76da8d3b6
zh: 23de66f8fc659c15
/agent-note-remote-event-delivery-ctx-remote-on/consequences:
en: c50a0968e3f65df7
zh: 786f33cf1e95dae4
/agent-note-remote-event-delivery-ctx-remote-on/related:
en: b64e771dafa6c05b
zh: 4c2f47884f5a2d19