dsh-loader-settlement-proof

In the DeepSeek Harness ecosystem, the Loader loading pipeline already carries multiple runtime assertions: app-boot assertEntriesLoaded and assertEntriesActivated, dsh-reloader, dsh-builtin-toggles, dsh-profile-lock-proof, and the Awesome runtime matrix. These mechanisms answer whether things are correct right now, yet none of them produce a revision-bound, independently re-verifiable settlement receipt for later inspection. dsh-loader-settlement-proof fills exactly that gap.

The plugin accepts a fixed, body-free settlement receipt and checks item by item: the DSH revision and Loader contract binding; the ordered declared to resolved to loaded to activated lifecycle; entry activation status and classified failures; requested versus resolved injections; required tool names with their schema SHA-256 receipts; and duplicates or cross-entry tool collisions across entries, phases, and tools. Verification results are emitted as deterministic, content-addressed JSON that the DSH CLI can publish beneath an explicit artifactDir and re-verify byte-for-byte, or invoke inline through MCP.

It is deliberately not another Loader: it never imports, runs, reloads, or toggles a recorded plugin, and it never ingests raw logs, stack traces, business bodies, or secrets. A verified verdict means only that the receipt is internally consistent with its explicit policy; it is not a security certification and cannot prove that the producer honestly observed the live Loader. This makes the plugin a natural fit for teams that need post-hoc audit trails, compliance evidence, or cross-team handoff of DSH Loader settlement results, giving security auditors and platform compliance reviewers a deterministic, offline-re-verifiable artifact.