Priyanshu Choudhary 8dde130a0b fix(runtime-process): treat EPERM as alive in pty-host destroy probe ... destroy()'s 500 ms graceful-shutdown loop probes the pty-host with process.kill(pid, 0) and treats any throw as "process gone, clean exit". On Windows, cross-context processes can return EPERM — the process is alive but we lack permission to signal it. Returning early in that case orphans the pty-host and skips killProcessTree. Detect EPERM and break out of the wait loop so the orphan falls through to killProcessTree. Other error codes (ESRCH etc.) still mean the process is gone. Reported by Copilot review on PR #1025. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-30 22:59:05 +05:30
..
src	fix(runtime-process): treat EPERM as alive in pty-host destroy probe	2026-04-30 22:59:05 +05:30
CHANGELOG.md	chore: version packages	2026-03-20 15:47:55 +00:00
package.json	chore: merge origin/main into feat/windows-platform-adapter	2026-04-14 15:19:21 +05:30
tsconfig.json	fix: scope node types to node packages	2026-04-13 18:25:21 +05:30