Priyanshu Choudhary 0f5df48f06 fix(windows): probe absolute powershell path so PATH-degraded children don't fall through to cmd.exe ... The dashboard (Next.js) sometimes spawns the runtime-process pty-host with a PATH that lacks C:\Windows\System32. Both `pwsh` and `powershell.exe` probes in resolveWindowsShell() then fail and we drop to cmd.exe — which can't execute the PowerShell-syntax launch commands agents emit (e.g. Codex's `& 'codex' ...`), producing `'&' was unexpected at this time.` and an immediately-exited orchestrator. Probe %SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe directly via existsSync — this path is guaranteed on Windows 10+ and doesn't depend on PATH. Also add an AO_SHELL env override as an explicit escape hatch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-27 21:44:04 +05:30
..
ao	chore: bump all package versions to 0.2.5 (#1190)	2026-04-13 05:47:08 +05:30
cli	Merge origin/main into feat/windows-platform-adapter	2026-04-25 20:42:17 +05:30
core	fix(windows): probe absolute powershell path so PATH-degraded children don't fall through to cmd.exe	2026-04-27 21:44:04 +05:30
integration-tests	fix(test): update notifier-desktop integration test for Windows toast support	2026-04-25 21:39:00 +05:30
plugins	fix(agents): use shell:true on Windows in detect() to honor PATHEXT	2026-04-27 18:49:52 +05:30
web	fix(windows): junctions/hardlinks for symlinks, WinRT toast notifier, DPI re-fit	2026-04-25 21:29:49 +05:30