@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/shared/external/NOTICE-swift-ios-skills.md

@@ -0,0 +1,41 @@
+# Vendored Skills - swift-ios-skills
+
+67 skills under `pipeline/skills/shared/external/` are vendored from the dpearson2699/swift-ios-skills collection (Agent Skills for iOS 26+, Swift 6.3, SwiftUI, and modern Apple frameworks).
+
+Required Notice: Copyright (c) 2025 dpearson2699 (https://github.com/dpearson2699)
+
+## Upstream
+
+- Repository: https://github.com/dpearson2699/swift-ios-skills
+- Vendored commit: `8112d10` (2026-06-04, post-v3.5.0)
+- License: PolyForm Perimeter 1.0.0 (see LICENSE in upstream repo). Redistribution of copies requires preserving the Required Notice above.
+
+## Local modifications
+
+- Punctuation normalized to ASCII per pipeline humanizer policy (em-dash, en-dash, ellipsis, curly quotes, section sign).
+- 12 skills keep local directory and frontmatter names that differ from upstream:
+
+| Local name | Upstream name |
+|---|---|
+| `live-activities` | `activitykit` |
+| `callkit-voip` | `callkit` |
+| `cloudkit-sync` | `cloudkit` |
+| `eventkit-calendar` | `eventkit` |
+| `homekit-matter` | `homekit` |
+| `mapkit-location` | `mapkit` |
+| `metrickit-diagnostics` | `metrickit` |
+| `musickit-audio` | `musickit` |
+| `passkit-wallet` | `passkit` |
+| `pencilkit-drawing` | `pencilkit` |
+| `photos-camera-media` | `photokit` |
+| `realitykit-ar` | `realitykit` |
+
+## Vendored same-name skills (45)
+
+alarmkit, app-clips, app-intents, app-store-optimization, app-store-review, apple-on-device-ai, authentication, background-processing, contacts-framework, core-bluetooth, core-motion, core-nfc, coreml, debugging-instruments, device-integrity, energykit, healthkit, ios-accessibility, ios-localization, ios-networking, natural-language, permissionkit, push-notifications, shareplay-activities, speech-recognition, storekit, swift-charts, swift-codable, swift-concurrency, swift-language, swift-testing, swiftdata, swiftui-animation, swiftui-gestures, swiftui-layout-components, swiftui-liquid-glass, swiftui-navigation, swiftui-patterns, swiftui-performance, swiftui-uikit-interop, swiftui-webkit, tipkit, vision-framework, weatherkit, widgetkit
+
+## Adopted 2026-06-04 (10 new)
+
+avkit, core-data, cryptokit, ios-simulator, pdfkit, swift-api-design-guidelines, swift-architecture, swift-formatstyle, swift-security, swiftlint
+
+Note: `swift-security` is a superset of the older standalone `ios-security` skill; `ios-security` is kept because Phase 4 review references it. Candidate for retirement in a later pass.

package/pipeline/skills/shared/external/NOTICE-xcode-build-skills.md

@@ -0,0 +1,53 @@
+# Vendored Skills - Xcode Build Optimization
+
+The following 6 skills under `pipeline/skills/shared/external/` are vendored from an external open-source project. They are redistributed under the same MIT license as upstream.
+
+| Skill directory | Role |
+|-----------------|------|
+| `xcode-build-orchestrator/` | Entry point. Two-phase recommend-first workflow: analyze, then apply approved fixes. |
+| `xcode-build-benchmark/` | Repeatable Xcode clean + incremental + zero-change baseline with timing summary. |
+| `xcode-compilation-analyzer/` | Swift / mixed-language compile hotspot detection (type-check, expression complexity). |
+| `xcode-project-analyzer/` | Audits build settings, script phases, scheme behavior, target dependencies, parallelism. |
+| `spm-build-analysis/` | Swift Package Manager graph, plugin overhead, module variant detection, swift-syntax universal builds. |
+| `xcode-build-fixer/` | Applies approved optimization changes and re-benchmarks to verify wall-clock delta. |
+
+## Upstream
+
+- Repository: https://github.com/AvdLee/Xcode-Build-Optimization-Agent-Skill
+- Author: Antoine van der Lee (contact@avanderlee.com)
+- Vendored commit: `6bd7b59` (2026-05-12)
+- License: MIT (see LICENSE in upstream repo)
+
+## Vendor policy
+
+- These skill directories are kept as-is from upstream **with one deployment tweak**: every `SKILL.md` frontmatter has `user-invocable: false` added so the 6 specialists do not clutter the `/multi-agent:*` slash autocomplete menu. The wrapper `/multi-agent:build-optimize` dispatches to them programmatically via the Skill() tool, which works regardless of the discoverability flag.
+- Updates land via a single shallow re-copy of the 6 skill trees from upstream HEAD followed by re-applying the `user-invocable: false` line. Future automation could collapse this into the sync script.
+- 40+ optimization checks documented in upstream `OPTIMIZATION-CHECKS.md`; refer there for the full catalog.
+- Skills produce artifacts under `.build-benchmark/` in the target project. No project files (source, settings, packages) are modified without explicit developer approval.
+- Python 3 standard library only; no extra pip dependencies.
+
+## License (MIT, redistributed)
+
+```
+MIT License
+
+Copyright (c) 2026 Antoine van der Lee
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```

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

@@ -10,7 +10,7 @@ date_added: "2026-04-02"
 
 ## Overview
 
-AgentFlow turns your existing Kanban board into a fully autonomous AI development pipeline. Instead of building custom orchestration infrastructure, it treats your project management tool (Asana, GitHub Projects, Linear) as a distributed state machine — tasks move through stages, AI agents read and write state via comments, and humans intervene through the same UI they already use.
+AgentFlow turns your existing Kanban board into a fully autonomous AI development pipeline. Instead of building custom orchestration infrastructure, it treats your project management tool (Asana, GitHub Projects, Linear) as a distributed state machine  -  tasks move through stages, AI agents read and write state via comments, and humans intervene through the same UI they already use.
 
 The result is complete pipeline observability from your phone, free crash recovery (state lives in your PM tool, not in memory), and human override at any point by dragging a card.
 
@@ -26,7 +26,7 @@ The result is complete pipeline observability from your phone, free crash recove
 
 ### 7-Stage Kanban Pipeline
 
-Tasks flow through: Backlog, Research, Build, Review, Test, Integrate, Done. Each stage has specific gates. The Kanban board IS the orchestration layer — no separate database, no message queue, no custom infrastructure.
+Tasks flow through: Backlog, Research, Build, Review, Test, Integrate, Done. Each stage has specific gates. The Kanban board IS the orchestration layer  -  no separate database, no message queue, no custom infrastructure.
 
 ### Stateless Orchestrator
 
@@ -80,16 +80,16 @@ This reads your SPEC.md, decomposes it into atomic tasks, maps dependencies, and
 Open 3-4 terminal windows, each as a worker slot:
 
 ```bash
-# Terminal 2 — Builder
+# Terminal 2  -  Builder
 claude -p "/sdlc-worker --slot T2"
 
-# Terminal 3 — Builder
+# Terminal 3  -  Builder
 claude -p "/sdlc-worker --slot T3"
 
-# Terminal 4 — Reviewer
+# Terminal 4  -  Reviewer
 claude -p "/sdlc-worker --slot T4"
 
-# Terminal 5 — Tester
+# Terminal 5  -  Tester
 claude -p "/sdlc-worker --slot T5"
 ```
 
@@ -165,9 +165,9 @@ Or install as a Claude Code plugin:
 - Do: Write a clear SPEC.md before running `/spec-to-board`
 - Do: Start with 3-4 workers for a typical project
 - Do: Monitor from your Kanban board and drag cards to "Needs Human" when needed
-- Do: Review LEARNINGS.md periodically — it captures common failure patterns
-- Don't: Skip the deterministic quality gates — they catch most issues cheaply
-- Don't: Force-push to main — AgentFlow uses `git revert` for safety
+- Do: Review LEARNINGS.md periodically  -  it captures common failure patterns
+- Don't: Skip the deterministic quality gates  -  they catch most issues cheaply
+- Don't: Force-push to main  -  AgentFlow uses `git revert` for safety
 - Don't: Run more workers than your project's parallelism supports
 
 ## Troubleshooting

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

@@ -1,19 +1,21 @@
 ---
 name: alarmkit
-description: "Implement AlarmKit alarms and countdown timers for iOS and iPadOS with Lock Screen, Dynamic Island, and Apple Watch system UI. Covers AlarmManager scheduling, AlarmAttributes and AlarmPresentation, AlarmButton stop and snooze actions, authorization, state observation, and Live Activity integration. Use when building wake-up alarms, countdown timers, or alarm-style alerts that need Apple's system alarm experience."
+description: "Implement AlarmKit alarms and countdown timers for iOS and iPadOS with Lock Screen, Dynamic Island, StandBy, and paired Apple Watch system UI. Covers AlarmManager scheduling, AlarmAttributes and AlarmPresentation, AlarmButton stop and snooze actions, authorization, state observation, countdown widget-extension handoff, and Live Activity integration. Use when building wake-up alarms, countdown timers, or alarm-style alerts that need Apple's system alarm experience."
 ---
 
 # AlarmKit
 
 Schedule prominent alarms and countdown timers that surface on the Lock Screen,
-Dynamic Island, and Apple Watch. AlarmKit requires iOS 26+ / iPadOS 26+. Alarms override
-Focus and Silent mode automatically.
+Dynamic Island, StandBy, and a paired Apple Watch when the alarm fires. AlarmKit
+requires iOS 26+ / iPadOS 26+. Alarms can break through Focus and Silent mode.
 
-AlarmKit builds on Live Activities -- every alarm creates a system-managed Live
-Activity with templated UI. You configure the presentation via `AlarmAttributes`
-and `AlarmPresentation` rather than building custom widget views.
+AlarmKit uses ActivityKit data models for its Live Activity, but the firing alert
+is system-managed alarm UI, not a general custom notification UI surface. Custom
+UI belongs only to countdown and paused Live Activity states rendered by a Widget
+Extension with the same `AlarmAttributes<Metadata>` and
+`AlarmPresentationState` used when scheduling.
 
-See `references/alarmkit-patterns.md` for complete code patterns including
+See [references/alarmkit-patterns.md](references/alarmkit-patterns.md) for complete code patterns including
 authorization, scheduling, countdown timers, snooze handling, and widget setup.
 
 ```swift
@@ -40,13 +42,14 @@ import AlarmKit
 ### 1. Create a new alarm or timer
 
 1. Add `NSAlarmKitUsageDescription` to Info.plist with a user-facing string.
-2. Request authorization with `AlarmManager.shared.requestAuthorization()`.
-3. Configure `AlarmPresentation` (alert, countdown, paused states).
-4. Create `AlarmAttributes` with the presentation, optional metadata, and tint color.
-5. Build an `AlarmManager.AlarmConfiguration` (.alarm or .timer).
-6. Schedule with `AlarmManager.shared.schedule(id:configuration:)`.
-7. Observe state changes via `alarmManager.alarmUpdates`.
-8. If using countdown, add a widget extension target for non-alerting Live Activity UI.
+2. Request authorization with `AlarmManager.shared.requestAuthorization()` when the app can explain the value, or handle the first-schedule system prompt.
+3. If authorization is `.denied` or not `.authorized`, show recovery UI instead of scheduling.
+4. Configure `AlarmPresentation` (alert, countdown, paused states).
+5. Create `AlarmAttributes` with the presentation, optional metadata, and tint color.
+6. Build an `AlarmManager.AlarmConfiguration` (.alarm or .timer).
+7. Schedule with `AlarmManager.shared.schedule(id:configuration:)`.
+8. Observe state changes via `alarmManager.alarmUpdates`.
+9. If using countdown, add a Widget Extension target with an `ActivityConfiguration` for the same `AlarmAttributes<Metadata>` type.
 
 ### 2. Review existing alarm code
 
@@ -54,9 +57,10 @@ Run through the Review Checklist at the end of this document.
 
 ## Authorization
 
-AlarmKit requires explicit user authorization. Without it, alarms silently
-fail to schedule. Request early (e.g., at onboarding) or let AlarmKit prompt
-automatically on first schedule.
+AlarmKit requires user authorization. Request early when the app can explain the
+value, or let AlarmKit prompt automatically on first schedule. If authorization
+is not granted after the explicit or automatic prompt, alarms are not scheduled
+and will not alert.
 
 ```swift
 let manager = AlarmManager.shared
@@ -119,14 +123,14 @@ let weekday: Alarm.Schedule = .relative(.init(
 ```swift
 let id = UUID()
 
-let configuration = AlarmManager.AlarmConfiguration.alarm(
+let snooze = Alarm.CountdownDuration(preAlert: nil, postAlert: 300)
+let configuration = AlarmManager.AlarmConfiguration(
+    countdownDuration: snooze,
     schedule: .relative(.init(
         time: .init(hour: 7, minute: 0),
         repeats: .never
     )),
     attributes: attributes,
-    stopIntent: StopAlarmIntent(alarmID: id.uuidString),
-    secondaryIntent: SnoozeIntent(alarmID: id.uuidString),
     sound: .default
 )
 
@@ -136,6 +140,13 @@ let alarm = try await AlarmManager.shared.schedule(
 )
 ```
 
+`stopIntent` and `secondaryIntent` default to `nil`. Omit `stopIntent` for
+AlarmKit's standard system Stop behavior; provide it only when Stop must run app
+cleanup, custom stop behavior, or other side effects. Omit `secondaryIntent` for
+ordinary Snooze/Repeat with `secondaryButtonBehavior: .countdown` and
+`Alarm.CountdownDuration.postAlert`; provide it only for `.custom` secondary
+behavior or app cleanup/custom behavior.
+
 ### Alarm State Transitions
 
 ```text
@@ -150,11 +161,11 @@ scheduled --> countdown --> alerting
 cancel(id:) removes from system entirely
 ```
 
-- `cancel(id:)` -- remove the alarm completely (any state)
-- `pause(id:)` -- pause a counting-down alarm
-- `resume(id:)` -- resume a paused alarm
-- `stop(id:)` -- stop an alerting alarm
-- `countdown(id:)` -- restart countdown from alerting state (snooze)
+- `cancel(id:)` -- remove the alarm completely, including repeating alarms
+- `pause(id:)` -- pause a counting-down alarm; throws from other states
+- `resume(id:)` -- resume a paused alarm; throws from other states
+- `stop(id:)` -- stop the alarm; one-shot alarms are removed, repeating alarms reschedule
+- `countdown(id:)` -- restart countdown from alerting state (snooze); throws from other states
 
 ## Countdown Timers
 
@@ -196,8 +207,6 @@ let config = AlarmManager.AlarmConfiguration(
         repeats: .never
     )),
     attributes: attributes,
-    stopIntent: stopIntent,
-    secondaryIntent: snoozeIntent,
     sound: .default
 )
 ```
@@ -208,18 +217,22 @@ Each `Alarm` has a `state` property reflecting its current lifecycle position.
 
 | State | Meaning |
 |---|---|
-| `.scheduled` | Waiting to fire (alarm mode) or waiting to start countdown |
+| `.scheduled` | Scheduled and ready to alert at the appropriate time |
 | `.countdown` | Actively counting down (timer or pre-alert phase) |
 | `.paused` | Countdown paused by user or app |
 | `.alerting` | Alarm is firing -- sound playing, UI prominent |
 
 ### Observing State Changes
 
+`AlarmManager.shared.alarms` is a throwing getter for the current daemon
+snapshot. Use `try`, and either propagate the error or wrap launch refresh in
+`do/catch` before relying on the snapshot.
+
 ```swift
 let manager = AlarmManager.shared
 
 // Get all current alarms
-let alarms = manager.alarms
+let alarms = try manager.alarms
 
 // Observe changes as an async sequence
 for await updatedAlarms in manager.alarmUpdates {
@@ -235,20 +248,23 @@ for await updatedAlarms in manager.alarmUpdates {
 }
 ```
 
-An alarm that disappears from `alarmUpdates` has been cancelled or fully stopped
-and is no longer tracked by the system.
+An alarm that disappears from `alarmUpdates` is no longer scheduled with
+AlarmKit. Compare against app-persisted IDs when you need to distinguish fired,
+cancelled, and rescheduled alarms.
 
 ## AlarmAttributes and AlarmPresentation
 
 `AlarmAttributes` conforms to `ActivityAttributes` and defines the static
 data for the alarm's Live Activity. It is generic over a `Metadata` type
-conforming to `AlarmMetadata`.
+conforming to `AlarmMetadata`, which inherits `Decodable`, `Encodable`,
+`Hashable`, and `Sendable`. The `metadata` value itself is optional and defaults
+to `nil`.
 
 ### AlarmPresentation
 
-Defines the UI content for each alarm state. The system renders a templated
-Live Activity using this data -- you do not build custom SwiftUI views for the
-alarm itself.
+Defines the UI content for each alarm state. The system renders the alerting UI,
+while a widget extension can customize countdown and paused Live Activity views
+with the same attributes and presentation state.
 
 ```swift
 // Alert state (required) -- shown when alarm is firing
@@ -302,6 +318,14 @@ let attributes = AlarmAttributes(
     metadata: CookingMetadata(recipeName: "Pasta", stepNumber: 3),
     tintColor: .blue
 )
+
+let attributesWithoutMetadata = AlarmAttributes<EmptyAlarmMetadata>(
+    presentation: presentation,
+    metadata: nil,
+    tintColor: .blue
+)
+
+struct EmptyAlarmMetadata: AlarmMetadata {}
 ```
 
 ### AlarmPresentationState
@@ -345,13 +369,42 @@ The secondary button on the alert UI has two behaviors:
 
 ## Live Activity Integration
 
-AlarmKit alarms automatically appear as Live Activities on the Lock Screen
-and Dynamic Island on iPhone, and in the Smart Stack on Apple Watch. The
-system manages the alerting UI. For countdown and paused states, add a
-widget extension that reads `AlarmAttributes` and `AlarmPresentationState`.
-
-A widget extension is **required** if your alarm uses countdown presentation.
-Without it, the system may dismiss alarms unexpectedly.
+AlarmKit alarms appear as Live Activities on the Lock Screen, Dynamic Island,
+StandBy, and on a paired Apple Watch when the alarm fires. The system manages
+the alerting UI. For countdown and paused states, add a Widget Extension target
+whose `ActivityConfiguration` uses the same `AlarmAttributes<Metadata>` type
+used when scheduling the alarm.
+
+A widget extension is expected if your alarm uses countdown presentation. Keep
+that lightweight metadata type available to both the app and widget extension.
+Without the extension, alarms may be dismissed unexpectedly or fail to alert,
+though the system can still show a fallback countdown UI in limited cases such
+as after a device restart before first unlock.
+
+When explaining AlarmKit boundaries, say the ownership line explicitly. AlarmKit
+owns alarm authorization, `AlarmManager` scheduling and state, `AlarmAttributes`,
+`AlarmPresentation`, `AlarmPresentationState`, sound, and system Stop/Repeat/Open
+App alarm actions for alarm and timer experiences. The firing alert remains
+system-rendered alarm UI; do not describe AlarmKit as a general custom
+notification UI surface.
+
+Custom countdown or paused alarm UI belongs in a Widget Extension
+`ActivityConfiguration` for the same `AlarmAttributes<Metadata>` type and
+`AlarmPresentationState`. Name the Apple-sourced alarm surfaces together: Lock
+Screen, Dynamic Island, StandBy, and paired Apple Watch. Do not claim Smart Stack
+as an AlarmKit surface.
+
+Route ordinary Home Screen or Smart Stack widgets, `WidgetFamily` layout choices,
+widget timelines, and `WidgetCenter` reload policy to `widgetkit`. Route non-alarm
+Live Activity lifecycle (`Activity.request`, `update`, `end`), push-to-start
+tokens, per-activity update tokens, and remote Live Activity `content-state`
+payload contracts to `activitykit`. Route generic APNs, `UNUserNotificationCenter`,
+notification categories/actions, and custom notification UI to `push-notifications`
+unless app code ultimately calls `AlarmManager`.
+
+For setup, name Apple-documented `NSAlarmKitUsageDescription` and `AlarmManager`
+authorization. Do not require unsupported AlarmKit setup keys or
+`com.apple.developer.alarmkit` unless a current Apple source documents them.
 
 ```swift
 struct AlarmWidgetBundle: WidgetBundle {
@@ -398,18 +451,21 @@ struct AlarmActivityWidget: Widget {
 **DO:** Use `.alarm` with `.weekly([...])` for recurring alarms. Timers are one-shot.
 
 **DON'T:** Omit the widget extension when using countdown presentation.
-**DO:** Add a widget extension target. AlarmKit requires it for countdown/paused Live Activity UI.
-**Why:** Without a widget extension, the system may dismiss alarms before they alert.
+**DO:** Add a widget extension target for countdown/paused Live Activity UI.
+**Why:** Without a widget extension, alarms may be dismissed before they alert; the system fallback is limited.
 
 **DON'T:** Ignore `alarmUpdates` and track alarm state manually.
 **DO:** Observe `alarmManager.alarmUpdates` to stay synchronized with the system.
 **Why:** Alarm state can change while your app is backgrounded.
 
-**DON'T:** Forget to provide a `stopIntent` -- it cannot be nil in practice.
-**DO:** Always provide a `LiveActivityIntent` for stop so the button performs cleanup.
+**DON'T:** Treat `stopIntent` and `secondaryIntent` as mandatory for every alarm.
+**DO:** Omit them for standard system Stop/Snooze; provide intents only for app cleanup or custom behavior.
+
+**DON'T:** Fold ordinary widgets, generic Live Activities, or push/local notification behavior into AlarmKit.
+**DO:** Route Home Screen/Smart Stack widgets, `WidgetFamily`, timelines, and `WidgetCenter` reloads to `widgetkit`; route non-alarm `Activity.request`/`update`/`end`, push-to-start, update tokens, and remote `content-state` payloads to `activitykit`; route generic APNs, `UNUserNotificationCenter`, and notification categories/actions to `push-notifications` unless app code ultimately calls `AlarmManager`.
 
-**DON'T:** Store large data in `AlarmMetadata`. It is serialized with the Live Activity.
-**DO:** Keep metadata lightweight. Store large data in your app and reference by ID.
+**DON'T:** Store large data in `AlarmMetadata`.
+**DO:** Keep metadata lightweight or pass `nil`. Store large data in your app and reference by ID.
 
 **DON'T:** Use deprecated `stopButton` parameter on `AlarmPresentation.Alert`.
 **DO:** Use the current `init(title:secondaryButton:secondaryButtonBehavior:)` initializer.
@@ -419,19 +475,24 @@ struct AlarmActivityWidget: Widget {
 - [ ] `NSAlarmKitUsageDescription` present in Info.plist with non-empty string
 - [ ] Authorization requested and `.denied` state handled in UI
 - [ ] `AlarmPresentation` covers all relevant states (alert, countdown, paused)
-- [ ] Widget extension target added if countdown presentation is used
-- [ ] `AlarmAttributes` metadata type conforms to `AlarmMetadata`
+- [ ] Widget Extension target uses `ActivityConfiguration` for the same `AlarmAttributes<Metadata>` type if countdown presentation is used
+- [ ] `AlarmAttributes` metadata is lightweight, optional when unused, and conforms to `AlarmMetadata`
 - [ ] Alarm ID stored for later cancel/pause/resume/stop operations
 - [ ] `alarmUpdates` async sequence observed to track state changes
-- [ ] `stopIntent` and `secondaryIntent` are valid `LiveActivityIntent` implementations
+- [ ] `stopIntent` and `secondaryIntent` omitted for standard system Stop/Snooze and provided only for cleanup/custom behavior
 - [ ] `postAlert` duration set on `CountdownDuration` if snooze (`.countdown` behavior) is used
+- [ ] AlarmKit ownership is limited to authorization, `AlarmManager` scheduling/state, `AlarmAttributes`, `AlarmPresentation`, `AlarmPresentationState`, sound, and alarm actions
+- [ ] Alerting UI is described as system-managed alarm UI, not a general custom notification UI surface
+- [ ] Custom countdown/paused UI is routed to a Widget Extension `ActivityConfiguration` using the same `AlarmAttributes<Metadata>` and `AlarmPresentationState`
+- [ ] Boundary routing is explicit: Home Screen/Smart Stack widgets, `WidgetFamily`, timelines, and `WidgetCenter` reloads go to `widgetkit`; non-alarm `Activity.request`/`update`/`end`, push-to-start/update tokens, and remote `content-state` payloads go to `activitykit`; generic APNs/`UNUserNotificationCenter` goes to `push-notifications`
+- [ ] Setup is source-grounded: `NSAlarmKitUsageDescription` and authorization are named; unsupported keys such as `com.apple.developer.alarmkit` are not required unless Apple documents them
 - [ ] Tint color set on `AlarmAttributes` to differentiate from other apps
 - [ ] Error handling for `AlarmManager.AlarmError.maximumLimitReached`
 - [ ] Tested on device (alarm sound/vibration differs from Simulator)
 
 ## References
 
-- Patterns and code: `references/alarmkit-patterns.md`
+- Patterns and code: [references/alarmkit-patterns.md](references/alarmkit-patterns.md)
 - Apple docs: [AlarmKit](https://sosumi.ai/documentation/alarmkit) |
   [AlarmManager](https://sosumi.ai/documentation/alarmkit/alarmmanager) |
   [AlarmAttributes](https://sosumi.ai/documentation/alarmkit/alarmattributes) |

package/pipeline/skills/shared/external/alarmkit/evals/evals.json

@@ -0,0 +1,41 @@
+{
+  "skill_name": "alarmkit",
+  "evals": [
+    {
+      "id": 0,
+      "prompt": "I'm adding a wake-up alarm feature to an iOS 26 app. Sketch the AlarmKit scheduling code for a one-time 7:00 AM alarm with a Snooze button, and call out the Info.plist and authorization pieces I need.",
+      "expected_output": "A source-grounded AlarmKit implementation outline that requests authorization, includes NSAlarmKitUsageDescription, schedules with AlarmManager using AlarmAttributes/AlarmPresentation, and configures snooze with CountdownDuration.postAlert rather than the .alarm convenience alone.",
+      "files": [],
+      "expectations": [
+        "Mentions NSAlarmKitUsageDescription and user authorization through AlarmManager before relying on scheduling.",
+        "Uses AlarmAttributes and AlarmPresentation.Alert with the current alert initializer shape that does not require a custom stopButton.",
+        "Configures snooze by providing Alarm.CountdownDuration with postAlert and the countdown-style AlarmConfiguration initializer, not only AlarmConfiguration.alarm(...).",
+        "Treats stopIntent and secondaryIntent as optional API parameters while recommending them when button actions need app cleanup or custom behavior."
+      ]
+    },
+    {
+      "id": 1,
+      "prompt": "Review this AlarmKit state-management plan: cache AlarmManager.shared.alarms at launch, pause any scheduled alarm, call countdown(id:) whenever the user taps Snooze, and call stop(id:) to remove both one-shot and repeating alarms. What should I fix?",
+      "expected_output": "A review that corrects the throwing alarms getter, valid lifecycle states for pause/resume/countdown, and stop behavior for one-shot versus repeating alarms.",
+      "files": [],
+      "expectations": [
+        "States that AlarmManager.shared.alarms is a throwing getter and examples should handle it with try or do/catch.",
+        "Explains that pause(id:) applies to countdown state, resume(id:) applies to paused state, and countdown(id:) applies to alerting state.",
+        "Explains that stop(id:) removes one-shot alarms but repeating alarms are scheduled again for their next occurrence.",
+        "Avoids claiming that a missing alarm from alarmUpdates always means only cancellation or a final stop; frames it as no longer scheduled with AlarmKit unless compared with app-persisted IDs."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "My timer app needs a 10-minute AlarmKit countdown with custom Lock Screen and Dynamic Island UI, plus maybe normal Home Screen widgets and APNs updates later. Which parts belong in AlarmKit, and where should I hand off to sibling skills?",
+      "expected_output": "A boundary-aware answer that keeps AlarmKit responsible for system alarms/countdowns and their countdown Live Activity handoff, while routing generic widget and push-notification work to the appropriate sibling skills.",
+      "files": [],
+      "expectations": [
+        "Keeps AlarmKit focused on system alarms/countdowns, AlarmManager, AlarmAttributes, AlarmPresentation, AlarmPresentationState, and authorization.",
+        "Clarifies that alerting UI is system-managed while countdown/paused Live Activity UI can be customized in a widget extension.",
+        "Names Apple-sourced surfaces such as Lock Screen, Dynamic Island, StandBy, and paired Apple Watch, without relying on an unsupported AlarmKit Smart Stack claim.",
+        "Routes ordinary Home Screen/timeline widget work to widgetkit or ActivityKit details to activitykit, and generic APNs setup to push-notifications instead of expanding AlarmKit scope."
+      ]
+    }
+  ]
+}

package/pipeline/skills/shared/external/alarmkit/references/alarmkit-patterns.md

@@ -2,7 +2,8 @@
 
 Complete implementation patterns for AlarmKit alarms, countdown timers,
 authorization, state observation, and Live Activity integration. All patterns
-target iOS 26+ / iPadOS 26+ with Swift 6.2.
+target iOS 26+ / iPadOS 26+ with Swift 6.3. The alerting UI is system-managed;
+countdown and paused states use a widget extension for custom Live Activity UI.
 
 ## Contents
 - Complete Alarm Scheduling Flow
@@ -73,7 +74,9 @@ func scheduleWakeUpAlarm(
     )
 
     let id = UUID()
-    let config = AlarmManager.AlarmConfiguration.alarm(
+    let snooze = Alarm.CountdownDuration(preAlert: nil, postAlert: 300)
+    let config = AlarmManager.AlarmConfiguration(
+        countdownDuration: snooze,
         schedule: .relative(.init(
             time: .init(hour: hour, minute: minute), repeats: .never
         )),
@@ -232,7 +235,9 @@ final class AlarmStore {
     private let manager = AlarmManager.shared
     private(set) var alarms: [Alarm] = []
 
-    init() { alarms = manager.alarms }
+    func refreshAlarms() throws {
+        alarms = try manager.alarms
+    }
 
     func startObserving() async {
         for await updatedAlarms in manager.alarmUpdates {
@@ -273,15 +278,19 @@ struct AlarmListView: View {
                 }
             }
         }
-        .task { await store.startObserving() }
+        .task {
+            try? store.refreshAlarms()
+            await store.startObserving()
+        }
     }
 }
 ```
 
 ## Live Activity Widget Extension for Alarms
 
-Widget extension that renders countdown and paused states. Required when
-your alarm uses countdown presentation.
+Widget extension that renders countdown and paused states. AlarmKit expects this
+when your alarm uses countdown presentation; the system fallback countdown UI is
+limited to cases such as after restart before first unlock.
 
 ```swift
 import WidgetKit
@@ -341,7 +350,7 @@ struct AlarmLockScreenView: View {
     let context: ActivityViewContext<AlarmAttributes<CookingTimerMetadata>>
 
     var body: some View {
-        VStack(alignment: .leading, spacing: 8) {
+        VStack(alignment: .leading) {
             HStack {
                 Image(systemName: "alarm.fill")
                     .foregroundStyle(context.attributes.tintColor)
@@ -518,23 +527,21 @@ func scheduleAlarmWithOpenAction(hour: Int, minute: Int) async throws -> Alarm {
 This key is **mandatory**. If missing or empty, `schedule(id:configuration:)`
 will fail and no alarms can be created by the app.
 
-### Recommended: NSSupportsLiveActivities
+### Countdown UI setup
 
-Since alarms create Live Activities, also include:
-
-```xml
-<key>NSSupportsLiveActivities</key>
-<true/>
-```
+If you support countdown presentation, add a widget extension target for the
+custom Live Activity UI. Keep `NSAlarmKitUsageDescription` in the host app's
+Info.plist; Apple does not document `NSSupportsLiveActivities` as an AlarmKit
+setup key.
 
 ## Error Handling
 
 ```swift
 import AlarmKit
 
-func scheduleAlarmSafely(
+func scheduleAlarmSafely<Metadata: AlarmMetadata>(
     id: UUID,
-    configuration: AlarmManager.AlarmConfiguration<some AlarmMetadata>
+    configuration: AlarmManager.AlarmConfiguration<Metadata>
 ) async {
     guard AlarmManager.shared.authorizationState == .authorized else {
         print("Not authorized -- request authorization first")