dsh-stack

A plugin list is not a working environment. Bundle order changes composition, version drift changes behavior, and the profile patch is what made the setup useful in the first place. dsh-stack captures that full contract—ordered plugin bundles, exact registry versions and commit-pinned Git sources, a portable profile-level Cordis patch, the source Harness version, and a whole-file SHA-256 digest—into a single small JSON Stackfile. It can live beside a project repo, a release note, a benchmark directory, or a bug report, and anyone can read it in full before allowing it to touch a profile.

The read path and the write path carry deliberately different authority. inspect validates integrity and portability, plan diffs the desired stack against a target profile, and export captures an installed profile into a new file. Only apply mutates a profile, and it does so behind a closed schema check, a rejection of unsafe specifiers and local paths, a printed install/ordering/patch/secret plan, a required --yes flag, an automatic backup, and a verification-and-rollback step. Credential fields are never written verbatim; they become environment-backed placeholders that inspect lists for you, and the real values are supplied only on the receiving machine. After installation, Harness also registers a read-only model tool called stack_inspect so you can pull the summary or the full redacted JSON at any point during a conversation.

If you need to share one agent configuration across a team, lock the environment for benchmarks and bug reproduction, or keep a team handbook in sync with what actually runs on each machine, dsh-stack is the layer that turns "works on my box" into "verified before it runs anywhere else."