In the DeepSeek Harness (DSH) development workflow, validation of build artifacts and check results often relies on remote or complex CI pipelines. Developers working locally need a lightweight mechanism to generate definitive delivery proof before merging code. dsh-shipgate provides this local-first solution.

Positioning and Background

dsh-shipgate is a local-first pre-merge delivery receipt generation plugin. It is used as a DSH Bundle to inject the tools service into Harness and register the shipgate_inspect tool. The plugin reuses the local inspect core as a CLI, does not perform checks, does not upload source code, and does not claim code correctness.

Core Capabilities

  • Local-first pre-merge receipt generation.
  • Injects the DSH tools service and registers the shipgate_inspect tool.
  • Reuses the local inspect core as a command-line interface.
  • Does not execute check logic, upload source code, or claim code correctness.

Installation and Enablement

Install it according to your DSH Bundle workflow. The plugin injects the DSH tools service into the Harness environment and completes registration of the shipgate_inspect tool.

Typical Usage

Command-Line Invocation

Run the built CLI, specifying the Git comparison base, check evidence files, and an intent description.

node /Users/albert.liu/Projects/dsh-delivery-gate/shipgate/dist/cli.js inspect --base origin/main --checks checks. --intent "Add checkout validation"

DSH Tool Invocation

Call the registered shipgate_inspect tool in Harness. At minimum, provide the base and checks parameters.

{
  "base": "origin/main",
  "checks": "checks.",
  "ci": true
}

The tool returns the receipt ID, result status, risk level, artifact paths, and a Markdown summary. By default, ci: false is advisory mode; setting ci: true applies the project’s configured failure policy.

Use Cases and Notes

Use Cases: You need to generate delivery proof locally, or quickly validate check results in CI, without uploading source code or relying on remote execution environments.

Notes:
* Local mode is advisory. To apply the project’s failure policy, add ci: true when invoking.
* Product boundaries and validation criteria are defined in PROJECT.md.
* The plugin runs on the user’s GitHub Runner and does not upload source code or Receipts.
* The environment requires Node.js 20 or higher.
* When using a GitHub Action, it must be paired with actions/checkout@v4 and have fetch-depth: 0 set to resolve the merge base.

Summary

dsh-shipgate focuses on local delivery proof generation and, by reusing the inspect core, provides a lightweight, controllable validation solution for the DSH workflow.