fix(core): propagate navigation errors to prevent silent skips

When a NAV_LOST or missing search component error occurred during company
processing, the error was swallowed by the catch block, causing the
loop to skip remaining companies without triggering the session retry.
Now re-throwing fatal errors to properly trigger the account-level recovery.
Also optimized navigateBackToList to skip goBack when already on the list page.

Author: SSARCandy

src/automation/main_flow.js

@@ -85,6 +85,11 @@ async function processCompany(webContents, id, company, context, sendLog, emitPr
 
   } catch (procError) {
     if (isStopRequested()) return;
+    
+    if (procError.message.includes('NAV_LOST') || procError.message.includes('找不到搜尋元件')) {
+      throw procError; // Propagate fatal errors to trigger account-level retry
+    }
+    
     sendLog(`[錯誤] ${code} 異常: ${procError.message}，下一間。`, 'error');
   }
 }

src/automation/voting.js

@@ -327,10 +327,12 @@ async function navigateBackToList(webContents, sendLog) {
     if (clickedBack) {
       await waitForNavigation(webContents, 8000);
     } else {
-      sendLog('[導航] 無回列表鈕，嘗試回上頁...');
-      const waitP = waitForNavigation(webContents, 5000);
-      webContents.goBack();
-      await waitP;
+      if (!(await isAtListPage(webContents))) {
+        sendLog('[導航] 無回列表鈕，嘗試回上頁...');
+        const waitP = waitForNavigation(webContents, 5000);
+        webContents.goBack();
+        await waitP;
+      }
     }
   } catch (e) {
     sendLog(`[導航] 返回過程異常: ${e.message}`, 'warning');