dsh-deployment-rollback-proof
离线的内容寻址证明，表明失败的部署最终收敛到同一个最近已知良好的制品
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:dongsheng123132/dsh-deployment-rollback-proof#b9f7e37ba51cb7d29c0786179ad580f8eaf0d3fcDeployment Rollback Proof 以 dsh-deployment-rollback-proof 发布，当前版本为 0.1.1。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Offline, deterministic evidence that every declared deployment target stopped serving one failed artifact and converged within RTO to the same last-known-good digest.
This plugin does not execute rollback, authenticate receipts, grant authorization, observe live infrastructure, or prove application correctness. It verifies an explicit, hash-only manifest. That boundary is deliberate:
dsh-rollback restores file mutations; this plugin never mutates a deployment.dsh-recovery-proof verifies isolated recovery drills; this plugin verifies post-incident deployment-target convergence.dsh-artifact-promotion-proof proves positive promotion settlement; this plugin proves failed-version removal and last-known-good restoration.The manifest declares the failed digest, last-known-good digest, incident/authorization/plan receipt hashes, RTO and freshness limits, exact target set and replica counts. One observation per target binds a rollback receipt and health-probe hash to the incident and plan. The verifier checks:
Only hashes, counts, timestamps and verdicts enter the report. Keys named like secret, authorization, raw, body, content, log, prompt or chat, plus secret-shaped values, are rejected.
npm test
node bin/dsh-deployment-rollback-proof.mjs inspect examples/rolled-back.json
node bin/dsh-deployment-rollback-proof.mjs verify examples/rolled-back.json
DSH installs the bundle from cordis.patch.yml and exposes:
dsh_deployment_rollback_inspectdsh_deployment_rollback_verifyThe standalone stdio MCP server exposes deployment_rollback_inspect and deployment_rollback_verify. The DSH verifier writes only beneath an explicit workspace-relative artifactDir, rejects path escape/symlinks, creates a content-addressed report exclusively, and verifies it by read-back.
See examples/rolled-back.json. Inputs are claims bound by hashes, not authenticated facts. A rolled-back verdict means only that the supplied structured evidence satisfies the declared policy.
See SECURITY.md. Node.js 22 or later is required. Licensed under MIT.