dsh-package-manager

Managing dsh-bundle plugins in DSH traditionally meant reaching into the Loader API or hand-assembling patch trees—fragile and impossible to hot-apply. dsh-package-manager collapses the entire pipeline into one action: install the plugin as a profile dependency, then normalize its dsh.bundle.patch into a managed block inside the profile's cordis.patch.yml. Subsequent hot-mount, hot-unmount, disable, and enable are all delegated to the host's existing watchUserPatches watcher; no extra Loader subtrees or recombination logic are introduced.

Lifecycle coverage is the core strength: installation writes the dependency and generates the managed block in a single step; uninstallation simply removes the block for an immediate hot-unmount; toggling only adds or removes a disabled row at the tail of the block, preserving the dependency and ledger record. For git-source plugins, ls-remote detects updates and auto-syncs the mirror. Additional capabilities include a declarative custom adapter for non-bundle plugins, minimal-diff deps.yaml synchronization, local plugin discovery, pre-install validation (rejecting workspace deps, non-ESM packages, missing entry points), and a doctor command to clean stale ledger entries and orphaned blocks. CLI, Web settings page, and programmatic API all share the same core, keeping behavior consistent and auditable.

Built for DSH developers who frequently add, remove, or toggle dsh-bundle plugins across profiles and want a single, auditable install pipeline without understanding Loader internals or restarting the host. Whether you drive it from the Web UI, the dpm CLI, or a batch script, the experience stays the same.