docs(i18n): briefed update path in the workflow, contract, and Agent Note

The dsh-translate-docs skill now triages updates onto a briefing-driven
path — gen-translation-brief output as the translator's whole working
set, orchestrator-applied mechanical fence edits, scoped record/check —
while the whole-document path for new pairs is unchanged. The i18n
README documents the scoped gate forms and the briefing tool;
development.md lists the new command; the new bilingual Agent Note
records the decision and the ten-example benchmark behind it (briefed
path ~1/3 the tokens and wall clock of the corpus-loading path at equal
judged quality; whole-document re-translation rejected on preservation
collapse). Counterpart updates in this commit were produced with the
new briefed path; the new note's Chinese side is a whole-document
translation.
This commit is contained in:
Tianyi Cui
2026-07-27 00:44:22 +08:00
parent bf87be0d7d
commit 3841c4ee58
14 changed files with 154 additions and 50 deletions

View File

@@ -1,6 +1,6 @@
# Bilingual-pair consistency record (docs/i18n/README.md): the git blob hash of each
# side as of the last confirmed-consistent state. Both languages carry equal authority;
# after editing either side, bring the other along and re-record with:
# pnpm run verify-translation-pairing --write
development.md: c46d84740e6f0a1f67158f39f9ea421cb57165d4
development.zh.md: 9e13ab258e1db5406f84ece61959a995110578ae
# pnpm run verify-translation-pairing --write docs/development.md
development.md: 4aab6772a514c5c461535f6e37906a503c10215a
development.zh.md: c420c0132d5d945457bad73ae71691d345488150