Fix silent startup failure and missing provider refresh for primary environments

Bug 1: When backend readiness timed out in packaged mode, the catch handler
only logged a warning — no window was created and handleFatalStartupError was
never called. Now the error propagates to handleFatalStartupError so the user
sees an error dialog instead of an invisible, unrecoverable app.

Bug 2: The config subscription condition excluded primary environments because
it only matched kind=="saved" or explicit onConfigSnapshot. Added
kind=="primary" to the condition so desktop users get the subscribeServerConfig
subscription and the associated provider refresh fires immediately instead of
waiting for the 60-second periodic timer.

Author: cursoragent

apps/desktop/src/main.ts

@@ -448,10 +448,7 @@ function ensureInitialBackendWindowOpen(): void {
       if (isBackendReadinessAborted(error)) {
         return;
       }
-      writeDesktopLogHeader(
-        `bootstrap backend readiness warning message=${formatErrorMessage(error)}`,
-      );
-      console.warn("[desktop] backend readiness check timed out during packaged bootstrap", error);
+      handleFatalStartupError("backend-readiness", error);
     })
     .finally(() => {
       if (backendInitialWindowOpenInFlight === nextOpen) {

apps/web/src/environments/runtime/connection.ts

@@ -264,7 +264,7 @@ export function createEnvironmentConnection(
   );
 
   const unsubConfig =
-    input.kind === "saved" || input.onConfigSnapshot
+    input.kind === "saved" || input.kind === "primary" || input.onConfigSnapshot
       ? input.client.server.subscribeConfig(
           (event: Parameters<Parameters<WsRpcClient["server"]["subscribeConfig"]>[0]>[0]) => {
             if (event.type !== "snapshot") {