Add a test seam to skip the background-service consent dialog under automation (#1170)

The first-run "keep Executor running in the background?" dialog cannot be
answered from CDP or Playwright, so a packaged first-run boot under automation
blocks here with no way to proceed (on macOS the modal also starves the app's
main run loop). Add an EXECUTOR_TEST_AUTO_CONFIRM_BACKGROUND_SERVICE env seam,
the same pattern confirmResetState already uses: "1" keeps the service, any
other value declines, and when unset the dialog is shown as before.

Author: RhysSullivan

.changeset/desktop-background-service-consent-seam.md

@@ -0,0 +1,5 @@
+---
+"executor": patch
+---
+
+Add a test seam to skip the first-run "keep Executor running in the background?" consent dialog under automation, matching the existing `confirmResetState` seam. Set `EXECUTOR_TEST_AUTO_CONFIRM_BACKGROUND_SERVICE=1` to keep the background service or any other value to decline. When the variable is unset the dialog is shown exactly as before. Native dialogs cannot be answered from CDP or Playwright, so a packaged first-run boot under automation previously blocked at this prompt with no way to proceed.

apps/desktop/src/main/index.ts

@@ -190,6 +190,13 @@ const waitForSupervisedAttach = async (
 };
 
 const confirmEnableBackgroundService = async (): Promise<boolean> => {
+  // EXECUTOR_TEST_AUTO_CONFIRM_BACKGROUND_SERVICE skips the modal, the same seam
+  // as confirmResetState. Native dialogs are unreachable from CDP/Playwright, so
+  // a first-run boot under automation otherwise blocks here forever with no way
+  // to answer. "1" keeps the background service; any other value declines and
+  // falls back to the managed sidecar.
+  const autoConfirm = process.env.EXECUTOR_TEST_AUTO_CONFIRM_BACKGROUND_SERVICE;
+  if (autoConfirm !== undefined) return autoConfirm === "1";
   const { response } = await dialog.showMessageBox({
     type: "question",
     title: "Keep Executor running in the background?",