dsh-safe-launch

A single incompatible plugin or a broken core update can bring down a live DSH instance, and manual rollback is often slow and error-prone. dsh-safe-launch embeds a verify-before-deploy workflow directly into DSH so that every risky change is validated against your live configuration before it is ever applied to the real profile.

Every core upgrade, plugin install, and batch plugin update is first executed in an isolated environment on a random port, with HTTP health checks, process identity verification, an eight-second soak window, and fatal-error scanning. Only when the trial run passes is the change committed; otherwise the candidate is discarded and a rollback snapshot is preserved, leaving your current instance completely untouched. A manifest-fingerprint watchdog polls every five seconds and automatically triggers an isolated compatibility re-test whenever an out-of-band change is detected, either adopting the change into a new verified snapshot or raising a loud alert with rollback guidance.

If you run a long-lived DSH instance with multiple plugins and cannot afford downtime from a single bad dependency, dsh-safe-launch is built for you. A single restart after install bootstraps the last-good configuration from your running instance, and every subsequent risky operation follows a test-confirm-apply pipeline. A built-in settings panel and an optional desktop safe-launcher shortcut keep the entire workflow command-line-free.