Poll for VIPM CLI readiness instead of trusting the installer's exit

Same install command, same env vars, two different outcomes across the last
two CI runs: one got past the Settings.ini load and hit the (now-fixed) git
error, the next regressed straight back to "Failed to load Settings.ini" -
with no code change to explain the difference. That's consistent with the
VIPM installer's main process exiting (satisfying Start-Process -Wait) before
a detached background step finishes writing the default Settings.ini, i.e. a
race, not a logic bug.

Replaces "trust the installer returned, then locate vipm.exe" with an actual
readiness check: after locating vipm.exe, poll `vipm --version` for up to 30s
(15 attempts, 2s apart) before running any real command against it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: stagg54

scripts/windows/run-caraya-tests.ps1

@@ -71,6 +71,24 @@ function Find-Tool {
 Install-Vipm
 $vipm = Find-Tool -Name "vipm.exe"
 
+# The installer's own process can exit (satisfying Start-Process -Wait) before VIPM has finished
+# writing its default Settings.ini in the background - seen directly in CI (against the LUnit job,
+# same image): the very same install sequence loaded Settings.ini fine on one run and failed with
+# "file not found" on another. Poll with a harmless command instead of assuming ready-to-use the
+# instant the installer returns.
+Write-Host "=== Waiting for VIPM CLI to become ready ==="
+$ready = $false
+for ($i = 1; $i -le 15; $i++) {
+    & $vipm --version 2>&1 | Out-Null
+    if ($LASTEXITCODE -eq 0) { $ready = $true; break }
+    Write-Host "vipm not ready yet (attempt $i/15, exit $LASTEXITCODE) - waiting 2s"
+    Start-Sleep -Seconds 2
+}
+if (-not $ready) {
+    throw "vipm.exe never became ready after installing (still failing after 15 attempts)"
+}
+Write-Host "vipm is ready: $(& $vipm --version)"
+
 function Invoke-Vipm {
     param([string[]]$VipmArgs)
     Write-Host "vipm $($VipmArgs -join ' ')"

scripts/windows/run-lunit-tests.ps1

@@ -65,6 +65,23 @@ function Find-Tool {
 Install-Vipm
 $vipm = Find-Tool -Name "vipm.exe"
 
+# The installer's own process can exit (satisfying Start-Process -Wait) before VIPM has finished
+# writing its default Settings.ini in the background - seen directly in CI: the very same install
+# sequence loaded Settings.ini fine on one run and failed with "file not found" on another. Poll
+# with a harmless command instead of assuming ready-to-use the instant the installer returns.
+Write-Host "=== Waiting for VIPM CLI to become ready ==="
+$ready = $false
+for ($i = 1; $i -le 15; $i++) {
+    & $vipm --version 2>&1 | Out-Null
+    if ($LASTEXITCODE -eq 0) { $ready = $true; break }
+    Write-Host "vipm not ready yet (attempt $i/15, exit $LASTEXITCODE) - waiting 2s"
+    Start-Sleep -Seconds 2
+}
+if (-not $ready) {
+    throw "vipm.exe never became ready after installing (still failing after 15 attempts)"
+}
+Write-Host "vipm is ready: $(& $vipm --version)"
+
 function Invoke-Vipm {
     param([string[]]$VipmArgs)
     Write-Host "vipm $($VipmArgs -join ' ')"