@mmerterden/multi-agent-pipeline 20.7.0 → 20.8.1

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

@@ -4,46 +4,44 @@
     {
       "id": 0,
       "name": "entitlement-setup-review",
-      "prompt": "Review this Core NFC setup before we hand it to the iOS team. The app needs to scan NDEF tags, read ISO 7816 identity cards by AID, and read a FeliCa transit tag. The draft entitlements include com.apple.developer.nfc.readersession.formats = [\"NDEF\", \"TAG\"], NFCReaderUsageDescription, and one ISO7816 AID. What should we change or verify?",
-      "expected_output": "A source-grounded setup review that corrects stale Core NFC entitlements and covers ISO 7816 and FeliCa configuration.",
+      "prompt": "Here is our NFC setup for a museum guide app. The entitlements file lists both NDEF and TAG under the reader session formats, NFCReaderUsageDescription is an empty string, we plan to read an ISO 7816 visitor card and a FeliCa ticket (we used a wildcard system code), and the Scan button always shows. What should change?",
+      "expected_output": "Keeps TAG as the only formats value, asks for a real usage sentence, lists the card AIDs under the ISO 7816 select-identifiers key and explicit FeliCa system codes without wildcards, and gates the Scan button on readingAvailable for the session class in use.",
       "files": [],
       "expectations": [
-        "States that the current `com.apple.developer.nfc.readersession.formats` value should use `TAG` and should not include legacy `NDEF`.",
-        "Requires a non-empty `NFCReaderUsageDescription` in Info.plist.",
-        "Requires `com.apple.developer.nfc.readersession.iso7816.select-identifiers` entries for ISO 7816 AIDs.",
-        "Requires `com.apple.developer.nfc.readersession.felica.systemcodes` entries for FeliCa and says wildcard system codes are not allowed.",
-        "Tells the team to check `NFCNDEFReaderSession.readingAvailable` or `NFCTagReaderSession.readingAvailable` before creating sessions."
+        "Drops NDEF from the reader-session formats entitlement so its only value is TAG",
+        "Requires a non-empty, user-facing NFCReaderUsageDescription",
+        "Puts the card AIDs in the Info.plist ISO 7816 select-identifiers array",
+        "Lists explicit FeliCa system codes and rejects the wildcard",
+        "Checks readingAvailable before showing the button or creating a session"
       ]
     },
     {
       "id": 1,
       "name": "native-tag-reader-boundary",
-      "prompt": "Design a concise Swift Core NFC tag scanner that can read ISO 7816, ISO 15693, MIFARE, and FeliCa tags. Also call out any payment-card or multi-tag pitfalls. Keep it as implementation guidance and snippets, not a full app.",
-      "expected_output": "Implementation guidance that uses NFCTagReaderSession correctly, maps polling options to tag families, and preserves payment-card boundaries.",
+      "prompt": "We want one scan screen that reads access cards (ISO 7816), inventory labels (ISO 15693), MIFARE Ultralight stickers and FeliCa passes, and later maybe a contactless bank card. Sometimes staff hold two badges together. Sketch the session code.",
+      "expected_output": "Uses one NFCTagReaderSession after a readingAvailable check, maps polling options to families, connects before switching on NFCTag, responds to two badges in the field with a message to take one away followed by restartPolling, and says bank card AIDs belong to NFCPaymentTagReaderSession where the EU entitlement applies, not to this session.",
       "files": [],
       "expectations": [
-        "Uses `NFCTagReaderSession` for native ISO 7816, ISO 15693, MIFARE, and FeliCa access.",
-        "Checks `NFCTagReaderSession.readingAvailable` before creating the session.",
-        "Maps `.iso14443` to ISO 7816-compatible and MIFARE tags, `.iso15693` to ISO 15693, and `.iso18092` to FeliCa.",
-        "Connects to the detected tag before sending protocol commands and switches over `NFCTag` cases.",
-        "Handles multiple detected tags by asking the user to remove extras and restarting polling rather than arbitrarily using every tag.",
-        "States that `NFCTagReaderSession` does not support payment-related AIDs and routes eligible EU payment use cases to `NFCPaymentTagReaderSession`."
+        "Chooses NFCTagReaderSession for all four native families and checks readingAvailable first",
+        "Maps .iso14443 to ISO 7816 and MIFARE, .iso15693 to vicinity labels and .iso18092 to FeliCa",
+        "Connects to the tag before any command and switches over the NFCTag cases with an unknown default",
+        "When more than one tag is detected, tells the user to remove the extras and calls restartPolling",
+        "Keeps bank card AIDs out of NFCTagReaderSession and points to NFCPaymentTagReaderSession, limited to qualifying EU payment apps"
       ]
     },
     {
       "id": 2,
       "name": "background-tag-routing",
-      "prompt": "A product manager wants an NFC tag to wake the app in the background by putting our bundle ID and a custom content type in the NDEF record. They also asked whether a custom myapp:// URL is fine. Write the corrected iOS implementation checklist.",
-      "expected_output": "A background tag reading checklist that corrects bundle-ID/content-type misconceptions and uses URI records and universal links.",
+      "prompt": "Our coffee shop stickers should open the app when an iPhone taps them with the app closed. We wrote a myshop:// URL and also tried adding our bundle ID as a MIME record. Nothing launches. How should the tags and the app be set up?",
+      "expected_output": "Explains background reading needs a well-known URI record, the first URI record is used, app routing needs a universal link plus Associated Domains, custom schemes and bundle ID or content-type routing do not work, and the app handles NSUserActivityTypeBrowsingWeb with ndefMessagePayload while skipping an empty first record.",
       "files": [],
       "expectations": [
-        "Says background tag reading looks for an NDEF URI record with type name format `.nfcWellKnown` and type `U`.",
-        "States that if multiple URI records exist, iOS uses the first URI record.",
-        "Uses universal links with Associated Domains for app-specific routing.",
-        "States that custom URL schemes are not supported for background tag reading.",
-        "Rejects routing by bundle ID or arbitrary NDEF content type.",
-        "Handles delivery through `NSUserActivityTypeBrowsingWeb` and `NSUserActivity.ndefMessagePayload`, including an empty-record guard for non-background activities."
+        "Requires a URI record with typeNameFormat .nfcWellKnown and type U, and notes the first URI record wins",
+        "Replaces myshop:// with a universal link and configures Associated Domains",
+        "States that custom schemes, bundle IDs and arbitrary content types cannot route background tags",
+        "Handles the launch in scene(_:continue:) by checking NSUserActivityTypeBrowsingWeb and reading ndefMessagePayload",
+        "Guards against a first record whose typeNameFormat is .empty"
       ]
     }
   ]
-}
+}