@mmerterden/multi-agent-pipeline 20.7.0 → 20.8.0

package/pipeline/skills/shared/external/cloudkit-sync/evals/evals.json

@@ -2,45 +2,48 @@
   "skill_name": "cloudkit-sync",
   "evals": [
     {
-      "id": 1,
-      "prompt": "Review this iOS 26 CloudKit sync plan: a CKSyncEngine is configured against the public database, the app only enables iCloud + CloudKit, handleEvent and nextRecordZoneChangeBatch are implemented synchronously, nextRecordZoneChangeBatch returns every pending record-zone change, and the team expects automatic sync to run immediately after each local edit. Write concise corrected guidance with Swift snippets where useful.",
-      "expected_output": "A review that corrects CKSyncEngine database scope, Remote notifications setup, async delegate signatures, context-scoped change batches, state persistence, and automatic sync timing.",
+      "id": 0,
+      "name": "sync-engine-review",
+      "prompt": "Here is our plan for syncing a habit tracker with CKSyncEngine: point it at the public database so friends can see streaks, skip Remote notifications because the engine polls, write synchronous delegate methods, send every pending change in each batch, and rebuild the engine state from scratch each launch. Review it.",
+      "expected_output": "Explains CKSyncEngine supports only private and shared databases, requires the CloudKit capability plus the Remote notifications background mode, uses async handleEvent and nextRecordZoneChangeBatch, filters pending changes to the zones requested in the send context, notes that automatic timing is indeterminate so fetchChanges and sendChanges are used for immediacy, and persists stateSerialization from stateUpdate events.",
       "files": [],
-      "assertions": [
-        "States that CKSyncEngine is for private or shared databases and must not sync the public database.",
-        "States that CloudKit plus Remote notifications background mode are required for CKSyncEngine/background delivery.",
-        "Uses async CKSyncEngineDelegate signatures for handleEvent and nextRecordZoneChangeBatch.",
-        "Filters pending record-zone changes to the send context scope, such as context.options.zoneIDs.",
-        "Explains that automatic sync timing is indeterminate and immediate sync requires fetchChanges or sendChanges.",
-        "Mentions persisting CKSyncEngine stateSerialization across launches."
+      "expectations": [
+        "Rejects the public database for CKSyncEngine; private or shared only",
+        "Requires the CloudKit capability and Remote notifications",
+        "Uses async delegate methods",
+        "Filters pending changes to the zones the send context requests",
+        "Mentions indeterminate timing and fetchChanges or sendChanges for immediate sync",
+        "Persists stateSerialization across launches"
       ]
     },
     {
-      "id": 2,
-      "prompt": "Review this SwiftData model for CloudKit sync: it uses @Unique on an email field, has a nonoptional @Relationship(deleteRule: .deny) to Owner, stores a large image Data property without .externalStorage, and the reviewer says every scalar property must be optional. Explain what should change and what should not be overcorrected.",
-      "expected_output": "A review that flags SwiftData CloudKit schema incompatibilities without incorrectly requiring every scalar property to become optional.",
+      "id": 1,
+      "name": "swiftdata-cloudkit-model-check",
+      "prompt": "We're turning on CloudKit for our SwiftData recipe models. One model has @Attribute(.unique) on the slug, Recipe.author is a non-optional relationship with a .deny delete rule, and photos are stored as plain Data. We already shipped the schema to production once. What has to change?",
+      "expected_output": "Gives a model compatibility verdict (drop unique constraints, make relationships optional, avoid .deny, mark large Data as external storage, without demanding every scalar be optional) and a schema rollout verdict (initialize and inspect the development schema, promote before release, only additive changes after production promotion).",
       "files": [],
-      "assertions": [
-        "Flags @Unique or unique constraints as unsupported by SwiftData CloudKit sync.",
-        "Flags nonoptional relationships as incompatible and recommends optional relationships.",
-        "Flags the .deny relationship delete rule as incompatible with CloudKit sync.",
-        "Recommends @Attribute(.externalStorage) for large Data fields.",
-        "Does not claim every scalar property must be optional.",
-        "Mentions CloudKit production schemas are additive or require schema promotion care."
+      "expectations": [
+        "Flags the unique attribute as incompatible with CloudKit",
+        "Requires relationships to be optional",
+        "Flags the .deny delete rule",
+        "Recommends external storage for large Data",
+        "Does not insist that every scalar property be optional",
+        "Warns that production schema changes must be additive and promoted with care"
       ]
     },
     {
-      "id": 3,
-      "prompt": "Review this CloudKit data/query plan: the app stores sensitive profile fields in record.encryptedValues in the public database, adds a new encrypted field to an already-deployed field name, sorts and filters CKQuery results by that encrypted field, uses title CONTAINS 'road' for substring search, and stores image files as CKAsset. Give corrected guidance.",
-      "expected_output": "A review that corrects encrypted field limits, query predicate semantics, and CKAsset handling.",
+      "id": 2,
+      "name": "record-query-encryption-review",
+      "prompt": "Our CloudKit design stores medical notes in the public database with encryptedValues, converts the existing 'notes' field to encrypted, adds an index to sort by an encrypted field, searches titles with CONTAINS, and encrypts CKAsset attachments manually. What's wrong?",
+      "expected_output": "Explains encryptedValues are unavailable in the public database, existing fields cannot become encrypted, encrypted fields cannot be indexed, queried or sorted, CONTAINS on a field is list membership while self CONTAINS is tokenized full-text search, BEGINSWITH or self CONTAINS suits title search, and CKAsset data is already encrypted.",
       "files": [],
-      "assertions": [
-        "States that encryptedValues are not available for public database records.",
-        "States that CloudKit can encrypt only new schema fields, not convert an existing field name to encrypted storage.",
-        "States that encrypted fields cannot be indexed, queried, or sorted.",
-        "Explains that CKQuery CONTAINS is list membership except self CONTAINS tokenized full-text search.",
-        "Recommends BEGINSWITH or self CONTAINS where appropriate instead of title CONTAINS for substring search.",
-        "States that CKAsset data is already encrypted by default or does not need encryptedValues."
+      "expectations": [
+        "Says encrypted values are not available for public database records",
+        "Says an existing field cannot be converted to encrypted",
+        "Says encrypted fields cannot be queried, sorted or indexed",
+        "Explains CONTAINS list membership versus self CONTAINS full-text search",
+        "Suggests BEGINSWITH or self CONTAINS for text search",
+        "Notes CKAsset contents are encrypted by default"
       ]
     }
   ]