fix(web): probe pwsh through the executor's path resolution
The pwsh-terminal e2e probed the bare 'pwsh' literal, which knip flagged as an unlisted binary. Reuse resolvePwshPath from @deepseek-ai/dsh-pwsh-local (the judgment the tool-pwsh tests already use), so the probe matches the executor's own resolution and the reference stays indirect; record mode skips the lane anyway, so the probe stays inert there. Regenerate the cordis and config catalogs the seam moves left stale (line-number shifts).
This commit is contained in:
@@ -24,6 +24,7 @@
|
||||
"@deepseek-ai/dsh-client-ui-primitives": "workspace:^",
|
||||
"@deepseek-ai/dsh-client-ui-slots": "workspace:^",
|
||||
"@deepseek-ai/dsh-client-web-react": "workspace:^",
|
||||
"@deepseek-ai/dsh-pwsh-local": "workspace:^",
|
||||
"@types/node": "^22.0.0",
|
||||
"@types/react": "~18.3.1",
|
||||
"@types/react-dom": "~18.3.0",
|
||||
|
||||
Reference in New Issue
Block a user