mirror of
https://github.com/deepseek-ai/deepseek-harness
synced 2026-08-15 21:04:50 +00:00
5533bb783a
Codex review of the reframe found stale "trusted-plugin surface/boundary" wording still in review-relevant spots the first pass missed: - docs/rfc/README.md index title for the RFC. - packages/bash/bash-local/src/run.ts (childEnv JSDoc + SpawnSpec stdin/env JSDoc + the spawn stdin comment) and src/index.ts (resolve carry-through comment); run.ts also pointed at a tool-bash README section name that no longer exists. - the two bash-local test descriptors (run.spec.ts / executor.spec.ts). - the tool-bash guard test's `boundary-*` call ids and one "boundary assertion" comment (renamed to `no-forward-*`). All reworded to the scrub-is-the-control framing (or neutral wording). The RFC FILENAME keeps `-trusted-plugin-surface` as a stable id (many links point at it; the index title and content are corrected). No code or behavior change.
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.