TR mirror drift in docs/usermanuals/en/reference/cli.md: jq -e '(.pii_severity.worst_tier // none) != high and (.cross_split_leakage_pairs | length) == 0' audit.json (DOC-TR10-006) #329

Wave 1 · theme D1-10: Documentation-only fixes · highest severity High · 1 finding(s) · effort docs fix

Summary

neither; cross_split_leakage_pairs lists compared split-pair names

Primary finding

DOC-TR10-006 — TR mirror drift in docs/usermanuals/en/reference/cli.md: jq -e '(.pii_severity.worst_tier // none) != high and (.cross_split_leakage_pairs | length) == 0' audit.json

severity High

Where. EN docs/usermanuals/en/reference/cli.md:356 · TR docs/usermanuals/tr/reference/cli.md:357

English text. jq -e '(.pii_severity.worst_tier // none) != high and (.cross_split_leakage_pairs | length) == 0' audit.json

Turkish text. aynı jq komutu

Which is correct. neither; cross_split_leakage_pairs lists compared split-pair names

Proposed correction (Turkish text for the -tr page). Sızıntı kontrolü için stdout zarfındaki cross_split_leakage_pairs kullanılamaz (karşılaştırılan split çiftlerinin ADLARINI taşır). Örnek: jq -e '(.pii_severity.worst_tier // "none") != "high"' audit.json ve sızıntı için diske yazılan data_audit_report.json içindeki cross_split_overlap.pairs.*.leak_rate_* / leaked_rows_in_* alanlarını eşikleyin.

Acceptance criteria

• Each statement is re-checked against the code at fix time.
• Documentation listed above is corrected in English and in its Turkish mirror in the same PR.
• Every finding in this issue is resolved or explicitly closed with a reason.

_{Found by the October 2026 ForgeLM code and documentation review against commit cab2947. Code links point at that commit; line numbers may have moved since. Finding IDs (CR-…, DOC-…, TECH-…) are stable references for this backlog.}