It did its job: it caught that the script did not parse under Windows
PowerShell 5.1, and confirmed identical behavior under pwsh on Linux, macOS and
Windows plus a clean #requires refusal on 5.1.
The fixes it drove stay -- #requires -Version 7.0, ASCII-only source, portable
path joins, culture-invariant parsing and the single-rename atomic swap. Only
the scaffolding goes, so the tools/ path does not carry a networked workflow
into main.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
cb2a33113a