fix(chat): catch rethrown save errors in fire-and-forget callers

handleSaveAsNote intentionally rethrows so that the programmatic
autosaveCurrentChat path can detect failures and abort project switches.
However, two UI-driven callers (handleNewChat and the manual Save
button) did not catch the rethrown error, producing unhandled rejections.

Wrap both with .catch(() => {}) since the error is already logged and
noticed inside handleSaveAsNote itself.

Author: Emt-lin

src/components/Chat.tsx

@@ -704,9 +704,11 @@ const ChatInternal: React.FC<ChatProps & { chatInput: ReturnType<typeof useChatI
       }
     }
 
-    // First autosave the current chat if the setting is enabled
+    // First autosave the current chat if the setting is enabled.
+    // Reason: catch here because handleNewChat is called from an onClick handler
+    // where a rejected promise would become an unhandled rejection.
     if (settings.autosaveChat) {
-      await handleSaveAsNote();
+      await handleSaveAsNote().catch(() => {});
     }
 
     // Clear messages through the new architecture
@@ -896,7 +898,7 @@ const ChatInternal: React.FC<ChatProps & { chatInput: ReturnType<typeof useChatI
           <>
             <ChatControls
               onNewChat={handleNewChat}
-              onSaveAsNote={() => handleSaveAsNote()}
+              onSaveAsNote={() => handleSaveAsNote().catch(() => {})}
               onLoadHistory={handleLoadChatHistory}
               onModeChange={(newMode) => {
                 setPreviousMode(selectedChain);

src/main.ts

@@ -289,7 +289,14 @@ export default class CopilotPlugin extends Plugin {
     if (getSettings().autosaveChat) {
       const chatView = this.app.workspace.getLeavesOfType(CHAT_VIEWTYPE)[0]?.view as CopilotView;
       if (chatView) {
-        await chatView.saveChat(projectOverride);
+        if (projectOverride !== undefined) {
+          // Reason: project-switch path needs to detect save failure to abort the switch.
+          await chatView.saveChat(projectOverride);
+        } else {
+          // Reason: non-switch callers (loadChatHistory, newChat, settings reload) should
+          // not be blocked by a transient save error. Error is already logged+noticed inside.
+          await chatView.saveChat().catch(() => {});
+        }
       }
     }
   }