deepseek-harness/docs/development.i18n.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: fd7f39ae7b5aac2d44572979ca8c8f1d2df0de6f
development.zh.md: 7dd6209bad75d605e0056d2465a35b08aa091780
docs: equal-authority pairing with sidecar consistency records Redesign per review: neither language is canonical. A pair is three sibling files — foo.md, foo.zh.md, foo.i18n.yaml — and either language may be authored first (a Chinese-first RFC is as legitimate as an English-first one). The sidecar record holds the FULL git blob hash of both sides as of the last confirmed-consistent state, replacing the in-file one-directional fingerprint; editing either side without re-confirming the pair goes red. New --write mode re-records a pair after both sides are brought in line, making the confirmation a reviewable yaml diff. Pairs merge whole (completeness enforced). - gate rewritten around pair anchors (union of .zh.md and .i18n.yaml remnants) so half-deleted pairs are caught from either side; red/green proven for en-only edit, zh-only edit, missing record, and a record for an excluded file - verify-rfc-classification now skips .zh.md counterparts (same RFC, indexed via its English filename; the pairing gate owns consistency) - docs/i18n/README.md + translation-rules.md reframed bidirectionally (terminology table binds both directions; typography section governs the Chinese side); zh counterparts updated; skill workflow updated - RFC amended to the shipped design, records the English-canonical in-file-fingerprint model as considered-and-revised; RFC translated (docs/rfc/.../2026-07-02-bilingual-docs-and-pairing-gate.zh.md) and added to the required frontier - generated docs stay excluded with the follow-up recorded: teach the generators to emit Chinese, then de-list 2026-07-03 07:41:24 -07:00			`# 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:`
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. 2026-07-27 00:44:22 +08:00			`# pnpm run verify-translation-pairing --write docs/development.md`
feat(i18n): unit-mapped briefings with mechanical --apply, adopting the #684 planner mechanics The briefing now maps each update at the narrowest safely aligned granularity, widening deterministically on mapping failure: a change confined to the pair's byte-identical code fences is computed outright (--apply splices it into the counterpart and validates the result against the pairing gate's structural signature before writing); otherwise changed Markdown units — headings, paragraphs, table rows, list items, fences, block quotes, HTML blocks, thematic breaks, link definitions, matched by container-scoped kind sequences — each carry their last-confirmed source, current source, and current counterpart text; units that do not align fall back to depth-matched heading sections (depth only, so translated heading text still maps); and when sections do not align either, or both sides drifted, the briefing says so and withholds the mapping. Terminology rows now match the changed spans only, English terms on word boundaries with plural inflections, and Chinese-target briefings track each relevant term's document-wide first occurrence — a moved occurrence pulls the vacated and receiving spans into the briefing with an explanatory note. The unit mapping, mechanical code splice, and first-occurrence tracking adopt the planner design from the incremental prompt-pipeline PR (#684), whose provider-backed bake-off independently validated the same scope ladder; this PR carries those mechanics into the agent-facing briefing path so both consumers of the consistency records behave alike. The prior line-hunk section mapping and its heading-text alignment (which could not map cross-language sections) are replaced wholesale. Docs: SKILL.md update path, i18n README pair, development.md pair, and the briefed-updates Agent Note pair brought along; the development.md fence edit was applied with --apply itself, and the prose updates were made through the new unit/section briefings. 2026-07-27 02:31:07 +08:00			`development.md: fd7f39ae7b5aac2d44572979ca8c8f1d2df0de6f`
			`development.zh.md: 7dd6209bad75d605e0056d2465a35b08aa091780`