stop-rudder-dev-maintainer

To stop pnpm dev safely, target only the current Rudder checkout's runtime using repo-root path checks and SIGTERM verification. This avoids broad pkill commands and prevents accidental shutdown of unrelated node, vite, or Electron processes.

The best way to clean up stuck Rudder local development processes is running a bundled stop script that matches repo-local dev runners and applies SIGTERM. It verifies survivors and only uses SIGKILL when explicitly passed with --force.

Graceful shutdown works by sending SIGTERM to matched Rudder dev and desktop runner processes, then verifying if anything survived. It confines matching to the current repository checkout, ensuring no production or unrelated repos are affected during the shutdown.

Yes, you can use the optional --dry-run flag with the stop script. This allows you to verify which repo-local pnpm dev processes match the current Rudder checkout before actually sending any SIGTERM or SIGKILL signals.

Leftover processes occur when standard termination fails to kill all child or desktop runners. You can handle survivors deterministically by running the stop script with the --force flag, which applies a targeted SIGKILL only to the remaining matched processes.