rudder-desktop-dev-recovery-maintainer

Rudder Desktop dev startup failures are fixed by classifying whether the blocker is the API server, Electron shell, or embedded Postgres, then applying a minimal repair to restore the known working runtime.

Confusing local instance state usually stems from embedded Postgres or ~/.rudder mismatches; validating the correct recovery path and applying safe, narrow repairs resolves the update failure without wiping data.

Yes, you can recover the dev environment without destructive actions by applying minimal fixes like stopping stale processes and validating health endpoints, avoiding local data wipes unless explicitly authorized.

The best way to troubleshoot embedded Postgres issues is to verify local API health, isolate the database layer as the failure mode, and apply targeted narrow repairs to restore the local instance state.

Validate the Rudder Desktop runtime by checking local health and organization endpoints, confirming Desktop launch and update pathways, and escalating to release-maintainer only after local state is green.

When dirty-WIP files block the Electron shell, preserve unrelated worktree files and apply fixture or compile ownership packets to resolve the typecheck and restore the build.