Files
deepseek-harness/packages/bash
imccyu 2c85c484d3 build(release): reference workspace members through the workspace protocol
1504 hand-written ranges pointing at workspace members become workspace:^, so
pnpm pack substitutes each member's real version at publication: sibling
peerDependencies follow the family version instead of being pinned at ^0.0.1,
and a reference to a vendored package follows that package's own line. Without
this, publishing 0.0.2 ships peer ranges naming a version that does not exist,
and 0.0.1-rc.1 does not satisfy ^0.0.1 either.

It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6
for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0.

workspace:* stays where an exact published version is the point, which is how
the Landlock entry pins its platform packages.

A workspace constraint now requires the protocol, so a new package cannot
reintroduce a hand-written range. The same constraint caught packages/boot/cmdline
arriving on master without the publishable trio, which this change completes.
2026-08-11 00:17:09 +08:00
..

bash/ — bash capability family

English | 中文

The capability family spans the canonical executor seam, its implementations, the shared shell environment, and the model-facing tools. All are product packages.

Package Role ctx key
bash/ Defines the executor contract shared by Service providers and Consumers. ctx.bash
bash-local/ Executes commands through the local subprocess service. (registers ctx.bash)
bash-sandbox/ Applies the configured sandbox backend before local execution. (registers ctx.bash)
pwsh-local/ Executes PowerShell commands with Windows-specific process behavior. (registers ctx.bash)
bash-env/ Provides the managed DSH_* environment shared by shell tools. ctx.bashEnv
tool-bash/ Exposes Bash execution and background-task integration to the model. (registers on ctx.tools)
tool-pwsh/ Exposes PowerShell execution to the model. (registers on ctx.tools)

A leaf cordis.yml selects one executor implementation and the model-facing tools it needs. A sandboxed composition also selects a ctx.sandbox provider; the ACP example shows one complete wiring.

The subsystem reference — request/spec vocabulary, results, background processes, the service, and events — is docs/subsystems/bash.md.