Looks like the issue was fixed on macOS 26.1!

Running into the same issue here. At this point, I’m considering using a CKSyncEngine with manual sync behavior only for the initial fetch, then discarding it and switching to a different CKSyncEngine instance with automatic sync behavior for the rest of the session. Managing this feels a bit clunky, though. Would love some clarification from Apple engineers on this.