@mmerterden/multi-agent-pipeline 20.36.0 → 20.37.1

package/pipeline/skills/shared/external/app-store-optimization/references/engagement-and-localization.md

@@ -0,0 +1,96 @@
+# Reviews, events and localized metadata
+
+In-app review prompts, In-App Events, ratings and review management, and localized metadata. SKILL.md keeps metadata fields, screenshots, custom pages, product page tests and the review checklist.
+
+## Asking for reviews in the app
+
+Use the SwiftUI environment value `RequestReviewAction` or, from UIKit,
+`AppStore.requestReview(in:)`. The full StoreKit surface is covered in
+`storekit`.
+
+```swift
+import StoreKit
+import SwiftUI
+
+struct TripSummaryView: View {
+    @Environment(\.requestReview) private var requestReview
+    let completedTrips: Int
+
+    var body: some View {
+        TripSummaryContent()
+            .onAppear {
+                if completedTrips == 5 { requestReview() }
+            }
+    }
+}
+```
+
+- The system shows the prompt at most three times in 365 days per device for
+  someone who has not rated the app.
+- Calling the API is a request; StoreKit decides whether anything appears.
+- Development builds always show it; TestFlight builds never do.
+- Good moments: a meaningful task just finished, a milestone or streak, a
+  visible success, several active sessions.
+- Bad moments: the very first launch, the onboarding flow, any error or crash,
+  a purchase that failed, or directly after a button tap.
+- Do not put a "Do you like this app?" dialog in front of the system prompt.
+  Apple discourages intercepting it and may reject apps that do.
+
+For a permanent "Write a review" row in settings, open
+`https://apps.apple.com/app/id{APP_ID}?action=write-review`. It goes straight
+to the review sheet and does not count against the three-per-year limit.
+
+## In-App Events
+
+Events are shown in search, on Today and in recommendations tailored to
+each user. They raise visibility while they run and can bring lapsed
+users back.
+
+- Badges (seven): Challenge, Competition, Live Event, Major Update, New
+  Season, Premiere, Special Event. Pick the one that matches what actually happens in
+  the app, and never create an event without real time-bound content.
+- Text limits in characters: 30 for the name, 50 for the short description,
+  120 for the long one.
+- Media: an event card image or video at 16:9 (1920 x 1080) and an event
+  details page image or video at 9:16 (1080 x 1920).
+- Time them with feature releases, seasonal moments and content drops.
+- Write the name and short description for someone scanning search results;
+  they appear on the event cards in Search and Today.
+- The card is shown on the product page as well, and a well-timed card lifts
+  tap-through.
+- Line events up so a new one starts as the previous one ends, keeping a card
+  in search at all times.
+
+## Ratings and reviews
+
+Star ratings and written reviews are visible on the product page and in
+search, and they move both ranking and conversion.
+
+- Earn more recent positive reviews: prompt after successes and answer
+  complaints constructively.
+- Answer critical reviews from App Store Connect. A calm, specific reply
+  improves how the app looks even when the rating does not change: acknowledge
+  the problem, say what is fixed or in progress, keep the tone neutral.
+- Read reviews as research into what users want, what frustrates them and the
+  words they use, then feed that into metadata and captions.
+- Submitting a new version offers the option of resetting the summary rating. Do it only
+  when the shown rating is far below current quality after major fixes. Keep a
+  good rating that reflects the app fairly, skip the reset for routine fixes, and after
+  a risky redesign wait until it has settled.
+
+## Localized Metadata Optimization
+
+A localized listing is a separate job from translating the app's screens.
+Keywords, descriptions and captions are researched and written per market.
+
+- Research keywords in each market. The term people use to find a photo editor
+  in Japanese is not a word-for-word translation of the English one.
+- Rewrite the description per locale, adapting opening lines, features, proof
+  and close to local expectations.
+- Localize every surface (description, keywords, previews, screenshots), and do
+  not count on literal translations or on one locale's keywords being indexed
+  elsewhere.
+- Caption screenshots in the market's language; native captions convert better
+  than English ones.
+- Localizing strings inside the app (String Catalogs, `FormatStyle`,
+  right-to-left layout) is covered by `ios-localization`.

package/pipeline/skills/shared/external/app-store-review/SKILL.md

