dsh-doublecheck: delivery quality gate (/gate) for DeepSeek Harness

[PerryLink]

dsh-doublecheck — the engineering-discipline bundle for DeepSeek Harness: v0.7.0 ships the delivery quality gate that folds a session's durable evidence into one deliverable / rework required decision.

What it solves / 解决什么问题

• /gate status|run|config: a four-phase checklist — requirements interrogation (key questions against the committed spec), test evidence (latest run color + optional coverage threshold), implementation consistency (local forked reviewer maps diffs to spec dimensions), and the review conclusion.
• One binary verdict with red items, rework suggestions, and a PR-ready gate-report.md; durable doublecheck/gate session event, audit-safe (counts/ids/verdicts only, secrets redacted).
• Weak dsh-auto-review dependency: folds its durable verdict records when installed, degrades honestly to the local reviewer otherwise.
• Plan-mode integration: rework verdicts suggest re-opening the work in plan mode.
• 四阶段可配置检查清单 + 单一「可交付/需返工」裁决 + 与 dsh-auto-review 弱依赖联动 + 计划模式建议。

Install / 安装

dsh plugin --profile web add dsh-doublecheck

Links / 链接

• Repository: https://github.com/PerryLink/dsh-doublecheck
• npm: https://www.npmjs.com/package/dsh-doublecheck
• Listed in: awesome-dsh-plugin#46, awesome-dsh-plugins#52, awesome-deepseek-harness#179, bruc3van/awesome-dsh-plugin#36

Apache-2.0 · issues and PRs welcome (中英文都欢迎).

[263311487-ux]

Nice — this is the evidence-gate layer. Complementary angle if useful: we built dsh-verify (browser acceptance testing for agent deliverables) after our 4-agent web team self-reviewed a demo as "no issues found" while the dark-mode toggle literally did nothing in a real browser — the .dark CSS rule was missing. Checklist gates and agent self-tests share the agent blind spot; an independent real-browser pass does not. dsh-verify takes a JSON spec (goto/click/expect_text/capture_style), drives headless Chromium, and returns an HTML report plus an exit code for CI. Buggy and fixed builds sit side by side in the repo as proof. It is now installable as a DSH plugin (dsh plugin add dsh-verify). Different layer from /gate: /gate decides, dsh-verify measures what the user actually experiences.

[PerryLink]

Thanks for the pointer — dsh-verify's browser-acceptance angle is exactly the complementary layer to /gate's evidence discipline (self-asserted evidence vs. a real browser telling the truth). Bookmarked for the doublecheck roadmap; happy to cross-link if you have a demo session where both run together.

[263311487-ux]

@PerryLink thanks for the kind words — cross-link sounds great. Concretely from our side:

1. dsh-doublecheck goes into the dsh-verify README (Related section) this week — evidence gate + browser verdict is a natural pairing.
2. Joint demo offer: dsh /gate collects the session evidence, then dsh-verify runs the human-style browser checks (click/fill/computed-style) on the delivered page and emits PASS/FAIL + screenshots. Two guarantees in one pipeline: /gate keeps the evidence honest, dsh-verify keeps the browser honest. Happy to build the browser side — open to your timing.
3. dsh-verify is already in awesome-dsh-plugin (category: browser) — happy to cross-reference your project there too.

[263311487-ux]

@PerryLink the joint guide is up — dsh-doublecheck × dsh-verify: the honest-delivery pipeline: https://github.com/263311487-ux/dsh-verify/blob/main/docs/doublecheck-gate.md

It covers: the division of labor (your /gate keeps the evidence honest, dsh-verify keeps the browser honest), install + one-pipeline usage, a joint report template for PRs, and live proof from this repo: the 4-agent team said "no issues found", the gate was green, and the real browser still caught the missing .dark CSS rule (FAIL 10/11, computed style never changed).

Open to your review — happy to fold in corrections, and to cross-link it from your README if useful.