docs/usermanuals/en/operations/troubleshooting.md: false claim — forgelm audit 'refuses to certify a leaky split' when cross_split_overlap > 0. (DOC-D3B04B-009) #227

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

Summary

Teams that assume audit blocks leaky splits in CI ship train/test contamination with exit 0.

Primary finding

DOC-D3B04B-009 — docs/usermanuals/en/operations/troubleshooting.md: false claim — forgelm audit 'refuses to certify a leaky split' when cross_split_overlap > 0.

severity High

Where. docs/usermanuals/en/operations/troubleshooting.md:100-104 (Turkish mirror: docs/usermanuals/tr/operations/troubleshooting.md:100-104) · type: false claim

The document says. forgelm audit 'refuses to certify a leaky split' when cross_split_overlap > 0.

What the code does. Cross-split leakage is reported, under cross_split_overlap.pairs, but never gates. audit exits 3 only for critical secrets or critical-tier PII (forgelm audit --help; forgelm/cli/subcommands/_audit.py:10-13, 94-97, 151-154). No 'certify' message exists.

Code references. forgelm/cli/subcommands/_audit.py:10-13, forgelm/cli/subcommands/_audit.py:299, forgelm/data_audit/_types.py:138

User impact. Teams that assume audit blocks leaky splits in CI ship train/test contamination with exit 0.

Proposed correction. Retitle to 'Audit reports cross-split leakage'. Cause: train rows also appear in validation/test (cross_split_overlap.pairs in data_audit_report.json). Note: leakage is reported but does not change the exit code — gate on it in CI by reading the JSON (--output-format json).

Turkish mirror. the Turkish page has the same error; fix both in the same PR

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.}