dsh-hotplug-engine

DSH manages plugin loading and unloading through cordis.patch.yml and its loader, yet the actual workflow is scattered across file edits, pnpm commands, and post-install health checks with no unified programmatic entry point. dsh-hotplug-engine bundles these steps into a single service: patch modification, pnpm invocation, post-install health verification, automatic rollback on failure, and full audit logging - all in one pipeline that only touches files and commands without modifying the DSH kernel.

At its core, the engine can toggle any patch line (both flow and block YAML), auto-rolls back when an install fails, and enforces a DSH default-disabled gate via a UI lock badge and a HOTPLUG.PATCH.DEFAULT_DISABLED API error. Three access patterns are exposed: host plugins inject the hotplugEngine service and call install, rollback, enable, and other methods directly; REST endpoints under the /api/dsh-hotplug prefix cover reads, writes, and SSE event streams; and agent-facing hotplug_* tools handle status, install, uninstall, toggle, rollback, and audit with write operations subject to approval.

This plugin fits teams and individuals who need to manage DSH plugins programmatically: developers building marketplace or admin-panel UIs, orchestration layers that dynamically install or remove plugins within agent workflows, and host-plugin authors who require auditable, rollback-capable plugin operations.