fix: improve app initialization error handling

- Add error dialog to notify users when initialization fails
- Log detailed error information for debugging
- Ensure app exits cleanly on initialization failure
- Prevent app from running in inconsistent state after init errors

This fixes the issue where app.whenReady().catch(console.log) would
silently swallow initialization errors, leaving the app running in a
zombie state with no user feedback.

Changes:
- Import dialog from electron
- Replace console.log with proper error handling
- Show user-friendly error dialog with error details
- Log full error stack trace for debugging
- Call app.quit() to exit cleanly

Severity: Critical (8-9/10)
Impact: Prevents app from running in inconsistent state, improves UX

Author: cxybd

apps/ui-tars/src/main/main.ts

@@ -8,6 +8,7 @@ import {
   BrowserView,
   BrowserWindow,
   desktopCapturer,
+  dialog,
   ipcMain,
   session,
   WebContentsView,
@@ -231,4 +232,17 @@ app
     logger.info('app.whenReady end');
   })
 
-  .catch(console.log);
+  .catch((error) => {
+    // Log detailed error information
+    logger.error('Failed to initialize app:', error);
+    logger.error('Error stack:', error.stack);
+
+    // Show user-friendly error dialog
+    dialog.showErrorBox(
+      'UI-TARS Initialization Failed',
+      `Failed to start UI-TARS:\n\n${error.message}\n\nPlease check the logs for details.\n\nThe application will now exit.`,
+    );
+
+    // Exit the application safely
+    app.quit();
+  });