mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
b44066d544
- The implemented RFC named stack positions (PR-A…PR-F, "the hooks bridges (PR-F)") as shipped reality, violating the rule that an implemented RFC describes current truth and docs never name a change unit the reader cannot see. Rephrased to describe the hooks subsystem / a hook bridge as the standing motivating consumer, without PR/stack references. The decision and rationale are unchanged. - childEnv's comment pointed at dsh-tool-bash's "module doc" for the trusted-plugin boundary, but that explanation lives in the package README (§ "Trusted-plugin boundary"), not the module JSDoc. Fixed the reference.
bash/ — bash capability family
The canonical three-package capability seam (see capability seams): an abstract executor interface, a concrete local implementation, and the model-facing tool that consumes it. All product packages.
| Package | Role | ctx key |
|---|---|---|
bash/ |
Abstract bash executor seam (interface + vocabulary) | ctx.bash |
bash-local/ |
Local-subprocess BashExecutor implementation |
(registers ctx.bash) |
tool-bash/ |
Model-facing bash/bash_output/bash_kill tool schemas |
(registers on ctx.tools) |
The interface lives at bash/bash/. A sandboxed executor would replace bash-local without touching the interface or the tool — the split is what makes that possible.