Files
deepseek-harness/.agents/notes/implemented/architecture/2026-06-21-bounded-llm-request-recovery.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

44 lines
2.2 KiB
YAML

# Bilingual-pair consistency record for 2026-06-21-bounded-llm-request-recovery.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-06-21-bounded-llm-request-recovery.md
/agent-note-bounded-recovery-for-transient-llm-request-failures:
en: fb8e336ecd4bf571
zh: 23e40e4cb224163f
/agent-note-bounded-recovery-for-transient-llm-request-failures/problem:
en: 83a361538a092dae
zh: e8f33cb95d0d3e09
/agent-note-bounded-recovery-for-transient-llm-request-failures/decision:
en: a15c7c13f167e5ac
zh: 63bcc2ef60c2f344
/agent-note-bounded-recovery-for-transient-llm-request-failures/decision/preserve-failure-facts-without-embedding-policy:
en: 943322e6cdbfa440
zh: 82288531f6194ed2
/agent-note-bounded-recovery-for-transient-llm-request-failures/decision/put-retry-policy-on-the-existing-failed-step-extension-point:
en: ed4d295378d94a26
zh: 1fee5ef4947bac8f
/agent-note-bounded-recovery-for-transient-llm-request-failures/decision/make-one-layer-own-visible-attempts:
en: 57dbdd385f48bb3e
zh: 5e15463fae4be582
/agent-note-bounded-recovery-for-transient-llm-request-failures/decision/bound-stalled-streams-where-they-can-be-stopped:
en: f7369086e87192b9
zh: e2839ed8cc5c23b8
/agent-note-bounded-recovery-for-transient-llm-request-failures/decision/keep-attempts-separate-in-the-existing-log:
en: 8f57db4bfd6e1c22
zh: 67ac62217bb68570
/agent-note-bounded-recovery-for-transient-llm-request-failures/out-of-scope:
en: 985720529b56cda2
zh: 8a649bfa9cd8d93f
/agent-note-bounded-recovery-for-transient-llm-request-failures/alternatives-considered:
en: a6d0306740d470ee
zh: 700bd4b0aa58f3e8
/agent-note-bounded-recovery-for-transient-llm-request-failures/verification:
en: db343f335a9d7cad
zh: 49b8300de55dcfeb
/agent-note-bounded-recovery-for-transient-llm-request-failures/consequences:
en: 08659e8606455ada
zh: 862080f8df5f28ec
/agent-note-bounded-recovery-for-transient-llm-request-failures/related:
en: e85a6ad7387c881b
zh: bb8fb4173ffe613d