514ce7acc8
Operator is keeping the override rather than reverting: he has a replacement cable and will run it at the weekend. Recorded as a held position so a later session does not revert it as an oversight or re-run the diagnosis. Also corrects a claim this runbook made an hour earlier. I wrote that the zero-error 1G link ruled out a marginal cable. It did not — it only proved the cable was clean at 1G. The two-hour soak shows errors climbing monotonically at 10G (200 to 221 rx, ~1 per 23 MB) plus one self-recovering link drop, so the autoneg fallback had a real basis and the fix is the cable, not the config.