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.
7 lines
429 B
YAML
7 lines
429 B
YAML
# 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 docs/development.md
|
|
development.md: 4aab6772a514c5c461535f6e37906a503c10215a
|
|
development.zh.md: c420c0132d5d945457bad73ae71691d345488150
|