Skip to content

dsh-substrate

Verified

@anweat/dsh-substrate · v0.1.2 · MIT · Web UI

Diagnoses DeepSeek Harness plugin conflicts and guides a version-locked external repair when one is available.

Install

dsh plugin add @anweat/dsh-substrate

Confirm the layer applied with dsh --profile default --dump-config — see the install guide.

Source

Tags

Readme

@anweat/dsh-substrate

dsh-substrate diagnoses DeepSeek Harness plugin conflicts and supplies a reversible, version-locked repair for duplicate loader entry IDs.

The Web card is read-only. It reports the detected DSH installation, the exact loader version, and the repair state. The external CLI performs installation changes so the running DSH process never rewrites its own dependencies.

Install in DSH

dsh plugin --profile web add @anweat/dsh-substrate@^0.1.2

Restart DSH after installing the plugin. Open the Substrate compatibility card to inspect the current state.

Repair duplicate entry IDs

Check whether the detected installation is supported:

npx --yes @anweat/[email protected] repair --home "<DSH_HOME>"

Apply the repair, then restart DSH:

npx --yes @anweat/[email protected] repair --home "<DSH_HOME>" --apply --yes

Revert the repair, then restart DSH again:

npx --yes @anweat/[email protected] repair --home "<DSH_HOME>" --revert --yes

The repair currently supports these exact packages:

The Git tag dsh-v0.1.3-alpha.1 has source-level evidence, but npm never published the matching dsh-app-boot package. It therefore remains outside the installable repair matrix.

Unknown versions are refused before any file is changed. The CLI stages a pnpm patch in the real DSH installation workspace, runs pnpm install, verifies the installed file, and supports a matching revert transaction.

This repair removes the duplicate entry-ID boot gate. It does not automatically isolate plugins that also claim the same Cordis service or tool names. Those later runtime conflicts still need service realms and tool scopes supplied by the host composition.

Version 0.1.0 users must add npm's peer-dependency compatibility flag when running the standalone CLI:

npx --yes --legacy-peer-deps @anweat/[email protected] repair --home "<DSH_HOME>"

See the compatibility matrix, browser coexistence verification, and tested boundaries.