Dustin ae6b6b1b72 ci(windows): make taskkill no-op when server.py already exited ...

The path-discovery step succeeds on the first run, but the cleanup
step exits non-zero because `taskkill /PID 5560 /T /F` returns 128
("process not found") when server.py has already exited on the mock
hermes_cli stub. That's the expected steady state for this mock-only
workflow, not a failure.

Two-line fix: reset `$global:LASTEXITCODE = 0` after the taskkill
call, and explicit `exit 0` at the end of the step so any other
external-command exit codes don't bubble up. The try/catch wrapper
didn't help because taskkill writes its diagnostic to stderr without
raising a PowerShell exception — `catch` never fired.

Run 26352805510 on this branch shows the failure shape: "OK: start.ps1
path discovery - all guards passed." in the verify step, then
"ERROR: The process '5560' not found." in the cleanup step. Path
discovery is what this workflow exists to validate; cleanup just has
to not fail the job.

2026-05-24 17:10:02 +00:00

..

docker-smoke.yml

harden(docker-smoke): catch !!ERROR/!!Exiting + tighten egg_info test

2026-05-17 17:34:46 -07:00

native-windows-startup.yml

ci(windows): make taskkill no-op when server.py already exited

2026-05-24 17:10:02 +00:00

release.yml

fix: dynamic version badge — read from git tag, never hardcoded (#790)

2026-04-20 20:36:53 -07:00

tests.yml

test: tighten CI and console hygiene

2026-05-11 23:13:16 +00:00