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:
@@ -43,4 +43,4 @@ Apply the ordered relocate-condense-raise policy in [docs/AGENTS.md](../../../do
|
||||
|
||||
## Validation and PR hygiene
|
||||
|
||||
Run at least `pnpm run doc-sync`, `pnpm run lint`, and `git diff --check`; JSDoc changes may regenerate catalogs. If a paired doc changed, follow [dsh-translate-docs](../dsh-translate-docs/SKILL.md) and run `pnpm run verify-translation-pairing --write`. The PR body should give word deltas, explain any deliberately long exception, and list checks.
|
||||
Run at least `pnpm run doc-sync`, `pnpm run lint`, and `git diff --check`; JSDoc changes may regenerate catalogs. If a paired doc changed, follow [dsh-translate-docs](../dsh-translate-docs/SKILL.md) and run `pnpm run verify-translation-pairing --write <pair>`. The PR body should give word deltas, explain any deliberately long exception, and list checks.
|
||||
|
||||
Reference in New Issue
Block a user