Plugin activation and package replacement mechanism, specifically the plugin failing to enable correctly after installation, indicated by `app.asar` still being the active entry point and 'unlimited mode' disappearing after restart.

This issue reports a critical failure in plugin activation: despite installation, the `dsh-purge` plugin cannot enable correctly. The core problem is that `app.asar` remains the active service entry point, indicating the 'package replacement' process has not occurred or completed successfully. This prevents the plugin's modifications from taking effect. Furthermore, the 'unlimited mode' configuration disappears after a restart, suggesting a failure in persistent state management. This pain point highlights fundamental issues with the plugin's deployment, file system manipulation, and configuration persistence. For a B2B SaaS product, such activation failures render the product unusable and erode user trust. It necessitates a robust, atomic package replacement mechanism and reliable configuration storage to ensure the plugin's intended functionality is consistently applied and maintained.