decision(delete-user-data): kit/extension parity – kit continues after an Eventarc publish failure, the extension aborts #3254

delete-user-data kit/extension parity. Priority: low. The kit is intentionally more robust here; this needs recording, not fixing.

Difference

• Extension: eventChannel.publish() is awaited with no try/catch. If publishing fails, the error propagates. In clearData, a failed RTDB, Storage or Firestore event rejects Promise.all, so auto-discovery and SEARCH_FUNCTION are skipped. In handleSearch and handleDeletion, the function fails after deleting.
• Kit: publish failures are caught and logged as WARN, and deletion carries on. This came from 🐛 Eventarc custom event publishing crashes functions (unhandled rejections) & missing Declarative Security APIs/roles #3199.

Reproduced

• Kit: deployed with a channel the function couldn't publish to. Each event logged Failed to publish Eventarc event … 403 PERMISSION_DENIED at WARN, and deletion finished.
• Extension: with eventarc.publisher removed from the instance service account, clearData threw 403 … eventarc.channels.publish on its first Firestore event. Auto-discovery and SEARCH_FUNCTION never ran, so posts/<uid>, custom/<uid>, groups/g1/members/<uid> and the <uid> collection were all left behind.
• Kit, same IAM removal: every publish logged a WARN, and the same data was deleted.

Code

• Extension: publishes at index.ts#L106, #L139, #L260, #L303, #L348; clearData steps at #L227-L236.
• Kit: events.ts#L48-L56.

Resolution

Keep the kit's behaviour and record it as an accepted difference under "Decisions" in #3249.