@@ -177,42 +177,7 @@ Codes, plist layout and SDK rules: [privacy manifest reference](references/priva
 
 ## 3.1.1 Paying for digital things
 
-When the app unlocks digital content, a feature, a subscription or a digital
-service, the sale normally runs through Apple IAP, unless a guideline exception, a regional rule or
-an approved entitlement says otherwise.
-
-| Needs IAP | Does not need IAP |
-|---|---|
-| Unlocking premium features | Physical goods |
-| Subscriptions to app functionality | Real-world services such as rides or food delivery |
-| Virtual currency | Person-to-person services, for example a live tutor or consultant |
-| Removing ads | Business apps for organizations, distributed as custom apps via Apple Business Manager |
-| Digital tips to creators | Donations to approved nonprofits (see 3.2.1 and 3.2.2) |
-
-Rules around the purchase:
-
-- Before a subscription is bought, the paywall states what it costs, how long a
-  period lasts and that it renews on its own.
-- For a free trial, show the trial length, the price after it, how often billing
-  happens, that it renews automatically, and how to cancel, all before purchase.
-- Strip any route to an outside checkout for digital goods, whether a link, a
-  button or a nudge in copy, unless the storefront's current rule or a granted
-  entitlement permits it. A StoreKit External Purchase Link entitlement or,
-  where permitted, a Music Streaming Services entitlement allows a link to a
-  permitted destination; the US storefront needs no entitlement. These rules differ by region and have changed recently; read the
-  current 3.1.1(a) and 3.1.3 text for the target storefront.
-- Reader apps may link out to account sign-up with the matching entitlement, but
-  may not offer a way around IAP for in-app purchases.
-
-StoreKit checks:
-
-- Products are typed correctly in App Store Connect (consumable, non-consumable,
-  subscription).
-- A Restore Purchases control exists and works.
-- Entitlements are verified with StoreKit 2 `Transaction.currentEntitlements` or
-  on the server.
-- A purchase that is interrupted, or deferred while a parent approves it through
-  Ask to Buy, leaves the UI in a sane state.
+Unlocking digital content, features, subscriptions, virtual currency or ad removal goes through IAP unless a guideline exception, regional rule or entitlement says otherwise; physical goods and real-world services do not. The paywall must disclose price, period, renewal and trial terms before purchase, and outside checkout links need a storefront rule or entitlement. Tables, StoreKit checks and regional notes: [Monetization, submission, metadata and appeals](references/monetization-and-submission.md).
 
 ## HIG items App Review looks at
 
@@ -272,91 +237,19 @@ behind another system permission alert.
 
 ## Entitlements and usage strings
 
-Every entitlement needs a reason App Review can see in the product.
-
-| Capability | What review expects |
-|---|---|
-| Camera | a clear `NSCameraUsageDescription` |
-| Location (Always) | a visible reason the user benefits from background location |
-| Push notifications | no marketing pushes without the user's opt-in |
-| HealthKit | health data used in a meaningful feature |
-| Background Modes | every declared mode (audio, location, VoIP, fetch) has a feature that uses it |
-| App Groups | the shared data is explained |
-| Associated Domains | universal links resolve and open the app |
-
-A usage string names the data and the user-facing reason:
-
-| Verdict | String |
-|---|---|
-| Approved | "We use where you are to place the closest charging stations on the map." |
-| Approved | "The camera scans a book's barcode so you can add it to your shelf." |
-| Rejected | "This app requires camera access." |
-| Rejected | "We use your photo library to improve your experience." |
-| Fixed | "Pick a photo from your library to use as your profile picture. Only the photo you choose is uploaded." |
-
-The second rejected string names a data type but gives no concrete purpose;
-"improve your experience" is the phrase review flags. The fixed version says
-which feature uses the data and what leaves the device.
+Every entitlement needs a reason review can see in the product, and every usage string names the data and the user-facing reason ("improve your experience" is rejected). Capability table and approved versus rejected strings: [Monetization, submission, metadata and appeals](references/monetization-and-submission.md).
 
 ## Submission workflow
 
-1. Archive: Product > Archive with a Distribution signing identity, from a clean
-   Release build. Aim for zero warnings; it is good hygiene, not a review rule.
-2. Upload: in Organizer choose Distribute App, then App Store Connect; or run
-   `xcodebuild -exportArchive`. `altool` and Transporter also work.
-3. Internal TestFlight: internal testers see the build minutes after processing.
-   Try every flow on two or more screen sizes.
-4. External TestFlight: the first build sent to an external group goes through
-   Beta App Review.
-5. Submit: pick the build, complete metadata, attach screenshots, press Submit
-   for Review. Review time varies, so keep slack before a deadline.
-
-Expedited review is for a critical fix for existing users, a date-bound event
-(a holiday launch, a legal deadline) or a security patch. Ask through Contact
-Us > App Review > Expedite Request with a specific, factual reason. It is not for
-first launches or new features.
-
-Phased release for automatic updates: day 1 1%, day 2 2%, day 3 5%, day 4 10%,
-day 5 20%, day 6 50%, day 7 100%. Users who check for updates by hand get the
-build immediately. The rollout can be paused, resumed or finished early at any
-time.
+Archive a clean Release build, upload, test on internal then external TestFlight, then submit. Expedited review is only for critical fixes, date-bound events or security patches. Steps and the phased-release schedule: [Monetization, submission, metadata and appeals](references/monetization-and-submission.md).
 
 ## Metadata rules
 
-- Name and subtitle: 30 characters each. The subtitle is a short value statement.
-  A bare category word such as "Photo Editor" is likely rejected; so are
-  competitor or trademarked terms and prices. The name must be unique.
-- Screenshots: 1 to 10 per required platform and localization. The
-  6.9-inch iPhone set is the primary one; the 6.5-inch set is required only
-  when there is no 6.9-inch set, and smaller iPhones get scaled images. Apps that
-  run on iPad need 13-inch iPad screenshots; smaller iPads are scaled.
-- Screenshot content: the real UI; never show a feature the build lacks. Captions and
-  frames are fine if they neither hide nor misstate the UI. Localized sets show
-  the localized UI.
-- Keywords: 100 characters, comma-separated with no spaces. Words already in the
-  name or subtitle are indexed, so do not repeat them. Use singular or plural,
-  not both. No competitor, trademark or unrelated terms.
-- App previews: up to 30 seconds, up to 3 per localization, captured from the app
-  on a device with the app's own audio (narration or music optional). No
-  misleading framing and no footage of hands holding a device. The first frame
-  is the poster frame.
+Name and subtitle 30 characters each, keywords 100 characters, screenshots and previews show the real UI. Screenshot sets, keyword and preview limits: [Monetization, submission, metadata and appeals](references/monetization-and-submission.md).
 
 ## Rejections and appeals
 
-- A rejection arrives in the Resolution Center with the guideline number.
-- Reply in that thread with facts. If you fixed the issue, say what changed and
-  upload a new binary. If you disagree, show how the app complies, quoting the
-  guideline.
-- Keep it professional, specific and short. Attach demo credentials, screenshots
-  or a screen recording. No emotional language, no threats.
-- For a formal appeal, go to the App Review Board through the Resolution Center or
-  Contact Us > App Review > Appeal. A separate team reads the whole history. The
-  ruling is final for that build; a changed build can still be submitted.
-
-What tends to work: a video walkthrough of the flagged feature, a point-by-point
-answer against the guideline text, fresh demo credentials (the usual 2.1 cause),
-a polite reference to comparable approved behaviour, and offering an alternative
-implementation.
+Reply in the Resolution Center thread with facts: what changed, or how the app complies with the quoted guideline, plus demo credentials or a recording. Formal appeals go to the App Review Board. Full steps and what tends to work: [Monetization, submission, metadata and appeals](references/monetization-and-submission.md).
 
 ## Common mistakes
 
@@ -396,6 +289,7 @@ Full lists: [review checklists](references/review-checklists.md).
 
 ## References
 
+- [Monetization, submission, metadata and appeals](references/monetization-and-submission.md): IAP versus external purchase rules, entitlement and usage-string expectations, the archive-to-release workflow (expedited review, phased release), and name, screenshot, keyword and preview limits. Also replying to a rejection and filing an appeal.
 - Guidelines text: https://developer.apple.com/app-store/review/guidelines/
 - SDK and Xcode deadlines: https://developer.apple.com/news/upcoming-requirements/
 - Screenshot sizes: https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications/

package/pipeline/skills/shared/external/app-store-review/references/monetization-and-submission.md

@@ -0,0 +1,138 @@
+# Monetization, submission, metadata and appeals
+
+<!-- toc -->
+- [3.1.1 Paying for digital things](#311-paying-for-digital-things)
+- [Entitlements and usage strings](#entitlements-and-usage-strings)
+- [Submission workflow](#submission-workflow)
+- [Metadata rules](#metadata-rules)
+- [Rejections and appeals](#rejections-and-appeals)
+<!-- /toc -->
+
+The 3.1.1 purchase rules, entitlement and usage-string expectations, the submission workflow, metadata limits, and handling rejections and appeals. SKILL.md keeps triage, the guidelines that cause most rejections and the review checklist.
+
+## 3.1.1 Paying for digital things
+
+When the app unlocks digital content, a feature, a subscription or a digital
+service, the sale normally runs through Apple IAP, unless a guideline exception, a regional rule or
+an approved entitlement says otherwise.
+
+| Needs IAP | Does not need IAP |
+|---|---|
+| Unlocking premium features | Physical goods |
+| Subscriptions to app functionality | Real-world services such as rides or food delivery |
+| Virtual currency | Person-to-person services, for example a live tutor or consultant |
+| Removing ads | Business apps for organizations, distributed as custom apps via Apple Business Manager |
+| Digital tips to creators | Donations to approved nonprofits (see 3.2.1 and 3.2.2) |
+
+Rules around the purchase:
+
+- Before a subscription is bought, the paywall states what it costs, how long a
+  period lasts and that it renews on its own.
+- For a free trial, show the trial length, the price after it, how often billing
+  happens, that it renews automatically, and how to cancel, all before purchase.
+- Strip any route to an outside checkout for digital goods, whether a link, a
+  button or a nudge in copy, unless the storefront's current rule or a granted
+  entitlement permits it. A StoreKit External Purchase Link entitlement or,
+  where permitted, a Music Streaming Services entitlement allows a link to a
+  permitted destination; the US storefront needs no entitlement. These rules differ by region and have changed recently; read the
+  current 3.1.1(a) and 3.1.3 text for the target storefront.
+- Reader apps may link out to account sign-up with the matching entitlement, but
+  may not offer a way around IAP for in-app purchases.
+
+StoreKit checks:
+
+- Products are typed correctly in App Store Connect (consumable, non-consumable,
+  subscription).
+- A Restore Purchases control exists and works.
+- Entitlements are verified with StoreKit 2 `Transaction.currentEntitlements` or
+  on the server.
+- A purchase that is interrupted, or deferred while a parent approves it through
+  Ask to Buy, leaves the UI in a sane state.
+
+## Entitlements and usage strings
+
+Every entitlement needs a reason App Review can see in the product.
+
+| Capability | What review expects |
+|---|---|
+| Camera | a clear `NSCameraUsageDescription` |
+| Location (Always) | a visible reason the user benefits from background location |
+| Push notifications | no marketing pushes without the user's opt-in |
+| HealthKit | health data used in a meaningful feature |
+| Background Modes | every declared mode (audio, location, VoIP, fetch) has a feature that uses it |
+| App Groups | the shared data is explained |
+| Associated Domains | universal links resolve and open the app |
+
+A usage string names the data and the user-facing reason:
+
+| Verdict | String |
+|---|---|
+| Approved | "We use where you are to place the closest charging stations on the map." |
+| Approved | "The camera scans a book's barcode so you can add it to your shelf." |
+| Rejected | "This app requires camera access." |
+| Rejected | "We use your photo library to improve your experience." |
+| Fixed | "Pick a photo from your library to use as your profile picture. Only the photo you choose is uploaded." |
+
+The second rejected string names a data type but gives no concrete purpose;
+"improve your experience" is the phrase review flags. The fixed version says
+which feature uses the data and what leaves the device.
+
+## Submission workflow
+
+1. Archive: Product > Archive with a Distribution signing identity, from a clean
+   Release build. Aim for zero warnings; it is good hygiene, not a review rule.
+2. Upload: in Organizer choose Distribute App, then App Store Connect; or run
+   `xcodebuild -exportArchive`. `altool` and Transporter also work.
+3. Internal TestFlight: internal testers see the build minutes after processing.
+   Try every flow on two or more screen sizes.
+4. External TestFlight: the first build sent to an external group goes through
+   Beta App Review.
+5. Submit: pick the build, complete metadata, attach screenshots, press Submit
+   for Review. Review time varies, so keep slack before a deadline.
+
+Expedited review is for a critical fix for existing users, a date-bound event
+(a holiday launch, a legal deadline) or a security patch. Ask through Contact
+Us > App Review > Expedite Request with a specific, factual reason. It is not for
+first launches or new features.
+
+Phased release for automatic updates: day 1 1%, day 2 2%, day 3 5%, day 4 10%,
+day 5 20%, day 6 50%, day 7 100%. Users who check for updates by hand get the
+build immediately. The rollout can be paused, resumed or finished early at any
+time.
+
+## Metadata rules
+
+- Name and subtitle: 30 characters each. The subtitle is a short value statement.
+  A bare category word such as "Photo Editor" is likely rejected; so are
+  competitor or trademarked terms and prices. The name must be unique.
+- Screenshots: 1 to 10 per required platform and localization. The
+  6.9-inch iPhone set is the primary one; the 6.5-inch set is required only
+  when there is no 6.9-inch set, and smaller iPhones get scaled images. Apps that
+  run on iPad need 13-inch iPad screenshots; smaller iPads are scaled.
+- Screenshot content: the real UI; never show a feature the build lacks. Captions and
+  frames are fine if they neither hide nor misstate the UI. Localized sets show
+  the localized UI.
+- Keywords: 100 characters, comma-separated with no spaces. Words already in the
+  name or subtitle are indexed, so do not repeat them. Use singular or plural,
+  not both. No competitor, trademark or unrelated terms.
+- App previews: up to 30 seconds, up to 3 per localization, captured from the app
+  on a device with the app's own audio (narration or music optional). No
+  misleading framing and no footage of hands holding a device. The first frame
+  is the poster frame.
+
+## Rejections and appeals
+
+- A rejection arrives in the Resolution Center with the guideline number.
+- Reply in that thread with facts. If you fixed the issue, say what changed and
+  upload a new binary. If you disagree, show how the app complies, quoting the
+  guideline.
+- Keep it professional, specific and short. Attach demo credentials, screenshots
+  or a screen recording. No emotional language, no threats.
+- For a formal appeal, go to the App Review Board through the Resolution Center or
+  Contact Us > App Review > Appeal. A separate team reads the whole history. The
+  ruling is final for that build; a changed build can still be submitted.
+
+What tends to work: a video walkthrough of the flagged feature, a point-by-point
+answer against the guideline text, fresh demo credentials (the usual 2.1 cause),
+a polite reference to comparable approved behaviour, and offering an alternative
+implementation.

package/pipeline/skills/shared/external/apple-on-device-ai/SKILL.md

@@ -89,32 +89,7 @@ Facts that shape every design:
 
 Every entry point checks availability and falls back without crashing.
 
-```swift
-import Foundation
-import FoundationModels
-import os
-
-private let aiLog = Logger(subsystem: "StudyApp", category: "AI")
-
-enum SummaryState { case ready, openSettings, downloading, unsupported }
-
-func summaryState() -> SummaryState {
-    let model = SystemLanguageModel.default
-    switch model.availability {
-    case .available:
-        return model.supportsLocale(Locale.current) ? .ready : .unsupported
-    case .unavailable(.appleIntelligenceNotEnabled):
-        return .openSettings          // point the user to Settings
-    case .unavailable(.modelNotReady):
-        return .downloading           // assets still arriving; show progress
-    case .unavailable(.deviceNotEligible):
-        return .unsupported           // hardware cannot run it; use a fallback
-    case .unavailable(let other):
-        aiLog.notice("Model unavailable: \(String(describing: other))")
-        return .unsupported
-    }
-}
-```
+Code for this section: [Foundation Models and multi-backend code](references/foundation-models-code.md).
 
 ### Sessions
 
@@ -144,22 +119,6 @@ let resumed = LanguageModelSession(model: .default, tools: [], transcript: saved
 `@Generable` builds the output schema at compile time, and the response comes
 back as your type.
 
-```swift
-@Generable
-struct StudyCard {
-    @Guide(description: "The term being studied, two to four words")
-    var term: String
-    @Guide(description: "Plain-language definitions", .count(2))
-    var definitions: [String]
-    @Guide(.range(1...5))
-    var difficulty: Int
-}
-
-let reply = try await tutor.respond(to: "Make a card for osmosis",
-                                    generating: StudyCard.self)
-let card = reply.content
-```
-
 `@Guide` options:
 
 | Guide | Effect |
@@ -178,38 +137,12 @@ Fields are generated in declaration order. Put the fields that others depend on
 first.
 
 Streaming gives partial values as they form; each property of
-`StudyCard.PartiallyGenerated` is optional:
+`StudyCard.PartiallyGenerated` is optional.
 
-```swift
-let cardStream = tutor.streamResponse(to: "Card for diffusion", generating: StudyCard.self)
-for try await partial in cardStream {
-    draft.term = partial.content.term ?? draft.term
-    draft.definitions = partial.content.definitions ?? draft.definitions
-}
-```
+Code for this section: [Foundation Models and multi-backend code](references/foundation-models-code.md).
 
 ### Tools
 
-```swift
-struct GlossaryTool: Tool {
-    let name = "lookUpTerm"
-    let description = "Returns the course glossary entry for a biology term."
-
-    @Generable
-    struct Arguments {
-        @Guide(description: "Singular form of the term to look up")
-        var term: String
-        @Guide(.range(1...3))
-        var gradeLevel: Int
-    }
-
-    func call(arguments: Arguments) async throws -> String {
-        await Glossary.shared.entry(for: arguments.term, level: arguments.gradeLevel)
-            ?? "No entry found."
-    }
-}
-```
-
 - Register tools when creating the session, and only the ones the task needs.
 - `Tool` is `Sendable`; captured state must be safe to share.
 - Tool names, descriptions and argument schemas, like `@Generable` schemas,
@@ -218,27 +151,11 @@ struct GlossaryTool: Tool {
   should be fetched beforehand and put in the prompt; keep tools for lookups
   that depend on the conversation.
 
+Code for this section: [Foundation Models and multi-backend code](references/foundation-models-code.md).
+
 ### Errors
 
-```swift
-do {
-    let answer = try await tutor.respond(to: question)
-    show(answer.content)
-} catch let failure as LanguageModelSession.GenerationError {
-    switch failure {
-    case .exceededContextWindowSize:   restartWithSummary()         // too many tokens
-    case .guardrailViolation:          showRephraseHint()           // safety filter hit
-    case .concurrentRequests:          queueUntilIdle()             // session already busy
-    case .unsupportedLanguageOrLocale: showLanguageNotice()
-    case .unsupportedGuide:            logSchemaProblem()           // a @Guide the model cannot honour
-    case .assetsUnavailable:           showDownloadingState()
-    case .refusal(let refusal, _):     explain(refusal)             // stream refusal.explanation
-    case .rateLimited:                 retryLater()                 // back off
-    case .decodingFailure:             logSchemaProblem()           // output did not fit the type
-    default:                           showGenericFailure()
-    }
-}
-```
+Code for this section: [Foundation Models and multi-backend code](references/foundation-models-code.md).
 
 ### Generation options
 
@@ -374,46 +291,21 @@ MLX lifecycle, llama.cpp and GGUF: [the MLX and llama.cpp guide](references/mlx-
 ## Running several backends
 
 Try the system model first, then a local open model, and fail clearly when
-neither is there:
-
-```swift
-func pickBackend() async throws -> Backend {
-    let systemModel = SystemLanguageModel.default
-    if systemModel.isAvailable { return .foundationModels }
-    if await mlxModelCanLoad() { return .mlx }
-    throw AIError.noBackendAvailable
-}
-```
+neither is there.
 
 Send every model call through one actor so requests never compete for the same
 hardware. Actors are reentrant: a method that awaits lets the next caller in,
 so an actor that only forwards the call does not serialise anything. Chain the
 work instead:
 
-```swift
-actor InferenceGate {
-    private var last: Task<Void, Never>?
-
-    func exclusive<Value: Sendable>(
-        _ work: @escaping @Sendable () async throws -> Value
-    ) async throws -> Value {
-        let previous = last
-        let current = Task { () async throws -> Value in
-            await previous?.value
-            return try await work()
-        }
-        last = Task { _ = try? await current.value }
-        return try await current.value
-    }
-}
-```
-
 - For a custom Core ML model, this skill stops at conversion and
   optimisation. Swift integration, loading, Vision hookup and running
   predictions are for `coreml`.
 - Private material such as journals or health notes stays on the device unless
   the product has deliberately chosen a non-local fallback.
 
+Code for this section: [Foundation Models and multi-backend code](references/foundation-models-code.md).
+
 ## Performance habits
 
 1. Benchmark without the debugger: in the scheme's Run action (Cmd-Opt-R),
@@ -457,6 +349,7 @@ actor InferenceGate {
 
 ## Reference files
 
+- [Foundation Models and multi-backend code](references/foundation-models-code.md): open for the code behind availability checks, `@Generable` output, tools, error handling and backend routing.
 - [Foundation Models reference](references/foundation-models.md): the full API,
   long conversations, feedback.
 - [Conversion guide](references/coreml-conversion.md): coremltools from each