dsh-plugin-manager

Once a DSH Web profile accumulates dozens of plugin packages, a common headache follows: which package does a given plugin come from? Is it currently served by the Loader or managed by Cordis? And how do you safely swap one group of plugins for another without breaking your config? dsh-plugin-manager is built for exactly this: a three-level view of source packages, functional categories, and individual plugin instances gives every Loader entry a clear origin while surfacing Cordis FiberState and diagnostics right in the UI.\n\nEnable and disable operations go through a change-preview step and an atomic write that only touches the managed section of cordis.patch.yml, with the last twenty changes logged for one-click undo. The current set of third-party toggles can be saved as named schemes—Writing, Dev, Minimal—then re-applied after a quick preview. Agent presets can be forked from any official or user preset with a diff merge that preserves source-specific tools and comments. For npm-sourced third-party packages the manager can check versions, back up the lock file and managed state, invoke the official update command, and roll back automatically on failure; newly added sub-plugins from an update inherit the parent package's disabled status.\n\nIt is aimed at users who juggle multiple plugin combinations in DSH on a daily basis, switch between work modes frequently, and want every operation to be previewable, reversible, and isolated from other tools. Official host components and the manager itself are protected from being disabled, all sensitive write APIs require a loopback origin (LAN requests get 403), and the security boundary is kept tightly scoped to the manager's own state files.