@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/shared/external/natural-language/references/translation-patterns.md

@@ -172,19 +172,22 @@ struct EditableTranslationView: View {
 
 ## Translation Session Strategies
 
-Control whether translations prioritize quality or speed.
+Control whether translations prioritize quality or speed. Strategy selection
+requires iOS 26.4+ / macOS 26.4+. Translation content is processed on device;
+`.highFidelity` uses Apple Intelligence models when available, and
+`.lowLatency` uses traditional models.
 
 ```swift
 import Translation
 
-// High fidelity: best quality, may use server
+// High fidelity: more fluent translations when Apple Intelligence is available
 let highQualityConfig = TranslationSession.Configuration(
     source: Locale.Language(identifier: "en"),
     target: Locale.Language(identifier: "ja"),
     preferredStrategy: .highFidelity
 )
 
-// Low latency: faster, prefers on-device models
+// Low latency: faster traditional translation models
 let fastConfig = TranslationSession.Configuration(
     source: Locale.Language(identifier: "en"),
     target: Locale.Language(identifier: "ja"),
@@ -198,13 +201,23 @@ Pre-download models before translating to avoid UI delays.
 
 ```swift
 .translationTask(configuration) { session in
-    try await session.prepareTranslation()
-    // Models are now ready, translate without delay
-    let response = try await session.translate(sourceText)
-    translatedText = response.targetText
+    do {
+        try await session.prepareTranslation()
+        // Models are now ready, translate without delay
+        let response = try await session.translate(sourceText)
+        await MainActor.run {
+            translatedText = response.targetText
+        }
+    } catch {
+        // Handle download refusal, cancellation, or unsupported language pairs.
+    }
 }
 ```
 
+For non-UI translation, initialize `TranslationSession(installedSource:target:)`
+only after the source and target languages are installed; this initializer
+throws when the required languages are unavailable.
+
 ## SwiftUI Integration Patterns
 
 ### Language Analysis View

package/pipeline/skills/shared/external/nextjs-app-router/SKILL.md

@@ -1,4 +1,5 @@
 ---
+name: nextjs-app-router
 description: "Next.js 15+ App Router: Server/Client Components, Server Actions, data fetching, layouts, middleware, ISR/SSG/SSR, and routing patterns"
 tags: [nextjs, react, frontend, ssr, app-router, full-stack]
 version: "2025.1"
@@ -39,7 +40,7 @@ app/
 ### Server Components (Default)
 
 ```tsx
-// app/users/page.tsx — Server Component (no directive needed)
+// app/users/page.tsx  -  Server Component (no directive needed)
 import { db } from '@/lib/db';
 
 export default async function UsersPage() {
@@ -182,7 +183,7 @@ const data = await fetch('https://api.example.com/data', {
 
 ```tsx
 export default async function DashboardPage() {
-  // Fetch in parallel — do NOT await sequentially
+  // Fetch in parallel  -  do NOT await sequentially
   const [stats, recentOrders, notifications] = await Promise.all([
     fetchStats(),
     fetchRecentOrders(),
@@ -208,7 +209,7 @@ export default function DashboardPage() {
   return (
     <div>
       <h1>Dashboard</h1>
-      {/* Instant — static content */}
+      {/* Instant  -  static content */}
       <WelcomeMessage />
 
       {/* Streams in when ready */}

package/pipeline/skills/shared/external/passkit-wallet/SKILL.md

@@ -1,13 +1,19 @@
 ---
 name: passkit-wallet
-description: "Integrate Apple Pay payments and Wallet passes using PassKit. Use when adding Apple Pay buttons, creating payment requests, handling payment authorization, adding passes to Wallet, configuring merchant capabilities, managing shipping and contact fields, or working with PKPaymentRequest, PKPaymentAuthorizationController, PKPaymentButton, PKPass, PKAddPassesViewController, PKPassLibrary, or Apple Pay checkout flows."
+description: "Integrate Apple Pay payments and Wallet passes using PassKit. Use when adding Apple Pay buttons, creating payment requests, handling payment authorization, adding passes to Wallet, configuring merchant capabilities, managing shipping/contact fields, or working with PKPaymentRequest, PKPaymentAuthorizationController, PKPaymentButton, AddPassToWalletButton, PKPass, PKAddPassesViewController, PKPassLibrary, Wallet pass distribution, or Apple Pay checkout flows for physical goods, real-world services, donations, and eligible recurring payments."
 ---
 
-# PassKit — Apple Pay & Wallet
+# PassKit
 
-Accept Apple Pay payments for physical goods and services, and add passes to
-the user's Wallet. Covers payment buttons, payment requests, authorization,
-Wallet passes, and merchant configuration. Targets Swift 6.2 / iOS 26+.
+Accept Apple Pay payments for physical goods, real-world services, donations,
+and eligible recurring payments, and add passes to the user's Wallet. Covers
+payment buttons, payment requests, authorization, Wallet passes, and merchant
+configuration. Targets Swift 6.3 / iOS 26+.
+
+For advanced Apple Pay flows, one `PKPaymentRequest` can set only one optional
+advanced request type: recurring, automatic reload, deferred, Apple Pay Later
+availability, or multi-token contexts. Use separate payment requests when a
+checkout needs more than one of those modes.
 
 ## Contents
 
@@ -33,7 +39,10 @@ Wallet passes, and merchant configuration. Targets Swift 6.2 / iOS 26+.
 
 ### Availability Check
 
-Always verify the device can make payments before showing Apple Pay UI.
+Always verify the device can make payments before showing Apple Pay UI. If you
+check for an active card with `canMakePayments(usingNetworks:capabilities:)`,
+Apple's HIG expects Apple Pay to be a primary, prominent payment option wherever
+you use that check.
 
 ```swift
 import PassKit
@@ -55,7 +64,9 @@ func canMakePayments() -> Bool {
 
 ### SwiftUI
 
-Use the built-in `PayWithApplePayButton` view in SwiftUI.
+Use the built-in `PayWithApplePayButton` view in SwiftUI. Use Apple-provided
+button APIs for any control labeled Apple Pay; custom buttons must not include
+the Apple Pay logo or "Apple Pay" text.
 
 ```swift
 import SwiftUI
@@ -86,11 +97,14 @@ button.cornerRadius = 12
 button.addTarget(self, action: #selector(startPayment), for: .touchUpInside)
 ```
 
-**Button types:** `.buy`, `.setUp`, `.inStore`, `.donate`, `.checkout`, `.book`, `.subscribe`, `.reload`, `.addMoney`, `.topUp`, `.order`, `.rent`, `.support`, `.contribute`, `.tip`
+**Button types:** `.plain`, `.buy`, `.setUp`, `.inStore`, `.donate`,
+`.checkout`, `.continue`, `.book`, `.subscribe`, `.reload`, `.addMoney`,
+`.topUp`, `.order`, `.rent`, `.support`, `.contribute`, `.tip`
 
 ## Creating a Payment Request
 
 Build a `PKPaymentRequest` with your merchant details and the items being purchased.
+PassKit amount APIs take `NSDecimalNumber`, not `Double`.
 
 ```swift
 func createPaymentRequest() -> PKPaymentRequest {
@@ -102,31 +116,54 @@ func createPaymentRequest() -> PKPaymentRequest {
     request.merchantCapabilities = .threeDSecure
 
     request.paymentSummaryItems = [
-        PKPaymentSummaryItem(label: "Widget", amount: 9.99),
-        PKPaymentSummaryItem(label: "Shipping", amount: 4.99),
-        PKPaymentSummaryItem(label: "My Store", amount: 14.98) // Total (last item)
+        PKPaymentSummaryItem(
+            label: "Widget",
+            amount: NSDecimalNumber(string: "9.99")
+        ),
+        PKPaymentSummaryItem(
+            label: "Shipping",
+            amount: NSDecimalNumber(string: "4.99")
+        ),
+        PKPaymentSummaryItem(
+            label: "My Store",
+            amount: NSDecimalNumber(string: "14.98")
+        ) // Total
     ]
 
     return request
 }
 ```
 
-The **last item** in `paymentSummaryItems` is treated as the total and its label appears as the merchant name on the payment sheet.
+The **last item** in `paymentSummaryItems` is treated as the total and its label
+appears in the Pay line on the payment sheet.
 
 ### Requesting Shipping and Contact Info
 
+Request only the contact fields needed to price, fulfill, or legally process the
+order.
+Collect required product choices, optional notes, per-item shipping destinations,
+and pickup locations before the Apple Pay button when the payment sheet cannot
+collect them accurately.
+
 ```swift
 request.requiredShippingContactFields = [.postalAddress, .emailAddress, .name]
 request.requiredBillingContactFields = [.postalAddress]
 
-request.shippingMethods = [
-    PKShippingMethod(label: "Standard", amount: 4.99),
-    PKShippingMethod(label: "Express", amount: 9.99),
-]
-request.shippingMethods?[0].identifier = "standard"
-request.shippingMethods?[0].detail = "5-7 business days"
-request.shippingMethods?[1].identifier = "express"
-request.shippingMethods?[1].detail = "1-2 business days"
+let standard = PKShippingMethod(
+    label: "Standard",
+    amount: NSDecimalNumber(string: "4.99")
+)
+standard.identifier = "standard"
+standard.detail = "5-7 business days"
+
+let express = PKShippingMethod(
+    label: "Express",
+    amount: NSDecimalNumber(string: "9.99")
+)
+express.identifier = "express"
+express.detail = "1-2 business days"
+
+request.shippingMethods = [standard, express]
 
 request.shippingType = .shipping // .delivery, .storePickup, .servicePickup
 ```
@@ -149,15 +186,25 @@ Query available networks at runtime with `PKPaymentRequest.availableNetworks()`.
 
 ## Presenting the Payment Sheet
 
-Use `PKPaymentAuthorizationController` (works in both SwiftUI and UIKit, no view controller needed).
+Use `PKPaymentAuthorizationController` (works in both SwiftUI and UIKit, no view controller needed). The controller's delegate is weak, so retain the controller for the life of the sheet.
 
 ```swift
-@MainActor
-func startPayment() {
-    let request = createPaymentRequest()
-    let controller = PKPaymentAuthorizationController(paymentRequest: request)
-    controller.delegate = self
-    controller.present()
+final class CheckoutCoordinator: NSObject {
+    private var paymentController: PKPaymentAuthorizationController?
+
+    @MainActor
+    func startPayment() {
+        let controller = PKPaymentAuthorizationController(
+            paymentRequest: createPaymentRequest()
+        )
+        paymentController = controller
+        controller.delegate = self
+        controller.present { [weak self] presented in
+            if !presented {
+                self?.paymentController = nil
+            }
+        }
+    }
 }
 ```
 
@@ -186,7 +233,9 @@ extension CheckoutCoordinator: PKPaymentAuthorizationControllerDelegate {
     func paymentAuthorizationControllerDidFinish(
         _ controller: PKPaymentAuthorizationController
     ) {
-        controller.dismiss()
+        controller.dismiss { [weak self] in
+            self?.paymentController = nil
+        }
     }
 }
 ```
@@ -209,50 +258,53 @@ func paymentAuthorizationController(
 
 ### Adding a Pass to Wallet
 
-Load a `.pkpass` file and present `PKAddPassesViewController`.
+Load signed `.pkpass` data, verify the device can add passes, then present
+`PKAddPassesViewController` when you want the user to review the pass before
+adding it. `PKPass(data:)` expects signed pass data and can throw invalid-data
+or invalid-signature errors. Name `invalid-data` and `invalid-signature`
+failures explicitly instead of hiding them behind a bare `try?` in review
+guidance.
 
 ```swift
 func addPassToWallet(data: Data) {
-    guard let pass = try? PKPass(data: data) else { return }
+    guard PKAddPassesViewController.canAddPasses() else {
+        return
+    }
 
-    if let addController = PKAddPassesViewController(pass: pass) {
+    do {
+        let pass = try PKPass(data: data)
+        guard let addController = PKAddPassesViewController(pass: pass) else {
+            return
+        }
         addController.delegate = self
         present(addController, animated: true)
+    } catch {
+        // Signed pass data is invalid or the signature cannot be validated.
+        showRecoverablePassError(error)
     }
 }
 ```
 
 ### SwiftUI Wallet Button
 
+Use `AddPassToWalletButton` as the SwiftUI equivalent to `PKAddPassButton`.
+
 ```swift
 import PassKit
 import SwiftUI
 
 struct AddPassButton: View {
     let passData: Data
+    @State private var addedToWallet = false
 
     var body: some View {
-        Button("Add to Wallet") {
-            addPass()
-        }
-    }
-
-    func addPass() {
-        guard let pass = try? PKPass(data: passData) else { return }
-        let library = PKPassLibrary()
-        library.addPasses([pass]) { status in
-            switch status {
-            case .shouldReviewPasses:
-                // Present review UI
-                break
-            case .didAddPasses:
-                // Passes added successfully
-                break
-            case .didCancelAddPasses:
-                break
-            @unknown default:
-                break
+        if PKAddPassesViewController.canAddPasses(),
+           let pass = try? PKPass(data: passData) {
+            AddPassToWalletButton([pass]) { added in
+                addedToWallet = added
             }
+            .addPassToWalletButtonStyle(.blackOutline)
+            .frame(width: 250, height: 50)
         }
     }
 }
@@ -260,7 +312,14 @@ struct AddPassButton: View {
 
 ## Checking Pass Library
 
-Use `PKPassLibrary` to inspect and manage passes the user already has.
+Use `PKPassLibrary` to inspect and manage passes the user already has. Check
+`PKPassLibrary.isPassLibraryAvailable()` before pass-library operations, but use
+`PKAddPassesViewController.canAddPasses()` to decide whether the device can add
+passes. `passes()` only returns passes your app can access through its
+entitlements. When replacing an existing pass, check the Boolean result from
+`replacePass(with:)` and handle failure. For signed pass bundle construction,
+update web services, and `replacePass(with:)`, read
+[references/wallet-passes.md](references/wallet-passes.md).
 
 ```swift
 let library = PKPassLibrary()
@@ -279,9 +338,10 @@ guard PKPassLibrary.isPassLibraryAvailable() else { return }
 
 ### DON'T: Use StoreKit for physical goods
 
-Apple Pay (PassKit) is for **physical goods and services**. StoreKit is for digital
-content, subscriptions, and in-app purchases. Using the wrong framework leads to
-App Review rejection.
+Apple Pay (PassKit) is for **physical goods, real-world services, donations, and
+eligible recurring payments**. StoreKit is for virtual goods, app features, and
+digital-content subscriptions. Using the wrong framework leads to App Review
+rejection.
 
 ```swift
 // WRONG: Using StoreKit to sell a physical product
@@ -290,8 +350,8 @@ let product = try await Product.products(for: ["com.example.tshirt"])
 // CORRECT: Use Apple Pay for physical goods
 let request = PKPaymentRequest()
 request.paymentSummaryItems = [
-    PKPaymentSummaryItem(label: "T-Shirt", amount: 29.99),
-    PKPaymentSummaryItem(label: "My Store", amount: 29.99)
+    PKPaymentSummaryItem(label: "T-Shirt", amount: NSDecimalNumber(string: "29.99")),
+    PKPaymentSummaryItem(label: "My Store", amount: NSDecimalNumber(string: "29.99"))
 ]
 ```
 
@@ -316,22 +376,36 @@ enum PaymentConfig {
 
 ### DON'T: Forget the total line item
 
-The last item in `paymentSummaryItems` is the total row. If you omit it, the
-payment sheet shows no merchant name or total.
+The last item in `paymentSummaryItems` is the total row. If you only list line
+items, the payment sheet uses the final line item as the Pay line instead of
+your business name.
 
 ```swift
 // WRONG: No total item
 request.paymentSummaryItems = [
-    PKPaymentSummaryItem(label: "Widget", amount: 9.99)
+    PKPaymentSummaryItem(label: "Widget", amount: NSDecimalNumber(string: "9.99"))
 ]
 
 // CORRECT: Last item is the total with your merchant name
 request.paymentSummaryItems = [
-    PKPaymentSummaryItem(label: "Widget", amount: 9.99),
-    PKPaymentSummaryItem(label: "My Store", amount: 9.99) // Total
+    PKPaymentSummaryItem(label: "Widget", amount: NSDecimalNumber(string: "9.99")),
+    PKPaymentSummaryItem(
+        label: "My Store",
+        amount: NSDecimalNumber(string: "9.99")
+    ) // Total
 ]
 ```
 
+### DON'T: Use binary floating-point values for money
+
+```swift
+// WRONG: PassKit amounts are NSDecimalNumber values
+PKPaymentSummaryItem(label: "Widget", amount: 9.99)
+
+// CORRECT: Construct decimal amounts explicitly
+PKPaymentSummaryItem(label: "Widget", amount: NSDecimalNumber(string: "9.99"))
+```
+
 ### DON'T: Skip the canMakePayments check
 
 ```swift
@@ -351,6 +425,9 @@ if PKPaymentAuthorizationController.canMakePayments(
 
 ### DON'T: Dismiss the controller before completing authorization
 
+Keep the authorization controller retained while presented, because its delegate
+property is weak. Dismiss only after the sheet finishes.
+
 ```swift
 // WRONG: Dismissing inside didAuthorizePayment
 func paymentAuthorizationController(
@@ -366,7 +443,9 @@ func paymentAuthorizationController(
 func paymentAuthorizationControllerDidFinish(
     _ controller: PKPaymentAuthorizationController
 ) {
-    controller.dismiss()
+    controller.dismiss { [weak self] in
+        self?.paymentController = nil
+    }
 }
 ```
 
@@ -375,24 +454,35 @@ func paymentAuthorizationControllerDidFinish(
 - [ ] Apple Pay capability enabled and merchant ID configured in Developer portal
 - [ ] Payment Processing Certificate generated and installed
 - [ ] `canMakePayments(usingNetworks:)` checked before showing Apple Pay button
+- [ ] Apple Pay is prominent wherever active-card availability is checked
+- [ ] Product choices, optional details, and complex shipping choices collected before payment sheet
 - [ ] Last item in `paymentSummaryItems` is the total with merchant display name
+- [ ] Payment summary and token-context amounts use `NSDecimalNumber`
 - [ ] Payment token sent to server for processing (never decoded client-side)
+- [ ] `PKPaymentAuthorizationController` retained while presented and cleared after finish
 - [ ] `paymentAuthorizationControllerDidFinish` dismisses the controller
 - [ ] Shipping method changes recalculate totals via delegate callback
-- [ ] StoreKit used for digital goods; Apple Pay used for physical goods
+- [ ] StoreKit used for virtual goods/digital content; Apple Pay used for physical goods, services, donations, and eligible recurring payments
 - [ ] Wallet passes loaded from signed `.pkpass` bundles
-- [ ] `PKPassLibrary.isPassLibraryAvailable()` checked before pass operations
+- [ ] `PKPass(data:)` invalid-data and invalid-signature failures surfaced
+- [ ] `PKPassLibrary.isPassLibraryAvailable()` used for pass operations, not add-pass capability
+- [ ] `PKAddPassesViewController.canAddPasses()` checked before add-pass UI
+- [ ] `PKPassLibrary.replacePass(with:)` Boolean result checked when replacing a pass
 - [ ] Apple Pay button uses system-provided `PKPaymentButton` or `PayWithApplePayButton`
+- [ ] Add-to-Wallet UI uses system-provided `PKAddPassButton`, `AddPassToWalletButton`, or `PKAddPassesViewController`
 - [ ] Error states handled in authorization result (network failures, declined cards)
 
 ## References
 
-- Extended patterns (recurring payments, coupon codes, multi-merchant): `references/wallet-passes.md`
+- Extended patterns (recurring/deferred payments, coupon codes, multi-merchant, pass bundles, pass updates): [references/wallet-passes.md](references/wallet-passes.md)
 - [PassKit framework](https://sosumi.ai/documentation/passkit)
 - [PKPaymentRequest](https://sosumi.ai/documentation/passkit/pkpaymentrequest)
 - [PKPaymentAuthorizationController](https://sosumi.ai/documentation/passkit/pkpaymentauthorizationcontroller)
 - [PKPaymentButton](https://sosumi.ai/documentation/passkit/pkpaymentbutton)
+- [PayWithApplePayButton](https://sosumi.ai/documentation/passkit/paywithapplepaybutton)
+- [AddPassToWalletButton](https://sosumi.ai/documentation/passkit/addpasstowalletbutton)
 - [PKPass](https://sosumi.ai/documentation/passkit/pkpass)
 - [PKAddPassesViewController](https://sosumi.ai/documentation/passkit/pkaddpassesviewcontroller)
 - [PKPassLibrary](https://sosumi.ai/documentation/passkit/pkpasslibrary)
 - [PKPaymentNetwork](https://sosumi.ai/documentation/passkit/pkpaymentnetwork)
+- [Apple Pay HIG](https://sosumi.ai/design/human-interface-guidelines/apple-pay)

package/pipeline/skills/shared/external/passkit-wallet/evals/evals.json

@@ -0,0 +1,51 @@
+{
+  "skill_name": "passkit",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "I'm adding Apple Pay checkout to a SwiftUI store for physical products. Show the capability setup, availability check, Apple Pay button, PKPaymentRequest with shipping, payment presentation, and authorization delegate shape. Include App Review boundary notes for StoreKit.",
+      "expected_output": "A source-grounded PassKit checkout plan that uses Apple Pay for physical goods, builds a valid payment request, handles authorization through a retained controller/delegate, and keeps StoreKit for digital goods.",
+      "files": [],
+      "assertions": [
+        "States that Apple Pay capability, Merchant ID, payment processing certificate, and merchant entitlement must be configured.",
+        "Checks `PKPaymentAuthorizationController.canMakePayments()` and `canMakePayments(usingNetworks:capabilities:)` before presenting Apple Pay UI.",
+        "Uses system-provided `PayWithApplePayButton` or `PKPaymentButton` rather than a custom Apple Pay button.",
+        "Constructs payment summary items and shipping methods with `NSDecimalNumber`, not `Double` money literals.",
+        "Keeps the final `paymentSummaryItems` entry as the total Pay-line item with the merchant/business name.",
+        "Retains `PKPaymentAuthorizationController` while presented, assigns its weak delegate, and clears the retained controller after dismissal.",
+        "Sends `payment.token` or `payment.token.paymentData` to a payment processor/server and returns `PKPaymentAuthorizationResult` through the delegate handler.",
+        "Explains that StoreKit is for virtual goods, app features, and digital-content subscriptions while PassKit covers physical goods, real-world services, donations, and eligible recurring payments."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Review this Wallet pass plan: load a pkpass, show a normal SwiftUI Button that says Add to Wallet, use PKPassLibrary.isPassLibraryAvailable to decide if the device can add it, list all Wallet passes with passes(), and update the pass later with a new serial number. Fix it.",
+      "expected_output": "A correction-focused Wallet pass answer that uses system Add to Wallet UI, signed-pass checks, correct add-pass availability, pass-library access limits, and stable pass identifiers for updates.",
+      "files": [],
+      "assertions": [
+        "Replaces the custom SwiftUI button with `AddPassToWalletButton` or routes review flows through `PKAddPassesViewController`/`PKAddPassButton`.",
+        "Uses `PKAddPassesViewController.canAddPasses()` to decide whether the device can add passes.",
+        "Uses `PKPassLibrary.isPassLibraryAvailable()` only for pass-library operations, not add-pass capability.",
+        "Mentions that `PKPass(data:)` expects signed `.pkpass` data and can throw invalid-data or invalid-signature errors.",
+        "Explains that `PKPassLibrary.passes()` returns only passes the app can access through entitlements.",
+        "Preserves the same `passTypeIdentifier` and `serialNumber` when updating an existing pass.",
+        "Checks the Boolean result from `PKPassLibrary.replacePass(with:)` and handles failure."
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "I need advanced Apple Pay support for a travel marketplace: recurring service membership, coupon entry in the payment sheet, two end merchants that need separate tokens, and a hotel preauthorization charged later. Outline the PassKit APIs and gotchas without drifting into FinanceKit or StoreKit implementation.",
+      "expected_output": "An advanced PassKit outline using the optional request types and update callbacks correctly, with decimal amounts, management URLs, coupon update details, multi-token contexts, and sibling-skill boundaries.",
+      "files": [],
+      "assertions": [
+        "Uses `PKRecurringPaymentRequest` with `PKRecurringPaymentSummaryItem`, interval unit/count, billing agreement or management URL, and `request.recurringPaymentRequest`.",
+        "Notes that a `PKPaymentRequest` can set only one optional payment request type such as recurring, automatic reload, deferred, Apple Pay Later availability, or multi-token contexts.",
+        "Enables coupon entry with `supportsCouponCode` and handles `paymentAuthorizationController(_:didChangeCouponCode:handler:)`.",
+        "Creates `PKPaymentRequestCouponCodeUpdate(errors:paymentSummaryItems:shippingMethods:)`, including shipping methods.",
+        "Uses `PKPaymentTokenContext` entries with merchant identifier, external identifier, merchant name/domain, and `NSDecimalNumber` amounts for multi-merchant tokens.",
+        "Uses `PKDeferredPaymentRequest` with `PKDeferredPaymentSummaryItem`, deferred date or cancellation date details, and a management URL.",
+        "Keeps FinanceKit financial-data access and StoreKit digital purchase implementation outside the PassKit answer."
+      ]
+    }
+  ]
+}