lemonmmice/dsh-agent-toolchain--plugins-dsh-verify ↗★ 0

dsh-verify

DSH 收尾裁决面插件:任务收尾 claims 清单交给机器裁决(build/api/file/manual),被证据反驳的 claim 自动记入失败样本库 适合需要对Agent任务交付物进行自动化硬校验和质量把控的场景。

Package
dsh-verify
Compatibility
Unverified
Version
0.1.0
License
Apache-2.0
Last updated
Sep 23, 2026

Other repositories with this package name

Install

This plugin has no verified bundle, or compatibility checks failed. Read the repository notes first. Read the full README ↗

dsh-verify

The DSH closing-adjudication surface — a thin shell over lib/verify/report.mjs (the same engine as the MCP verify_report tool). Zero logic lives here.

What it changes

Your task-closing summary stops being free text. You hand over a claims list (each claim = statement + evidence reference), and the machine adjudicates:

  • kind=build — reads the per-run build record (run-.json)
  • kind=api — queries the shared capture store (filter + expect.min/all2xx)
  • kind=file — checks an evidence artifact exists
  • kind=manual — explicit opt-out for what the system can't check

Verdict: pass / incomplete / fail. Claims contradicted by evidence auto-record into the failure corpus as agent-misjudge — the only data source for "caught the agent claiming success while the evidence disagrees".

The workflow (mandatory)

  1. Finish the work.
  2. Write down what you claim is done — as structured claims, not prose.
  3. Call verify_report(runId, task, claims), get the verdict.
  4. Report to the human: summary + verdict.

Skipping step 3 is a claim without verification. The trigger surface is the closing summary itself — an action you already perform every time — not a separate habit you have to remember.

See docs/verification-report.md.