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:
3
pnpm-lock.yaml
generated
3
pnpm-lock.yaml
generated
@@ -520,6 +520,9 @@ importers:
|
||||
'@deepseek-ai/dsh-client-web-react':
|
||||
specifier: workspace:^
|
||||
version: link:../../packages/client/web-react
|
||||
'@deepseek-ai/dsh-pwsh-local':
|
||||
specifier: workspace:^
|
||||
version: link:../../packages/bash/pwsh-local
|
||||
'@types/node':
|
||||
specifier: ^22.0.0
|
||||
version: 22.20.0
|
||||
|
||||
Reference in New Issue
Block a user