@mmerterden/multi-agent-pipeline 20.7.0 → 20.8.0

package/pipeline/skills/shared/external/core-motion/evals/evals.json

@@ -3,47 +3,51 @@
   "evals": [
     {
       "id": 0,
-      "prompt": "Build a concise SwiftUI tilt-control service for an iOS game. It should read device motion at a reasonable rate, avoid wasting battery, and clean up correctly when the view disappears.",
-      "expected_output": "A Core Motion implementation outline that uses one CMMotionManager, includes NSMotionUsageDescription, checks availability/reference frames, starts device-motion or accelerometer updates at a suitable interval, handles errors/queues, and stops updates on lifecycle exit.",
+      "name": "tilt-control-service",
+      "prompt": "I'm adding a marble-maze screen to an iOS 26 SwiftUI app where the player tilts the phone to roll the marble. Sketch the motion service and how the view should start and stop it. Later we may want the maze to line up with compass north.",
+      "expected_output": "Adds NSMotionUsageDescription, keeps one shared CMMotionManager inside an observable service, checks isDeviceMotionAvailable, chooses a modest update interval such as 30 Hz, starts on appear and stops on disappear, and for the compass idea checks availableAttitudeReferenceFrames() before requesting a north-referenced frame, falling back to an arbitrary frame.",
       "files": [],
       "expectations": [
-        "Adds or calls out NSMotionUsageDescription before accessing motion data.",
-        "Uses a single shared CMMotionManager instead of one manager per view.",
-        "Checks isDeviceMotionAvailable or the relevant sensor availability before starting updates.",
-        "Chooses a modest update interval based on the interaction instead of defaulting to the highest possible rate.",
-        "Stops the matching updates when the view or service is no longer active.",
-        "Checks available attitude reference frames before requesting a north-based frame."
+        "Requires NSMotionUsageDescription in Info.plist",
+        "Uses a single shared CMMotionManager rather than one per view",
+        "Guards on isDeviceMotionAvailable before starting device motion",
+        "Picks a moderate interval instead of the maximum rate",
+        "Stops device-motion updates when the view leaves the screen",
+        "Checks availableAttitudeReferenceFrames() before using a magnetic or true north frame"
       ]
     },
     {
       "id": 1,
-      "prompt": "Review this plan for a hiking app: use CMPedometer for daily steps, CMMotionActivityManager to switch walking/driving modes, and CMAltimeter for elevation. The team says absolute altitude is GPS-based, activity flags are mutually exclusive, and only activity recognition needs motion permission.",
-      "expected_output": "A correction-focused review that covers NSMotionUsageDescription and authorization checks for pedometer/activity/altimeter, nonexclusive CMMotionActivity flags with confidence, and absolute altitude as sea-level altitude on supported hardware rather than GPS-based data.",
+      "name": "hiking-plan-review",
+      "prompt": "Review this plan for a hiking companion on iPhone and Apple Watch: count steps and floors with CMPedometer, label segments as walking or driving with CMMotionActivityManager, and show elevation above sea level from CMAltimeter using GPS-quality readings on every device. What is wrong or missing?",
+      "expected_output": "Points out that NSMotionUsageDescription must cover every Core Motion API used, that authorization status is read from the pedometer, activity and altimeter managers, that activity flags can overlap and must be weighed with confidence, that absolute altitude is sea-level based and not a GPS reading, and that it needs iPhone 12 or later or Apple Watch Series 6, SE or later behind isAbsoluteAltitudeAvailable(). Stays within Core Motion rather than drifting into HealthKit workouts or SensorKit.",
       "files": [],
       "expectations": [
-        "Requires NSMotionUsageDescription for the Core Motion APIs in the plan.",
-        "Checks CMAuthorizationStatus through the relevant pedometer, activity, or altimeter manager APIs before relying on data.",
-        "Explains that CMMotionActivity flags are not mutually exclusive and should be interpreted with confidence.",
-        "Describes absolute altitude as altitude relative to sea level, not GPS-based altitude.",
-        "Mentions that absolute altitude requires supported hardware such as iPhone 12 or later or Apple Watch Series 6/SE or later.",
-        "Keeps the answer in Core Motion scope rather than turning it into a HealthKit workout or SensorKit research guide."
+        "Requires NSMotionUsageDescription for all the motion APIs in the plan",
+        "Checks CMAuthorizationStatus through the pedometer, activity and altimeter managers",
+        "Explains that activity flags are not mutually exclusive and that confidence must be checked",
+        "Corrects the claim that absolute altitude is GPS based; it is relative to sea level",
+        "States the hardware floor: iPhone 12 or later, Apple Watch Series 6, Apple Watch SE or later",
+        "Keeps the answer inside Core Motion instead of recommending HealthKit or SensorKit"
       ]
     },
     {
       "id": 2,
-      "prompt": "I need advanced motion guidance for a watchOS app that analyzes golf swings with batched accelerometer data, tracks AirPods head motion during coaching, and supports shallow dive depth on Apple Watch Series 10/Ultra. What setup and API pitfalls should I avoid?",
-      "expected_output": "An advanced Core Motion guide that uses CMBatchedSensorManager safely without assigning read-only frequency properties, covers CMHeadphoneMotionManager privacy/connection behavior, and sets up CMWaterSubmersionManager with availability checks, motion usage text, Shallow Depth and Pressure or full entitlement, and underwater-depth background mode.",
+      "name": "golf-swing-airpods-dive",
+      "prompt": "Our watchOS and iOS sports suite needs three things: high-rate capture of a golf swing on the watch, head tracking through AirPods during a putting drill, and a dive log that records depth. How should each be built, and can we set the swing sampling rate to 800 Hz ourselves?",
+      "expected_output": "Uses CMBatchedSensorManager after checking isAccelerometerSupported and authorization, gated to watchOS 10 or later, and explains the frequency properties are read-only values to read, not set. Adds NSMotionUsageDescription for headphone and submersion features, uses CMHeadphoneMotionManager with a delegate and connection-status updates, checks CMWaterSubmersionManager.waterSubmersionAvailable before creating the manager, distinguishes the 6 m Shallow Depth and Pressure capability from the 40 m entitlement, adds underwater-depth to WKBackgroundModes, and does not say only Apple Watch Ultra supports shallow depth.",
       "files": [],
       "expectations": [
-        "Uses CMBatchedSensorManager only after checking support and authorization.",
-        "Does not assign accelerometerDataFrequency or deviceMotionDataFrequency and instead treats them as reported read-only frequencies.",
-        "Mentions watchOS 10+ async batched update sequences or otherwise gates batched update APIs by availability.",
-        "Includes NSMotionUsageDescription for headphone motion and submersion access.",
-        "Uses CMHeadphoneMotionManager delegate or connection-status updates for connect/disconnect behavior.",
-        "Checks CMWaterSubmersionManager.waterSubmersionAvailable before instantiating the manager.",
-        "Distinguishes Shallow Depth and Pressure capability for 6-meter dives from the full Submerged Depth and Pressure entitlement for 40-meter dives.",
-        "Adds WKBackgroundModes with underwater-depth for dive sessions/autolaunch and does not claim only Apple Watch Ultra can support shallow depth."
+        "Checks batched-sensor support and authorization before starting CMBatchedSensorManager",
+        "Says accelerometerDataFrequency and deviceMotionDataFrequency cannot be assigned",
+        "Gates the batched async sequences on watchOS 10 or later",
+        "Requires NSMotionUsageDescription for headphone motion and submersion",
+        "Uses a CMHeadphoneMotionManager delegate plus startConnectionStatusUpdates()",
+        "Checks waterSubmersionAvailable before instantiating CMWaterSubmersionManager",
+        "Separates the 6 m shallow-depth capability from the 40 m submerged-depth entitlement",
+        "Adds underwater-depth to WKBackgroundModes",
+        "Does not claim shallow depth is exclusive to Apple Watch Ultra"
       ]
     }
   ]
-}
+}