thePR0M3TH3ANandClaude Opus 5 01960e9234 Choose the install interpreter by capability, like the test script does ...

Adding `shell: bash` to the install step in the previous commit was right for
error propagation and wrong about which python it would get: under bash on
Windows a bare `python` resolves to MSYS2's, which has no pip, so the step
died with "No module named pip" where it had previously worked under pwsh.

Same shape as the test-runner fix, so the same answer: try candidates and
keep the first that can actually run pip, including the pythonLocation that
setup-python exports without putting first on PATH, and fail loudly naming
what was tried. It also echoes the interpreter it picked, so the next
surprise of this kind is a line of log rather than a deduction.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01Vtx94nXDmNgXEeThUZP4QN

2026-08-20 10:45:34 -04:00

..

workflows

Choose the install interpreter by capability, like the test script does

2026-08-20 10:45:34 -04:00

CODEOWNERS

Add repo memory layer and agent governance

2026-08-12 20:57:56 -04:00

dependabot.yml

chore: add dependency auditing

2025-08-03 08:32:57 -04:00