Pine/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases 1 Wiki Activity

Merge remote-tracking branch 'upstream/master' into docs/i18n-translation-prompt

Browse Source 
# Conflicts:
#	README.i18n.yaml
#	README.zh.md
#	docs/development.i18n.yaml
#	docs/development.zh.md
#	docs/rfc/implemented/process/2026-07-02-bilingual-docs-and-pairing-gate.i18n.yaml
#	docs/rfc/implemented/process/2026-07-02-bilingual-docs-and-pairing-gate.zh.md
#	scripts/translation-pairing.manifest.json
This commit is contained in:
Ziya
2026-07-12 21:08:45 -07:00
parent ba4e39f10d 4cda9dd03d
commit 04b61f2362
873 changed files with 63362 additions and 12439 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/rfc/implemented/process/2026-07-02-bilingual-docs-and-pairing-gate.md
+4 -2
View File
@@ -1,8 +1,10 @@
# Bilingual documentation via paired sibling files and a pairing gate
# RFC: Bilingual documentation via paired sibling files and a pairing gate
Status: implemented
English | [中文](2026-07-02-bilingual-docs-and-pairing-gate.zh.md)
## Context
## Problem
This repo's README and docs tree are read by people and agents inside and outside the company, in both English and Chinese. Maintaining a second language by hand, with no mechanism, is how translations rot: one side moves on, the other silently lies, and no gate notices. The repo's standing answer to invariants of this kind is to encode them as a mechanical check (see [quality gates](2026-06-11-quality-gates.md) and [doc-sync enforcement](2026-06-11-doc-sync-enforcement.md)), so the bilingual policy ships with one.