[finding] plugins/uberdev/docs/testing.md — The prescribed refutation procedure claims the dump step wil #776

Origin: 2c6db44177351a84156c12e838aceecd76f8713b
Agent: premerge.review.code_review
File: plugins/uberdev/docs/testing.md:100
Severity: suggestion (Phase premerge)
Disposition: DEFERRED (premerge-repair-budget-exhausted)
Tier: SUGGESTION
Related: PR #768

Findings (1)

1. plugins/uberdev/docs/testing.md:100 — suggestion / SUGGESTION / DEFERRED (premerge-repair-budget-exhausted) — The prescribed refutation procedure claims the dump step will settle whether interpreter-level newline translation is th

Lenses: premerge.review.code_review

ci-shard-plan.py now reconfigures stdout to LF and ci-shard-env.sh exits 2 on any CR-bearing pack. Section [A] of the dump re-runs that same pinned producer, so it can only ever print an LF plan or 'the producer refused' - and if it refused, the planning step already failed the job and the dump step never runs. An operator following the instruction and finding [A] clean will record that as confirmation of a claim the setup made unobservable.

To resolve: address the findings above in code and close this issue. Closing resolves exactly the findings listed in this body and the findings added by a later comment on it — one index records both, and closing resolves that recorded set and nothing else. A finding in this file that this issue never recorded is filed as a NEW issue rather than suppressed, so closing never mutes the file. Before closing, apply finding:true-positive if it was a real defect or finding:false-positive if it was not — that label is the eval ground truth (RFC 0018).