Troubleshooting page documents a fabricated audit.quality_filter.skip YAML block with nonexistent check names (CR-A01-016) #425

Wave 1 · theme D1-8: Docs describing features that do not exist (doc side of code findings) · highest severity High · 1 finding(s) · effort trivial

Summary

An operator pastes the documented block into their training YAML. forgelm --config X.yaml exits 1 with extra_forbidden, and no individual check can be disabled.

Primary finding

CR-A01-016 — Troubleshooting page documents a fabricated audit.quality_filter.skip YAML block with nonexistent check names

severity High · reachability default · intent contract-violation · confidence confirmed · independently confirmed · reproduced end to end · already tracked: KNOWN-OPEN C31-DOC-SCHEMA-PROSE — docs/roadmap/phase-16-trust-surface-hardening.md:785-786 (S15 open)

What happens. troubleshooting.md:110-116 tells operators to disable individual quality checks with audit.quality_filter.skip: [min_alpha_ratio, max_bullet_ratio]. ForgeConfig has no audit block (extra='forbid'), no per-check skip exists, and neither check name exists; the real names are low_alpha_ratio and the others. Applying the fix makes every run fail config validation.

Where.

• docs/usermanuals/en/operations/troubleshooting.md:106-116
• docs/usermanuals/tr/operations/troubleshooting.md:108-116
• forgelm/config.py:1604-1605
• forgelm/data_audit/_quality.py:22-28
• docs/usermanuals/en/data/quality-filter.md:36
• tools/check_usermanual_schema_drift.py:302-304

Evidence.

• The dry-run gives EXIT=1, 'audit Extra inputs are not permitted'. quality-filter.md:36 and :52 already say there is no audit: block and no per-check override.

Recommended fix. Replace the snippet with --no-quality-filter (the only supported control) and the real flag names, in EN and TR.

Acceptance criteria

• A regression test reproduces the failure scenario and asserts the corrected behaviour.
• 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.}