Ziya
f5774a2a26
New docs must not enlarge the translation backlog: any date-named document (yyyy-mm-dd-*.md, i.e. an RFC) dated on/after the manifest's requiredSince cutoff must merge with its complete pair, independent of the required back-catalog list. Cutoff ships at 2026-07-05, so the existing 2026-07-04 RFC wave is grandfathered into the batch backlog and everything after is bilingual from birth. The date comes from the filename, deliberately: it is deterministic from tree content alone — no git history (shallow CI checkouts hold), no PR base ref — matching the gate's pure-content design. A proposal dated before the cutoff that merges later escapes the rule; that is the graceful grandfathering of in-flight work, not a hole. --list marks such files (required by date); contract and RFC updated in both languages and the pairs re-recorded.
18 lines
403 B
JSON
18 lines
403 B
JSON
{
|
|
"requiredSince": "2026-07-05",
|
|
"required": [
|
|
"README.md",
|
|
"docs/development.md",
|
|
"docs/i18n/README.md",
|
|
"docs/i18n/translation-rules.md",
|
|
"docs/rfc/implemented/process/2026-07-02-bilingual-docs-and-pairing-gate.md"
|
|
],
|
|
"excluded": [
|
|
"docs/AGENTS.md",
|
|
"docs/module-graph.md",
|
|
"docs/cordis-catalog/",
|
|
"docs/tool-catalog/",
|
|
"docs/i18n/terminology.md"
|
|
]
|
|
}
|