@mmerterden/multi-agent-pipeline 20.8.0 → 20.8.2

package/pipeline/skills/shared/external/swift-security/references/keychain-fundamentals.md

@@ -18,7 +18,7 @@ and Best Practices".
 - [Reading](#reading)
 - [One Place That Builds Queries](#one-place-that-builds-queries)
 - [OSStatus Codes](#osstatus-codes)
-- [An Actor Around the Keychain (iOS 17+ / macOS 14+)](#an-actor-around-the-keychain-ios-17--macos-14)
+- [An Actor Around the Keychain (iOS 13+ / macOS 10.15+)](#an-actor-around-the-keychain-ios-13--macos-1015)
 - [Performance](#performance)
 - [macOS: Two Keychains (TN3137)](#macos-two-keychains-tn3137)
 - [Accessibility at a Glance](#accessibility-at-a-glance)
@@ -85,8 +85,11 @@ Internet passwords are identified by account, server, protocol, authentication
 type, port, path, security domain, access group and synchronizable. See
 [keychain-item-classes.md](keychain-item-classes.md) for every class.
 
-`SecItemUpdate` cannot change `kSecAttrAccount` or `kSecClass`. To rename an
-account or change class, delete the old item and add a new one.
+`SecItemUpdate` cannot change `kSecClass`: the class belongs to the query,
+and the attributes dictionary accepts only real keychain attributes. To change
+class, delete the old item and add a new one. A primary-key attribute such as
+`kSecAttrAccount` can be updated; the update fails with `errSecDuplicateItem`
+only when another item already has the resulting primary key.
 
 ## Saving: Add, Then Update on Duplicate
 
@@ -257,7 +260,7 @@ its merits:
 | -128 | `errSecUserCanceled` | The user dismissed the prompt; tell the UI. |
 | -25293 | `errSecAuthFailed` | Authentication failed or the protected item is no longer usable. |
 | -50 | `errSecParam` | A programming error in the dictionary; fix the query. |
-| -25244 | `errSecNoSuchAttr` | The attribute is not supported (seen on the data protection keychain). |
+| -25303 | `errSecNoSuchAttr` | The attribute is not supported (seen on the data protection keychain). |
 
 ```swift
 struct KeychainError: Error, CustomStringConvertible {
@@ -272,7 +275,7 @@ struct KeychainError: Error, CustomStringConvertible {
 Logs may record the shape of a query (class, service, which flags were set)
 and the status code. They never record `kSecValueData`, tokens or key bytes.
 
-## An Actor Around the Keychain (iOS 17+ / macOS 14+)
+## An Actor Around the Keychain (iOS 13+ / macOS 10.15+)
 
 Reads of biometric-protected items wait for the user and can take several
 seconds (WWDC 2014 Session 711). Doing that on the main actor freezes the UI.
@@ -381,7 +384,8 @@ Why an actor rather than a queue:
 | `Sendable` | Enforced | Annotate `@Sendable` by hand |
 | Swift 6 | Native | Needs care to pass strict checking |
 
-For iOS 13 through 16, a private serial queue does the same job:
+In completion-handler code that has not moved to Swift concurrency, a private
+serial queue does the same job:
 
 ```swift
 final class LegacySecretStore {
@@ -450,7 +454,7 @@ func macSafe(_ query: [CFString: Any]) -> [CFString: Any] {
 
 When a macOS keychain bug appears, first confirm which backend the call went
 to. An attribute the file-based keychain quietly drops will produce
-`errSecNoSuchAttr` (-25244) on the data protection keychain.
+`errSecNoSuchAttr` (-25303) on the data protection keychain.
 
 ## Accessibility at a Glance
 
@@ -477,8 +481,8 @@ is a safe default for foreground use. The actor above defaults to
 2. Saves fall back to `SecItemUpdate` on -25299.
 3. Every `SecItemCopyMatching` sets at least one `kSecReturn*` key.
 4. The cast of the `CFTypeRef` result matches the return keys and match limit.
-5. No SecItem call runs on `@MainActor` (actor on iOS 17+, serial queue on
-   iOS 13 to 16).
+5. No SecItem call runs on `@MainActor` (an actor, available from iOS 13, or
+   a private serial queue in completion-handler code).
 6. Add, query and update dictionaries are built fresh for each call.
 7. Keys are `kSec*` constants, not string literals.
 8. Queries are specific: service and account for generic passwords,

package/pipeline/skills/shared/external/swift-security/references/secure-enclave.md

@@ -321,12 +321,13 @@ func pqRoundTrip() throws -> Bool {
 ```
 
 Transport needs no work: in iOS 26, `URLSession` and `Network.framework`
-negotiate quantum-secure TLS 1.3 with X-Wing (ML-KEM768 combined with X25519)
-on their own, and CloudKit, push notifications and iCloud Private Relay already
-use it. For an app's own end-to-end encryption, prefer a hybrid of
-post-quantum and classical algorithms, such as the `XWingMLKEM768X25519` KEM in
-HPKE; an `SecureEnclave.MLKEM768.PrivateKey` performs encapsulation and
-decapsulation inside the hardware. The full CryptoKit catalog is in
+negotiate quantum-secure TLS 1.3 on their own, offering the hybrid
+`X25519MLKEM768` key-exchange group, and CloudKit, push notifications and
+iCloud Private Relay already use it. For an app's own end-to-end encryption,
+prefer a hybrid of post-quantum and classical algorithms, such as the CryptoKit
+X-Wing KEM (`XWingMLKEM768X25519`) in HPKE; an
+`SecureEnclave.MLKEM768.PrivateKey` performs encapsulation and decapsulation
+inside the hardware. The full CryptoKit catalog is in
 [cryptokit-public-key.md](cryptokit-public-key.md).
 
 | Release | Enclave-related change |

package/pipeline/skills/shared/external/swift-testing/SKILL.md

@@ -218,7 +218,7 @@ API you correct.
 | API | Needs |
 |-----|-------|
 | Exit tests (`processExitsWith:`) | Swift 6.2, Xcode 26.0; not iOS, tvOS, watchOS |
-| Capture lists in exit tests | Swift 6.3 compiler; captured values must be `Sendable` and `Codable` |
+| Capture lists in exit tests | Compiles with the Swift 6.3.1 compiler (Xcode 26.4); earlier compilers not checked. Captured values must be `Sendable` and `Codable` |
 | `Test.cancel(_:)`, `Issue.record(_:severity:)`, image attachments | Swift 6.3, Xcode 26.4 |
 
 ```swift
@@ -230,9 +230,12 @@ API you correct.
 }
 ```
 
-Give each captured value an explicit type (`[name = name as Type]`). A bare
-`[status]` fails to compile with "Type of captured value is ambiguous",
-because the macro cannot infer the type on its own.
+Give each captured value an explicit type (`[name = name as Type]`). With the
+Swift 6.3.1 compiler a bare `[status]` fails with "Type of captured value
+'status' is ambiguous", a captured value that is not `Codable` fails with "must
+conform to 'Sendable' and 'Codable'", and a closure that reads `status` with no
+capture list fails with "a C function pointer cannot be formed from a closure
+that captures context".
 
 A test that calls `Test.cancel(_:)` must be `throws` or `async throws`.
 
@@ -241,7 +244,7 @@ A test that calls `Test.cancel(_:)` must be `throws` or `async throws`.
 | Found | Replace with |
 |-------|--------------|
 | `#expect(exitsWith:)` | `await #expect(processExitsWith: .failure) { ... }`. In an iOS app target, test the logic behind a smaller API that does not exit, or move the exit test to a supported host or tool target. |
-| Exit-test closure reading outer values with no capture list | An explicit, typed capture list (`[code = code as Int32]`); Swift 6.3 compiler; values `Sendable` and `Codable` |
+| Exit-test closure reading outer values with no capture list | An explicit, typed capture list (`[code = code as Int32]`); verified with Swift 6.3.1; values `Sendable` and `Codable` |
 | `Test.cancel()` in a test that is not throwing | Mark the test `async throws` and call `try Test.cancel("reason")` |
 | A warning that should not fail the run | `Issue.record("message", severity: .warning)`: reported, test still passes; Swift 6.3, Xcode 26.4 |
 | `Attachment(image, named:).record()` | `Attachment.record(image, named: "...", as: .png)`; accepts `UIImage`, `CGImage`, `CIImage`, `NSImage`; Swift 6.3, Xcode 26.4 |

package/pipeline/skills/shared/external/swift-testing/evals/evals.json

@@ -23,7 +23,7 @@
       "assertions": [
         "Replaces exitsWith: with await #expect(processExitsWith: .failure).",
         "States that exit tests need Swift 6.2 and Xcode 26.0 and do not run on iOS, tvOS or watchOS, and suggests testing the non-exiting logic in the app target.",
-        "Adds an explicit capture list for badCode, requiring the Swift 6.3 compiler and Sendable plus Codable values.",
+        "Adds an explicit, typed capture list for badCode, notes it was verified with the Swift 6.3.1 compiler, and requires Sendable plus Codable values.",
         "Makes the cancelling test async throws (or throws) and calls try Test.cancel.",
         "Uses Issue.record with severity: .warning and names the Swift 6.3 and Xcode 26.4 gate.",
         "Uses Attachment.record(chartImage, named:, as: .png) and names the Swift 6.3 and Xcode 26.4 gate."

package/pipeline/skills/shared/external/swift-testing/references/testing-advanced.md

@@ -52,7 +52,8 @@ and reports it as cancelled: neither passed nor failed.
 ## Capturing Values in Exit Tests
 
 ST-0012 lets an exit test's closure capture values from the surrounding scope.
-It needs the Swift 6.3 compiler. Exit tests themselves arrived in Swift 6.2
+It compiles with the Swift 6.3.1 compiler in Xcode 26.4; earlier compilers were
+not checked. Exit tests themselves arrived in Swift 6.2
 (Xcode 26.0) through the `processExitsWith:` macros. Captured values must be
 `Sendable` and `Codable`, because they are sent to the child process.
 
@@ -101,7 +102,7 @@ import UIKit
 |---------|---------|
 | Attachments of standard values | Swift 6.2, Xcode 26.0 |
 | Exit tests with `processExitsWith:` | Swift 6.2, Xcode 26.0; macOS, Linux, FreeBSD, OpenBSD, Windows |
-| Capture lists in exit tests | Swift 6.3 compiler |
+| Capture lists in exit tests | Verified with the Swift 6.3.1 compiler (Xcode 26.4) |
 | `Issue.record(_:severity:)`, `Test.cancel(_:)`, image attachments | Swift 6.3, Xcode 26.4 |
 
 iOS, tvOS and watchOS have no exit tests. Put the exiting behaviour behind a

package/pipeline/skills/shared/external/swiftdata/SKILL.md

@@ -35,9 +35,11 @@ shipped without a migration plan.
 
 ## Defining models
 
-`@Model` only applies to classes. It adds conformance to `PersistentModel`,
-`Observable` and `Sendable`, so a model needs reference semantics and a
-designated initializer.
+`@Model` only applies to classes. It adds conformance to `PersistentModel`
+(which refines `Observable`, `Hashable` and `Identifiable`), so a model needs
+reference semantics and a designated initializer. Model instances are not
+`Sendable`: to hand a model to another actor, pass its `PersistentIdentifier`
+(which is `Sendable`) and fetch it again from that actor's context.
 
 ```swift
 import SwiftData

package/pipeline/skills/shared/external/swiftui-navigation/SKILL.md

@@ -188,19 +188,24 @@ struct RootTabs: View {
 The custom binding sends every change through `select`, so a tab like
 "New" can run an action instead of becoming the selected tab.
 
-### iOS 26 additions
+### Tab APIs from iOS 18 and iOS 26
 
-- `Tab(role: .search)` turns the tab bar into a search field while that tab is
-  active.
-- `.tabBarMinimizeBehavior(_:)` with `.onScrollDown`, `.onScrollUp` or `.never`.
-  iPhone only.
+From iOS 18 (macOS 15):
+
+- `Tab(role: .search)` marks the search tab; the iOS 26 tab bar shows it as a
+  search field while that tab is active.
 - `.tabViewSidebarHeader { }` and `.tabViewSidebarFooter { }` customise the
   sidebar on iPadOS and macOS.
-- `.tabViewBottomAccessory { }` pins a view just above the tab bar, such as a
-  mini player.
 - `TabSection` collects tabs under a sidebar heading; mark it with
   `.tabPlacement(.sidebarOnly)` to keep it out of the compact bar.
 
+From iOS 26 only:
+
+- `.tabBarMinimizeBehavior(_:)` with `.onScrollDown`, `.onScrollUp` or `.never`.
+  iPhone only.
+- `.tabViewBottomAccessory { }` pins a view just above the tab bar, such as a
+  mini player.
+
 More in [references/tabview.md](references/tabview.md).
 
 ## Deep links
@@ -259,7 +264,10 @@ Details, AASA format and scheme parsing: [references/deeplinks.md](references/de
 - Driving a model-backed sheet with `.sheet(isPresented:)` instead of
   `.sheet(item:)`.
 - Putting views in the path. The path holds small `Hashable` route values.
-- Holding an `@Observable` router as a property of another `@Observable` object.
+- Writing `NavigationStack(path: $router.path)` where `router` is a plain `let`
+  or comes from `@Environment`. That gives no binding and does not compile;
+  declare the property `@Bindable var router: Router`, or add
+  `@Bindable var router = router` inside `body`.
 - Building tabs with the older `.tabItem { }` instead of `Tab(value:)` with
   `TabView(selection:)`.
 - Expecting `tabBarMinimizeBehavior` to do anything on iPad. It is iPhone only.
@@ -285,5 +293,5 @@ Details, AASA format and scheme parsing: [references/deeplinks.md](references/de
 
 - [references/navigationstack.md](references/navigationstack.md): routers, per-tab stacks, centralised destinations, data-driven tabs
 - [references/sheets.md](references/sheets.md): enum sheet routing, sizing, dismissal confirmation
-- [references/tabview.md](references/tabview.md): tab architecture, custom selection binding, dynamic tabs, iOS 26 tab API
+- [references/tabview.md](references/tabview.md): tab architecture, custom selection binding, dynamic tabs, the iOS 18 and iOS 26 tab APIs
 - [references/deeplinks.md](references/deeplinks.md): router URL handling, universal links and AASA, custom schemes, Handoff

package/pipeline/skills/shared/external/swiftui-navigation/references/navigationstack.md

@@ -172,5 +172,7 @@ struct DynamicTabs: View {
 - A path shared across tabs, unless you really want one global history.
 - Route identifiers that are not stable or not `Hashable`.
 - View instances stored in the path instead of route data.
-- A router stored inside another `@Observable` object; keep it standalone to
-  avoid nested observation.
+- A router passed as a plain `let` or read from `@Environment` and then used as
+  `$router.path`: no binding exists without `@Bindable`, so the stack view needs
+  `@Bindable var router: Router` (as `ExploreStack` has) or a local
+  `@Bindable var router = router` in `body`.

package/pipeline/skills/shared/external/swiftui-navigation/references/tabview.md

@@ -107,7 +107,7 @@ enum AppTab: Hashable, Identifiable {
 }
 ```
 
-## iOS 26 tab API
+## Tab APIs from iOS 18 and iOS 26
 
 ```swift
 TabView {
@@ -121,20 +121,27 @@ TabView {
 .tabViewSidebarBottomBar { SettingsButton() }
 ```
 
-- `TabBarMinimizeBehavior`: `.automatic` (decided by context), `.onScrollDown`,
-  `.onScrollUp` and `.never`. The two scroll behaviours apply on iPhone only.
-- `Tab(role: .search)` replaces the bar with a search field while that tab is
-  active.
+iOS 18 (macOS 15, visionOS 2):
+
+- `Tab(role: .search)` marks the search tab; the iOS 26 tab bar replaces the bar
+  with a search field while that tab is active.
 - Sidebar customisation: `.tabViewSidebarHeader { }`,
   `.tabViewSidebarFooter { }` and `.tabViewSidebarBottomBar { }`.
+- `TabSection` and `.tabPlacement(_:)`.
+
+iOS 26 only:
+
+- `TabBarMinimizeBehavior`: `.automatic` (decided by context), `.onScrollDown`,
+  `.onScrollUp` and `.never`. The two scroll behaviours apply on iPhone only.
 - `.tabViewBottomAccessory { }` shows content just above the tab bar; its
   placement is described by `TabViewBottomAccessoryPlacement`.
 
+The example mixes both groups, so as written it needs iOS 26.
+
 ## Pitfalls
 
 - A view model per tab. Keep state local to views or in shared `@Observable`
   services.
-- `@Observable` objects nested inside each other.
 - An `AppTab.id` that changes between launches; dynamic cases must hash on a
   stable identifier.
 - Special tabs such as compose that change the selection.

package/pipeline/skills/shared/external/vision-framework/SKILL.md

@@ -44,7 +44,9 @@ optional.
 
 Most requests are value types. Requests that must remember earlier frames are
 `final class` types conforming to `StatefulRequest`: `TrackObjectRequest`,
-`TrackRectangleRequest`, `TrackOpticalFlowRequest`, `DetectTrajectoriesRequest`,
+`TrackRectangleRequest`, `TrackOpticalFlowRequest`,
+`TrackTranslationalImageRegistrationRequest`,
+`TrackHomographicImageRegistrationRequest`, `DetectTrajectoriesRequest`,
 `DetectHumanBodyPose3DRequest` and `GeneratePersonSegmentationRequest`. Keep one
 instance alive for the whole sequence.
 

package/pipeline/skills/shared/external/weatherkit/SKILL.md

@@ -68,8 +68,9 @@ headline = "\(now.temperature.formatted()), \(now.condition.description)"
 
 ### Hourly
 
-By default the hourly forecast covers 25 consecutive hours starting with the
-current hour. `hourlyForecast` is a `Forecast<HourWeather>`:
+At the time of writing, Apple's documentation says the default hourly forecast
+covers 25 consecutive hours starting with the current hour; read the count from
+the result rather than hard-coding it. `hourlyForecast` is a `Forecast<HourWeather>`:
 
 ```swift
 let timeline = report.hourlyForecast.map { slot in
@@ -79,7 +80,9 @@ let timeline = report.hourlyForecast.map { slot in
 
 ### Daily
 
-By default the daily forecast covers 10 consecutive days starting today.
+At the time of writing, Apple's documentation says the default daily forecast
+covers 10 consecutive days starting today; again, read the count from the
+result.
 `dailyForecast` is a `Forecast<DayWeather>`:
 
 ```swift
@@ -145,8 +148,8 @@ if let nextHour = try await forecaster.weather(for: site, including: .minute) {
 | Query | Result type | Notes |
 | --- | --- | --- |
 | `.current` | `CurrentWeather` | |
-| `.hourly` | `Forecast<HourWeather>` | 25 hours from now |
-| `.daily` | `Forecast<DayWeather>` | 10 days from today |
+| `.hourly` | `Forecast<HourWeather>` | Default span per Apple's docs: 25 hours from now |
+| `.daily` | `Forecast<DayWeather>` | Default span per Apple's docs: 10 days from today |
 | `.minute` | `Forecast<MinuteWeather>?` | `nil` where unsupported |
 | `.alerts` | `[WeatherAlert]?` | `nil` where unsupported |
 | `.availability` | `WeatherAvailability` | Which region-limited datasets exist here |

package/pipeline/skills/shared/external/widgetkit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: widgetkit
-description: "WidgetKit and ActivityKit surfaces on iOS 26+: timeline-driven widgets for the Home Screen, the Lock Screen and StandBy, interactive widgets using Button or Toggle with AppIntent actions, Live Activities and their Dynamic Island layouts (compact, expanded, minimal), Control Center controls with ControlWidgetButton or ControlWidgetToggle, families, deep links, the refresh budget, reloads triggered by push, Liquid Glass accented rendering, extension setup, App Groups and entitlements. Use when implementing, reviewing or improving widgets, Live Activities or controls."
+description: "WidgetKit surfaces on iOS 26+: timeline-driven widgets for the Home Screen, the Lock Screen and StandBy, interactive widgets using Button or Toggle with AppIntent actions, widget views for a Live Activity (Dynamic Island compact, expanded, minimal), Control Center controls with ControlWidgetButton or ControlWidgetToggle, families, deep links, the refresh budget, push reloads, accented rendering, extension setup, App Groups. Use when implementing or reviewing widgets, Live Activity views or controls. Not for Live Activity lifecycle or pushes (live-activities)."
 metadata:
   source: multi-agent-pipeline
 ---
@@ -13,7 +13,9 @@ surface WidgetKit and ActivityKit draw on: the Home Screen, the Lock Screen,
 Live Activities and the Dynamic Island, Control Center and StandBy.
 
 Related skills: `app-intents` for intent and entity design beyond what a widget
-needs, `live-activities` for deeper ActivityKit push contracts.
+needs, `live-activities` for the Live Activity lifecycle (request, update, end),
+push tokens and ActivityKit push contracts. This skill covers the widget views a
+Live Activity renders.
 
 Longer examples are in [the advanced reference](references/widgetkit-advanced.md).
 
@@ -300,14 +302,20 @@ on its side. Read `@Environment(\.widgetLocation)` to tell where you are drawn:
 - Budget: roughly 40 to 70 refreshes a day, with entries 5 minutes apart or more.
   For countdowns use `Text(timerInterval:countsDown:)` instead of one entry per tick.
 
-## iOS 26 Additions
+## iOS 18 Additions
 
 - `WidgetAccentedRenderingMode` (`.accented`, `.accentedDesaturated`,
-  `.desaturated`, `.fullColor`) controls how images adapt to Liquid Glass tinting.
+  `.desaturated`, `.fullColor`), applied with `.widgetAccentedRenderingMode(_:)`,
+  controls how images adapt to accented (tinted) rendering. Available from
+  iOS 18, macOS 15 and watchOS 11; on visionOS from 26.
+- `ControlPushHandler.pushTokensDidChange(controls:)` gives a push token per
+  control; an APNs push to it reloads the control.
+
+## iOS 26 Additions
+
 - `WidgetPushHandler.pushTokenDidChange(_:widgets:)` gives you a token to send to
-  your server; an APNs push to it reloads the widget. `ControlPushHandler` does
-  the same for controls. See
-  [Reloading timelines by push](references/widgetkit-advanced.md#reloading-timelines-by-push-ios-26-and-later).
+  your server; an APNs push to it reloads the widget. See
+  [Reloading timelines by push](references/widgetkit-advanced.md#reloading-timelines-by-push).
 - `.systemSmall` widgets render in CarPlay from iOS 26. Keep them readable at a
   glance so a driver is never pulled into detail.
 

package/pipeline/skills/shared/external/widgetkit/references/widgetkit-advanced.md

@@ -6,7 +6,7 @@ heading says otherwise.
 ## Contents
 
 - [Timeline Strategies](#timeline-strategies)
-- [Reloading timelines by push (iOS 26 and later)](#reloading-timelines-by-push-ios-26-and-later)
+- [Reloading timelines by push](#reloading-timelines-by-push)
 - [Deep Links and Widget URLs](#deep-links-and-widget-urls)
 - [User-configurable widgets through App Intents](#user-configurable-widgets-through-app-intents)
 - [Multiple Widget Support](#multiple-widget-support)
@@ -75,9 +75,10 @@ cost budget.
 - A widget run from Xcode's debugger has no refresh limit, so budget problems
   only show up outside the debugger.
 
-## Reloading timelines by push (iOS 26 and later)
+## Reloading timelines by push
 
-A `WidgetPushHandler` receives a token for APNs. Send it to your server.
+From iOS 26, a `WidgetPushHandler` receives a token for APNs. Send it to your
+server.
 
 ```swift
 struct ScoreboardPushHandler: WidgetPushHandler {
@@ -99,8 +100,9 @@ func hexString(_ bytes: Data) -> String {
 When the server sends an APNs push addressed to that token, the system calls
 `getTimeline` or `timeline(for:in:)` again.
 
-Controls have their own handler that receives every control at once, as
-`ControlInfo` values; each carries its token in an optional `pushInfo`:
+Controls have their own handler, available from iOS 18, that receives every
+control at once, as `ControlInfo` values; each carries its token in an optional
+`pushInfo`:
 
 ```swift
 struct GaragePushHandler: ControlPushHandler {
@@ -478,7 +480,7 @@ Task {
 }
 ```
 
-From iOS 26 a broadcast channel works too: `pushType: .channel("ferry-route-12")`.
+From iOS 18 a broadcast channel works too: `pushType: .channel("ferry-route-12")`.
 
 Update payload: