The PEP 668 step failed on both legs against a fix that was working. `Get-Command python`
resolves through PATH, and the "Install uv" step earlier in this job puts .uvtools\Scripts
on it — a venv Scripts directory, which holds a python.exe. So the "base" being asked was
that venv, which is correctly not externally managed, and the assertion fired exactly as
designed.
Both interpreters are now named rather than looked up: the marker is planted relative to
$env:pythonLocation's python and the same one is asked about, and .pep668 is created from
it so it is a venv rather than a venv of a venv. The step also ends with an explicit
exit 0, since the runner appends `exit $LASTEXITCODE` to every pwsh step.
The pip upkeep step passed on both legs: pip 22.1.2 -> 26.2.1 on 3.10 where the old pip
runs, and on 3.14 where it cannot and only the ensurepip fallback gets out of it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>