connector-apple-calendar: defer etag write until event processing succeeds

Follow-up to ad61247. Per-event parse failure (caught at the try/catch
inside processCalDAVEvents loop) would still leave that event's etag
in the persistent map with no corresponding uid, recreating the bug
the prior commit fixed but at a much narrower failure rate. Move the
etag write to the end of the per-event try block so the etag is only
recorded when the uid was also recorded.

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

Author: KrisBraun

connectors/apple-calendar/src/apple-calendar.ts

@@ -715,14 +715,6 @@ export class AppleCalendar extends Connector<AppleCalendar> {
     let etagMapDirty = false;
 
     for (const caldavEvent of events) {
-      // Record the etag up-front for every event in this batch so the
-      // stored set matches the uids we're about to record. Both maps are
-      // persisted together below.
-      if (etagMap[caldavEvent.href] !== caldavEvent.etag) {
-        etagMap[caldavEvent.href] = caldavEvent.etag;
-        etagMapDirty = true;
-      }
-
       try {
         const icsEvents = parseICSEvents(caldavEvent.icsData);
 
@@ -751,6 +743,14 @@ export class AppleCalendar extends Connector<AppleCalendar> {
             );
           }
         }
+
+        // Record etag only after the per-event work succeeds so a parse
+        // failure can't leave an etag without a uid (which would later
+        // surface as a `missingUid` skip on deletion).
+        if (etagMap[caldavEvent.href] !== caldavEvent.etag) {
+          etagMap[caldavEvent.href] = caldavEvent.etag;
+          etagMapDirty = true;
+        }
       } catch (error) {
         console.error(
           `Error processing CalDAV event ${caldavEvent.href}:`,