dsh-profile-lock-proof

In the DeepSeek Harness ecosystem, there is no lightweight, auditable way to confirm that a profile's dependency declarations, pnpm lockfile, installed package metadata, and each package's dsh.bundle.patch are genuinely in sync. dsh-profile-lock-proof fills that gap by producing a content-addressed, machine-readable proof that cross-checks specifiers, hashes, and patches across every layer. Any missing, stale, mutable, or mismatched evidence causes the check to fail closed. The entire verification never executes package code, never touches the network, never mutates the profile, and never discloses raw manifest, lockfile, patch, script-command, or secret content—what you get is a pure structural assertion.

Inputs are strictly confined to workspace-relative regular files; symlink traversal and path escape are rejected outright. Profile and lockfile bytes must match the SHA-256 values recorded in an explicit proof manifest. Dependency specifiers must be exact semver or github:owner/repo# references. The pnpm importer specifier, the installed name/version/package hash, the bundle patch path and hash, and the absence of lifecycle hooks must all four-way agree. On success the report is written atomically into an explicit artifactDir and read back for confirmation; on failure a non-zero exit code is returned, making it drop-in ready for CI pipelines or shell orchestration.

If you maintain or audit DeepSeek Harness profiles and want a zero-side-effect, reproducible consistency check without dragging in a full SBOM toolchain, triggering network calls, or executing third-party code, this plugin is that lock. It also fits naturally into CI as a regression gate on every profile change, or as a self-contained evidence bundle for third-party auditors before delivery.