chore(servers): parallel keychain deletes for symmetry (#1356)

Picks up the symmetry observation from the third review: `deleteKeychainFields`
now uses `Promise.all` like its read and write siblings. Distinct (id, field)
deletes have no ordering requirement, and `secretStore.delete` is already a
silent no-op on unavailability so Promise.all has no failure-mode surprise.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: cliffhall

core/mcp/remote/node/server.ts

@@ -1292,13 +1292,15 @@ export function createRemoteApp(
     return obsolete;
   };
 
+  // Parallel for symmetry with `readKeychainEntriesFor` /
+  // `writeKeychainEntriesFor`: distinct (id, field) deletes have no
+  // ordering requirement, and `secretStore.delete` is already a silent
+  // no-op on unavailability so Promise.all has no failure-mode surprise.
   const deleteKeychainFields = async (
     id: string,
     fields: string[],
   ): Promise<void> => {
-    for (const field of fields) {
-      await secretStore.delete(id, field);
-    }
+    await Promise.all(fields.map((field) => secretStore.delete(id, field)));
   };
 
   const keychainErrorResponse = (