Priyanshu Choudhary f825dff6c7 fix(runtime-process): preserve EPERM in Windows pty-host sweep exit-poll ... The catch in sweepWindowsPtyHosts treated every error as "process exited", including EPERM. On Windows EPERM means the pty-host exists but the caller lacks permission to signal it (cross-context), so the orphan was skipping the killProcessTree force-kill step and leaking. Mirror the destroy() logic at line 290: only flag exited on non-EPERM (typically ESRCH). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>		2026-05-04 22:33:33 +05:30
..
ao	chore: release 0.4.0 (#1625)	2026-05-04 06:57:24 +05:30
cli	fix(cli): Windows platform adapter follow-ups	2026-05-04 20:28:16 +05:30
core	fix(agent-kimicode): make plugin Windows-compatible	2026-05-04 18:20:50 +05:30
integration-tests	Merge origin/main into feat/windows-platform-adapter	2026-04-29 04:37:04 +05:30
plugins	fix(runtime-process): preserve EPERM in Windows pty-host sweep exit-poll	2026-05-04 22:33:33 +05:30
web	Merge remote-tracking branch 'origin/main' into feat/windows-platform-adapter	2026-05-04 20:42:56 +05:30