From 355793b7e641d6c1ce9cbfe17f40f8561a280405 Mon Sep 17 00:00:00 2001
From: saopig1 <4x7sw862st@gmail.com>
Date: Sat, 30 May 2026 15:25:20 +0800
Subject: [PATCH] fix(scope): keep mounting if initial navigation errors
 (parity with old unconditional mount)

---
 web/src/main.ts | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/web/src/main.ts b/web/src/main.ts
index 6e34c52..89c0ef7 100644
--- a/web/src/main.ts
+++ b/web/src/main.ts
@@ -14,4 +14,7 @@ app.use(router);
 // Wait for the initial navigation (and the beforeEach guard that reads ?bot)
 // to fully resolve before mounting, so the reactive route query is populated
 // when App.onMounted runs and the dedicated-bot scope locks the right bot.
-router.isReady().then(() => app.mount('#app'));
+// .catch keeps parity with the old unconditional mount: if the initial
+// navigation errors (e.g. a transient network failure in the auth guard),
+// still render the shell rather than leaving a blank page.
+router.isReady().catch(() => {}).then(() => app.mount('#app'));