From d9244cf0d774c0a9077ed41be1f6e2074f66a18a Mon Sep 17 00:00:00 2001 From: Arkadiusz Fal Date: Wed, 26 Aug 2026 23:52:02 +0200 Subject: [PATCH] Describe what the identity generation actually protects --- Yattee/Services/CloudKit/AccountSyncCoordinator.swift | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Yattee/Services/CloudKit/AccountSyncCoordinator.swift b/Yattee/Services/CloudKit/AccountSyncCoordinator.swift index 46835f01..959818d7 100644 --- a/Yattee/Services/CloudKit/AccountSyncCoordinator.swift +++ b/Yattee/Services/CloudKit/AccountSyncCoordinator.swift @@ -169,9 +169,11 @@ final class AccountSyncCoordinator { /// Handles the identity moving under a running app. /// - /// Nothing is migrated between namespaces here: the previous identity's - /// staging, outbox and bootstrap flag stay where they are, unread, and the - /// new identity starts from its own. + /// Nothing is migrated between namespaces: the previous identity's staging, + /// outbox and bootstrap flag stay where they are, unread, and the new one + /// starts from its own. Bumping the generation is what makes that stick — + /// work already in flight for the previous identity refuses to apply its + /// results afterwards. /// /// Internal so tests can drive it directly rather than racing a real scope /// resolution.