dsh-recovery

When any optional plugin is missing or throws during activation, the entire DSH Web management interface goes down with it. dsh-recovery starts the management plane first, quarantines the failing entry for that run, and keeps the Web UI alive even when one or more optional plugins are broken, so you can continue working without restarting the whole service.

From the Settings to Recovery page you can inspect each failure by plugin ID, module name, failure category, and whether automatic repair is available. The repair workflow runs entirely in the browser: it reinstalls dependencies from npm, GitHub, or local sources already recorded in the profile manifest, retries plugin activation, or restores the last known healthy configuration. Profile files are backed up before any change, and if verification fails everything is rolled back automatically. Unknown package sources are never guessed, and Recovery does not hide failures in the Web server, API gateway, plugin inventory, or itself.

It is built for users running a Recovery-compatible DSH build with several optional plugins loaded, who occasionally hit broken third-party packages, upgrade conflicts, or profile configuration drift. The flow never calls a model API; the network is touched only when restoring a remotely sourced package, keeping the management surface self-sufficient and always online.