Skip to content
  • Home
  • Plugin manual
  • dsh-action-parity

dongsheng123132/dsh-action-parity

30Last commit Aug 14, 2026

dsh-action-parity DSH plugin

This plugin verifies that a business action is implemented once and reached consistently from CLI, MCP and GUI surfaces in DeepSeek Harness. It checks a manifest of stable Action IDs, content-addressed action-core and binding declarations, and structural replay observations produced by each interface. It does not execute business actions or test by pixels.

developer-tools

How to install the dsh-action-parity DSH plugin

dsh plugin --profile web add github:dongsheng123132/dsh-action-parity

Copying does not run this command. Review the repository and version before installing the dsh-action-parity DSH plugin.

dsh-action-parity DSH plugin data source

dsh-action-parity DSH plugin snapshot date: Aug 16, 2026

discovered

What the dsh-action-parity DSH plugin can do

  • Verifies that every CLI, MCP and GUI binding names the same stable actionId and coreActionId.
  • Checks that GUI bindings expose data-action-id:<actionId> while CLI and MCP use stable machine identifiers.
  • Verifies that core modules, binding declarations and replay fixtures still match their declared SHA-256.
  • Verifies that the same fixture yields the same result digest, success state and state-version transition on every surface.

Where the dsh-action-parity DSH plugin fits

  • Validating the example action in examples/basic for consistent implementation across CLI, MCP, and GUI.
  • Running inspect and verify commands on a custom workspace root to check action parity.
  • Ensuring that stale state mutations are rejected with STALE_STATE and do not advance state.
  • Enforcing confirmation-required actions on every surface.

Who the dsh-action-parity DSH plugin is for

  • Developers who implement business actions in DeepSeek Harness.
  • Engineers who need to ensure consistency across CLI, MCP, and GUI interfaces.

dsh-action-parity DSH plugin limitations

  • Does not execute the actual business actions, only verifies their declarations and replay fixtures.
  • Rejects inputs containing secret, prompt, chat, raw input/output, argv, stdout, or stderr fields.
  • Paths must remain inside workspaceRoot; symlink inputs and output directories are rejected.
  • Only the explicit artifactDir is written, with atomic publication and SHA-256 read-back verification.

dsh-action-parity DSH plugin: from the repository README

Quoted from the dongsheng123132/dsh-action-parity README, the upstream source of the dsh-action-parity DSH plugin. Copyright remains with the original authors.

Evidence that a business action is implemented once and reached consistently from CLI, MCP and GUI surfaces in [DeepSeek Harness](https://github.com/deepseek-ai/DeepSeek-Harness). This plugin does not execute business actions and does not test buttons by pixels. It verifies a manifest of stable Action IDs, content-addressed action-core and binding declarations, and structural replay observations produced by each interface. ## What it verifies - every CLI, MCP and GUI binding names the same stable `actionId` and `coreActionId`; - GUI bindings expose `data-action-id:<actionId>` while CLI and MCP use stable machine identifiers; - core modules, binding declarations and replay fixtures still match their declared SHA-256; - the same fixture yields the same result digest, success state and state-version transition on every surface; - stale mutations fail closed with `STALE_STATE` and do not advance state; - confirmation-required actions enforce confirmation on every surface; - missing/stale evidence and every parity failure are disclosed in a deterministic content-addressed report. Inputs containing secret-, prompt-, chat-, raw input/output-, argv-, stdout- or stderr-shaped fields are

Read the full READMERepository license: MIT

dsh-action-parity DSH plugin questions

How do I install dsh-action-parity?

Run `dsh plugin --profile web add github:dongsheng123132/dsh-action-parity`. This registers the `dsh_action_parity_inspect` and `dsh_action_parity_verify` commands.

What does dsh-action-parity verify?

It verifies that a business action is implemented consistently across CLI, MCP and GUI surfaces. It checks Action IDs, SHA-256 integrity of core modules and fixtures, and replay result consistency. It does not execute the actual action.

What are the exit codes?

Exit code 0 means success, 2 means parity failure, and 1 means invalid or unsafe input. The report is deterministic and content-addressed.

Can I use this plugin in CI?

Yes, the plugin is designed to be run as a CLI tool and can be integrated into CI pipelines. The repository includes a CI workflow as a reference.

Why does my input get rejected?

Inputs containing secret, prompt, chat, raw input/output, argv, stdout, or stderr fields are rejected. Paths must be inside workspaceRoot and symlink inputs/output directories are not allowed.