Files
deepseek-harness/.agents/notes/implemented/architecture/2026-06-18-session-surface.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

38 lines
1.9 KiB
YAML

# Bilingual-pair consistency record for 2026-06-18-session-surface.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-18-session-surface.md
/agent-note-session-surface-an-ordered-projection-over-the-event-log:
en: 9ea7a8765e7f3259
zh: 17e0d51645f01edd
/agent-note-session-surface-an-ordered-projection-over-the-event-log/problem:
en: 4f7a9d20d71a6ab3
zh: 958abbdfefec4f21
/agent-note-session-surface-an-ordered-projection-over-the-event-log/decision:
en: a9944b568ec51fad
zh: 6717d30db31b81d7
/agent-note-session-surface-an-ordered-projection-over-the-event-log/decision/top-level-surface-metadata-on-sessionevent:
en: 788fc16ecdedc252
zh: 14d05c2a1272de5d
/agent-note-session-surface-an-ordered-projection-over-the-event-log/decision/surfaceop-two-operations:
en: ff075eec0881094a
zh: 1f7768f28b8996d5
/agent-note-session-surface-an-ordered-projection-over-the-event-log/decision/surfacemanager-delta-based-not-full-rebuild:
en: 0b10fd9c5166d17b
zh: 02de01f70c03f70e
/agent-note-session-surface-an-ordered-projection-over-the-event-log/decision/persistence:
en: 9bb1f81b86b24760
zh: fe4948645dd0c66d
/agent-note-session-surface-an-ordered-projection-over-the-event-log/decision/crash-recovery:
en: ee71f9c0f12b6a0e
zh: 403b1723f808391d
/agent-note-session-surface-an-ordered-projection-over-the-event-log/decision/invariants:
en: 24b1342fb3b5be29
zh: a62692b0250c072a
/agent-note-session-surface-an-ordered-projection-over-the-event-log/alternatives-considered:
en: 193157129e65e487
zh: a0a73b8a9cbd78e6
/agent-note-session-surface-an-ordered-projection-over-the-event-log/consequences:
en: 801b67f8da564a22
zh: 3c0433ed07083050