Fix: guard server.updateSettings RPC call behind server config availability

In hosted-static mode, the cached LocalApi has no rpcClient, causing
server.* methods to reject. Now that settings routes are accessible in
hosted-static mode, the fire-and-forget updateSettings call would produce
unhandled promise rejections. Move the RPC call inside the existing
currentServerConfig guard so it only fires when a server is connected.

Author: cursoragent

apps/web/src/hooks/useSettings.ts

@@ -165,9 +165,9 @@ export function useUpdateSettings() {
       const currentServerConfig = getServerConfig();
       if (currentServerConfig) {
         applySettingsUpdated(applyServerSettingsPatch(currentServerConfig.settings, serverPatch));
+        // Fire-and-forget RPC — push will reconcile on success
+        void ensureLocalApi().server.updateSettings(serverPatch);
       }
-      // Fire-and-forget RPC — push will reconcile on success
-      void ensureLocalApi().server.updateSettings(serverPatch);
     }
 
     if (Object.keys(clientPatch).length > 0) {