fix(docs): bring German/Traditional Chinese READMEs back in sync with English - #206
Merged
Conversation
…ync with English Three real gaps found by comparing all three READMEs section by section, none caught by check-doc-claims.mjs since it checks facts, not translation parity: - Both translations were missing the entire "Recipes" section (three worked examples) that exists in README.md — added, translated to match each file's established terminology and register. - Both translations had reduced the "Conflict Detection" Smart Feature to one generic sentence, while English carries three sentences of real detail (the command, the review workflow, the causality guarantee) — expanded to match. - README.zh-TW.md's Contributing section hardcoded "630 項測試" next to `npm test`, the exact stale-count problem check-doc-claims.mjs's test-count guard exists to prevent — just phrased in Chinese, so the English-only regex never saw it. Removed, and the regex now also matches the CJK phrasing.
This was referenced Aug 24, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Requested review of "the READMEs" turned up real drift between README.md and its two translations, found by reading all three side by side (check-doc-claims.mjs checks facts against code, not translation parity against the English source — this class of gap is outside what it looks for):
dream list/dream show, nothing auto-applies), and the causality guarantee. Expanded both to match.npm test # 630 項測試— the exact "stale test count next to npm test" problemcheck-doc-claims.mjs's own check feat: v2.12.0 — Knowledge Evolution (soft-archive, supersedes, observation-level forget) #5 exists to prevent (its comment cites an earlier incident: "all eleven said 630 tests while the suite had grown past 1400"). It slipped through because that check's regex only matches the English words "tests"/"test cases" — "630 項測試" is the same claim in Chinese. Removed the stale count and widened the regex to also catch the CJK phrasing, so this doesn't silently recur.Test plan
node scripts/check-doc-claims.mjs— all 32 checks pass, including the now-widened "READMEs state no hardcoded test count" check