DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins

@playform/ets-hook-dsh-workspace-approve

Ets Hook Dsh Workspace Approve

workspace-approve hook:一个 DeepSeek Harness 插件,用于绑定确切的人类批准——与候选项绑定的批准及其约束(不可见流程中的该系列批准步骤:授权许可 -> 批准绑定 -> 合并提交)。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add @playform/ets-hook-dsh-workspace-approve@0.2.1
README兼容性版本

兼容性与来源证明

Ets Hook Dsh Workspace Approve 以 @playform/ets-hook-dsh-workspace-approve 发布,当前版本为 0.2.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
npm
Registry 更新时间
2026/11/4

版本

0.2.1stable
2026/10/28
0.2.0stable
2026/10/25
0.1.0stable
2026/10/25

相关插件

正在加载相关插件…

最新版
0.2.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
37.7 kB
文件数
44
Surface
any
许可证
CC0-1.0
发布源
npm
GitHub
★ 2
周下载
283
安全扫描
✓ v0.2.1 扫描通过
最近提交
2026/11/4
查看源码 ↗项目主页 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 security-access 分类下经过校验的插件。

Cc Safety Netcc-safety-net编码代理 CLI 钩子——阻止破坏性命令和访问机密文件Doctor@linxin666/dsh-doctorDSH 配置档案的事务性救援模式,配备受监督的启动器、隔离的恢复容器、确定性修复、健康监控以及本地 Web 恢复控制台Pocketdsh-pocket把 DeepSeek Harness 装进你的口袋:一个包、一个设置页,手机扫码即同步访问电脑上的 DSH(局域网 + 公网,实时同屏)。Codex Subscriptiondsh-codex-subscription在 DeepSeek Harness 中通过 OAuth 使用 ChatGPT 和 Codex 订阅,支持配额、安全重置、网络搜索、图像和快速模式,并可通过 ChatGPT 移动应用(Beta)控制 DSH

README

@playform/hook-dsh-workspace-approve

v0.1.0 - UNPUBLISHED - plan: Workspace-Family/APPROVE

The role

The workspace-approve hook for the DeepSeek Harness plugin family (the Classic release).

It is a DeepSeek Harness plugin that binds the exact human approval (the candidate-bound approval plus the constraints), the approve step of the invisible flow of the workspace family:

... -> the authority licenses -> the approve binds -> the merge commits -> ...

The exact-approval semantics

An approval binds to the exact candidate: the concrete change set, identified by its path, its content fingerprint, and the file version observed at the approval, never a fuzzy intent.

The constraints travel with the approval: a changed constraint set at approval time is a rejection, not an amendment.

The decision records the Commitment (who accepted responsibility).

The merge/execute side derives its AuthorizationDecision from the check of the service.

An intent must not authorize its own means: the approval of an intention never authorizes the implementation the agent later produces.

The check only validates the implementation against the approved candidate, because the independent authority licensing happened earlier in the flow.

The service surface (ctx.workspaceApprove)

MethodBehavior
bind(candidate)Register an exact candidate (path + fingerprint + version + constraints) as a pending binding; rejected with its own ledger line when the identity is incomplete or constraints are required and missing.
approve(id, who, constraints?)A pending binding becomes approved; a changed constraint set rejects.
deny(id, who)A pending binding becomes denied.
revoke(id, who)An approved binding becomes revoked.
check(request)The exactness check: approved only when an approved binding covers the exact fingerprint AND the version is unchanged; otherwise unbound / the binding's decision / stale.
binding(id) / bindings(limit?) / statistics()The read surface.

The invalidation listener

On fs/observed (heard on the ROOT context through the Wire of the factory), a binding whose file is observed at a different version than the one bound in the approval is invalidated (decision: "invalidated", ledger invalidated <id> (version changed)).

The listener is a synchronous recorder: no awaits, no throws, no I/O, and own-actor events are ignored.

Storage and ledger

State lives in the own KV domain of the hook named workspace_approve (config domain): one record per binding plus a bounded ring snapshot (the last maxBindings, default 1000).

The sequence is the own monotonic counter of the plugin, never a wall clock.

Ledger lines (module-owned, prefixed approve:): activated, disabled, bound, decided, rejected, revoked, refused, unknown, invalidated, checked, capped, failed, storage open failed.

The configuration

Every knob is volatile (hot-editable without remounting): logFile (~/.dsh/playform/ets-hook-dsh-workspace-approve.log), log, enabled (false, the IDLE-forever posture), domain (workspace_approve), maxBindings (1000), and requireConstraints (true).

The plugin ships disabled and enables only by an explicit ACTIVATE.

The policy block (D6)

The config carries the shared per-action allowlist (policy: Policy(), composed from the block of the factory), mapped to State.Allow:

actiondefaultactiondefault
readautowriteapprove
indexautocommitapprove
recordautospawnapprove
suggestautomessageauto

The actions of this package are record, all AUTOMATIC; it has NO gated action (no file write, no batch commit, no spawn), so the block documents the posture and refuses nothing.

The block is one volatile object, so a policy flip is hot-editable without a remount, and the policy section of a resolved pack overrides the defaults per action (the wiring is the next refinement).

The plan

  • Workspace-Family/APPROVE - the approve step of the invisible flow.

License

CC0-1.0.