Say what a timestamp tie actually does to the toggle

The tie test claimed the local record only repeated the server value, but
it fixtures opposing toggles stamped at the same instant, so name it for
the rule it proves. Note beside the strategy why that tie needs no
deterministic tiebreaker: no writer stamps these settings with a fixed
epoch date, unlike accounts and data contexts.

YatteeTests/CloudKitSyncTests.swift

@@ -197,7 +197,7 @@ struct CloudKitSyncTests {
             #expect(resolved["updatedAt"] as? Date == Date(timeIntervalSince1970: 2_000))
         }
 
-        @Test("A local record that only repeats the server value leaves it untouched")
+        @Test("Equal timestamps keep the server value")
         @MainActor
         func equalTimestampsKeepServerValue() async throws {
             let mapper = CloudKitSyncTests.makeMapper()