[Copilot]

Venv CI jobs assumed the hosted runner exposed $Env:CONDA, causing setup to fail before tests when the variable was unset.

• Conda setup

  • Install Conda with a commit-pinned setup-miniconda action.
  • Preserve the matrix-selected Python by disabling environment activation.

• Path discovery

  • Resolve the first Conda executable on PATH.
  • Derive the base installation with conda info --base.
  • Record valid condaExecPath and condaPath values in envPaths.json.

• Diagnostics

  • Report explicit errors when Conda or its base Python cannot be found.

$condaCommand = Get-Command conda -CommandType Application |
    Select-Object -First 1
$condaBasePath = & $condaCommand.Source info --base

• Fixes CI venv jobs should not rely on the hosted runner's CONDA environment variable #26289

[Rich Chiodo (rchiodo)]

🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR.

[Rich Chiodo (rchiodo)]

Reviewed commit: 335f6516a5aa3935a129d1187a8247fc0fa618f5

Result: 🔴 could-not-verify

Verification details

Verification: Automated verification is best effort. The PR author remains responsible for testing.

Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: Podman machine 'pyrx-automation' is not running.

Test runs: none recorded.

[Rich Chiodo (rchiodo)]

Approved via Review Center.