@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/figma-ios/figma-to-component/scripts/confluence-page-ids.json

@@ -1,94 +0,0 @@
-{
-  "Design System Core": "198350074",
-  "Design System Core/Avatar": "198350076",
-  "Design System Core/Badge": "198099196",
-  "Design System Core/Background": "198350077",
-  "Design System Core/Banner": "198350078",
-  "Design System Core/Boarding Pass": "198350079",
-  "Design System Core/Button": "198350080",
-  "Design System Core/Button Controller": "198350081",
-  "Design System Core/Calendar": "198350082",
-  "Design System Core/Carousel": "198350083",
-  "Design System Core/Checkbox": "198350084",
-  "Design System Core/Floating": "198350085",
-  "Design System Core/Header/Menu D\u00fczenlenecek": "198350086",
-  "Design System Core/Info Boxes": "198350087",
-  "Design System Core/Overlay": "198350088",
-  "Design System Core/Phonebox": "198350089",
-  "Design System Core/Price": "198350090",
-  "Design System Core/Radio Button": "198350091",
-  "Design System Core/Seat": "198350092",
-  "Design System Core/Segment Buttons": "198350093",
-  "Design System Core/Selectbox": "198350094",
-  "Design System Core/Skeleton": "198350095",
-  "Design System Core/Stepper": "198350096",
-  "Design System Core/Switch&Toggle Buttons": "198350097",
-  "Design System Core/Tab Menu": "198350098",
-  "Design System Core/Text Link & Text Icon": "198350099",
-  "Design System Core/Textbox & Textarea": "198350100",
-  "Design System Core/Tooltip": "198350101",
-  "Figma Components": "198350072",
-  "Mobile App Components": "198350073",
-  "Mobile App Components/Accordion": "198350118",
-  "Mobile App Components/Account Transactions": "198350119",
-  "Mobile App Components/Additional Services": "198350107",
-  "Mobile App Components/Animations": "198350120",
-  "Mobile App Components/Availability": "198350104",
-  "Mobile App Components/Badges": "198350121",
-  "Mobile App Components/Banners": "198350122",
-  "Mobile App Components/Basket": "198350123",
-  "Mobile App Components/Booker": "198350103",
-  "Mobile App Components/Bottom Action": "198350124",
-  "Mobile App Components/Bundle Offers": "198350125",
-  "Mobile App Components/Buttons": "198350126",
-  "Mobile App Components/Cards": "198350127",
-  "Mobile App Components/Carousel": "198350128",
-  "Mobile App Components/Check-in / Boarding Pass": "198350111",
-  "Mobile App Components/Code Input (OTP)": "198350129",
-  "Mobile App Components/Counter": "198350130",
-  "Mobile App Components/Datepicker & Schudule": "198350131",
-  "Mobile App Components/Destination": "198350132",
-  "Mobile App Components/Empty States": "198350133",
-  "Mobile App Components/Explore": "198350117",
-  "Mobile App Components/File Upload": "198350134",
-  "Mobile App Components/Headers": "198350135",
-  "Mobile App Components/Help Center / FAQ": "198350113",
-  "Mobile App Components/Home Screen": "198350102",
-  "Mobile App Components/Information Sheet": "198350136",
-  "Mobile App Components/List": "198350137",
-  "Mobile App Components/Login / Sign Up / Forgot Password": "198350116",
-  "Mobile App Components/Manage Booking": "198350110",
-  "Mobile App Components/Menu Item": "198350138",
-  "Mobile App Components/Miles&Smiles + Digital Profile": "198350112",
-  "Mobile App Components/Modals": "198350139",
-  "Mobile App Components/NFC": "198350140",
-  "Mobile App Components/Navigation Bar": "198350141",
-  "Mobile App Components/Notification Center": "198350142",
-  "Mobile App Components/Passenger Information": "198350105",
-  "Mobile App Components/Payment": "198350109",
-  "Mobile App Components/Price Details": "198350143",
-  "Mobile App Components/Ratings": "198350144",
-  "Mobile App Components/Recent Searches": "198350145",
-  "Mobile App Components/Scan": "198350146",
-  "Mobile App Components/Seat Selection": "198350106",
-  "Mobile App Components/Segment Controls": "198350147",
-  "Mobile App Components/Sheets": "198350148",
-  "Mobile App Components/Standalone Flows": "198350114",
-  "Mobile App Components/Step Bar": "198350149",
-  "Mobile App Components/TK Pay Wallet": "198350115",
-  "Mobile App Components/Textbox & Selectbox": "198350150",
-  "Mobile App Components/Toaster": "198350151",
-  "Mobile App Components/Top Bar": "198350152",
-  "Mobile App Components/Travel Summary": "198350108",
-  "Visual Assets": "198350075",
-  "Visual Assets/3rd Logo": "198350161",
-  "Visual Assets/Badge": "198350159",
-  "Visual Assets/Brand Flayer": "198350154",
-  "Visual Assets/Brand Icons": "198350155",
-  "Visual Assets/Brand Logo": "198350156",
-  "Visual Assets/Country Flags": "198350158",
-  "Visual Assets/Custom Icons": "198350157",
-  "Visual Assets/Other Airlines Logos": "198350153",
-  "Visual Assets/Payment Logo": "198350160",
-  "_root": "186304971"
-}

package/pipeline/skills/shared/external/app-store-review/references/code-signing.md

@@ -1,259 +0,0 @@
-# Code Signing & Provisioning — App Store Rejection Reference
-
-## Contents
-- Common Code Signing Rejections
-- Certificate & Provisioning Profile Setup
-- Entitlements Mismatches
-- Xcode Signing Configuration
-- Distribution Signing Checklist
-- Troubleshooting Commands
-- Enterprise vs App Store Distribution
-- Automatic vs Manual Signing
-
-## Common Code Signing Rejections
-
-### ITMS-90035: Invalid Signature
-**Cause:** Binary signed with wrong certificate type (development instead of distribution) or corrupted signature.
-**Fix:**
-- Archive must use "Apple Distribution" certificate, not "Apple Development"
-- Re-export with Distribution provisioning profile
-- Check: `codesign -dv --verbose=4 YourApp.app` — `Authority` must show "Apple Distribution"
-
-### ITMS-90034: Missing or Invalid Provisioning Profile
-**Cause:** Embedded provisioning profile is missing, expired, or does not match the bundle identifier.
-**Fix:**
-- Verify profile is embedded: `ls -la YourApp.app/embedded.mobileprovision`
-- Decode and inspect: `security cms -D -i YourApp.app/embedded.mobileprovision`
-- Check `application-identifier` matches your bundle ID with team prefix
-- Regenerate profile in Apple Developer Portal if expired
-
-### ITMS-90046: Invalid Code Signing Entitlements
-**Cause:** App claims entitlements not included in provisioning profile.
-**Fix:**
-- Compare entitlements: `codesign -d --entitlements - YourApp.app`
-- Match against profile: `security cms -D -i embedded.mobileprovision` — check `Entitlements` dict
-- Remove unused entitlements from `.entitlements` file in Xcode
-- Regenerate provisioning profile after adding capabilities in Developer Portal
-
-### ITMS-90174: Invalid Bundle Structure (Framework Signing)
-**Cause:** Embedded frameworks not signed or signed with wrong identity.
-**Fix:**
-- All embedded frameworks in `Frameworks/` must be signed with same distribution certificate
-- Strip simulator architectures before submission: no `x86_64` or `i386` slices
-- Verify: `lipo -info YourFramework.framework/YourFramework`
-- Run: `codesign --verify --deep --strict YourApp.app`
-
-### ITMS-90426: Invalid Swift Support
-**Cause:** Swift runtime libraries in `SwiftSupport/` not properly signed or missing.
-**Fix:**
-- Use Xcode Organizer for distribution (handles SwiftSupport automatically)
-- If using `xcodebuild -exportArchive`, ensure export options include `stripSwiftSymbols: true`
-- Do not manually copy Swift dylibs
-
-### ITMS-90717: Invalid Provisioning Profile (Push Notifications)
-**Cause:** Push notification entitlement present but provisioning profile does not include APN capability.
-**Fix:**
-- Enable Push Notifications in Developer Portal > App ID > Capabilities
-- Create APNs key or certificate
-- Regenerate provisioning profile after enabling capability
-- Remove `aps-environment` entitlement if push not used
-
-### ITMS-90283: Invalid Provisioning Profile (App Groups)
-**Cause:** App Groups entitlement mismatch between binary and provisioning profile.
-**Fix:**
-- Register App Group in Developer Portal: `group.com.yourcompany.appname`
-- Add to App ID capabilities
-- Regenerate provisioning profiles for ALL targets sharing the group
-- Verify group ID matches exactly in `.entitlements` and profile
-
-### ERROR ITMS-90161: Invalid Provisioning Profile (Missing Capabilities)
-**Cause:** Binary uses capabilities (HealthKit, HomeKit, etc.) not enabled on App ID.
-**Fix:**
-1. Go to Developer Portal > Identifiers > Your App ID
-2. Enable the required capability
-3. Regenerate ALL provisioning profiles for this App ID
-4. In Xcode: delete old profiles, download new ones
-5. Clean build folder and re-archive
-
-## Certificate & Provisioning Profile Setup
-
-### Certificate Types
-| Certificate | Purpose | Valid For |
-|---|---|---|
-| Apple Development | Debug builds on devices | 1 year |
-| Apple Distribution | App Store & Ad Hoc distribution | 1 year |
-| iOS Distribution (legacy) | Same as Apple Distribution | 1 year |
-
-### Provisioning Profile Types
-| Profile Type | Certificate | Use Case |
-|---|---|---|
-| iOS App Development | Apple Development | Running on test devices |
-| Ad Hoc | Apple Distribution | TestFlight external / direct install |
-| App Store | Apple Distribution | App Store submission |
-
-### Certificate Renewal
-- Certificates expire annually — set calendar reminders
-- When renewing: create new certificate, regenerate ALL profiles, update CI/CD
-- Old apps on App Store continue working with expired certificates
-- New submissions require valid certificates
-
-## Entitlements Mismatches — The #1 Code Signing Rejection
-
-### Golden Rule
-Every entitlement in the binary's `.entitlements` file MUST exist in the provisioning profile. No exceptions.
-
-### How to Audit Entitlements
-
-```bash
-# Step 1: Extract entitlements from binary
-codesign -d --entitlements - YourApp.app > binary_entitlements.plist
-
-# Step 2: Extract entitlements from provisioning profile
-security cms -D -i YourApp.app/embedded.mobileprovision > profile.plist
-/usr/libexec/PlistBuddy -c "Print :Entitlements" profile.plist
-
-# Step 3: Compare — every key in binary must exist in profile
-# Common mismatches:
-# - aps-environment (push): production vs development
-# - com.apple.developer.associated-domains
-# - com.apple.security.application-groups
-# - com.apple.developer.healthkit
-# - com.apple.developer.in-app-payments (Apple Pay)
-```
-
-### Entitlements That Require Special Approval
-Some entitlements need Apple's explicit approval before they work:
-- `com.apple.developer.networking.multipath` — Multipath TCP
-- `com.apple.developer.networking.HotspotHelper` — Hotspot Helper
-- `com.apple.developer.ClassKit-environment` — ClassKit
-- `com.apple.developer.pass-type-identifiers` — Wallet passes
-- `com.apple.developer.carplay-audio` / `carplay-messaging` — CarPlay
-
-Apply for these via Developer Portal > Request > Additional Capabilities.
-
-## Xcode Signing Configuration
-
-### Recommended Setup (Automatic Signing)
-```
-Build Settings:
-  CODE_SIGN_STYLE = Automatic
-  DEVELOPMENT_TEAM = YOUR_TEAM_ID
-  CODE_SIGN_IDENTITY = Apple Distribution (for Release)
-  PROVISIONING_PROFILE_SPECIFIER = (leave empty for automatic)
-```
-
-### Manual Signing (CI/CD)
-```
-Build Settings:
-  CODE_SIGN_STYLE = Manual
-  DEVELOPMENT_TEAM = YOUR_TEAM_ID
-  CODE_SIGN_IDENTITY = Apple Distribution
-  PROVISIONING_PROFILE_SPECIFIER = "YourApp AppStore Profile"
-```
-
-### Per-Target Signing
-Each target (main app, extensions, widgets, watch app) needs its own:
-- Bundle identifier
-- Provisioning profile
-- Matching entitlements
-
-Extensions MUST use the same team ID as the main app.
-
-### Common Xcode Signing Mistakes
-1. **Debug signing config used for Archive** — Always check Release configuration
-2. **Different team IDs across targets** — All targets must share same team
-3. **Stale provisioning profiles** — Delete `~/Library/MobileDevice/Provisioning Profiles/` and re-download
-4. **Keychain access issues** — Certificate private key must be accessible to build user
-5. **Missing "Automatically manage signing" for new capabilities** — Toggle off and on to refresh
-
-## Distribution Signing Checklist
-
-Before every App Store submission:
-
-- [ ] Archive built with Release configuration
-- [ ] Code signing identity is "Apple Distribution" (not Development)
-- [ ] All provisioning profiles are App Store type and not expired
-- [ ] All targets (app, extensions, widgets) use same team ID
-- [ ] Entitlements in binary match provisioning profile capabilities
-- [ ] No simulator architectures in embedded frameworks (`lipo -info`)
-- [ ] `codesign --verify --deep --strict` passes on the .app bundle
-- [ ] Frameworks in `Frameworks/` are signed with same distribution identity
-- [ ] No `get-task-allow` entitlement in Release build (this is debug-only)
-- [ ] Push notification environment is `production` (not `development`) in Release
-
-## Troubleshooting Commands
-
-```bash
-# Verify code signature
-codesign --verify --deep --strict --verbose=2 YourApp.app
-
-# Display signing info
-codesign -dv --verbose=4 YourApp.app
-
-# Show entitlements
-codesign -d --entitlements - YourApp.app
-
-# Decode provisioning profile
-security cms -D -i YourApp.app/embedded.mobileprovision
-
-# List installed provisioning profiles
-ls ~/Library/MobileDevice/Provisioning\ Profiles/
-
-# Decode a specific profile
-security cms -D -i ~/Library/MobileDevice/Provisioning\ Profiles/PROFILE_UUID.mobileprovision
-
-# Check framework architectures (must NOT contain x86_64/i386 for submission)
-lipo -info YourFramework.framework/YourFramework
-
-# Strip simulator architectures from framework
-lipo -remove x86_64 -output YourFramework YourFramework
-
-# Find all code signing identities
-security find-identity -v -p codesigning
-
-# Verify specific provisioning profile expiry
-security cms -D -i profile.mobileprovision | grep -A1 ExpirationDate
-```
-
-## Enterprise vs App Store Distribution
-
-| | App Store | Enterprise (In-House) |
-|---|---|---|
-| Certificate | Apple Distribution | iOS Distribution (In-House) |
-| Profile Type | App Store | In-House |
-| Review | Required | Not reviewed |
-| Distribution | App Store only | Internal MDM/web |
-| Entitlements | Standard | Standard + managed |
-
-**WARNING:** Enterprise certificates are for internal apps ONLY. Apple terminates enterprise accounts that distribute to the public.
-
-## Automatic vs Manual Signing
-
-### When to Use Automatic
-- Solo developer or small team
-- Standard capabilities
-- Xcode manages profiles
-
-### When to Use Manual
-- CI/CD pipelines (Fastlane, Xcode Cloud, GitHub Actions)
-- Multiple signing configurations
-- Custom entitlements requiring specific profiles
-- Team with shared certificates via match/Fastlane
-
-### Fastlane Match Setup
-```ruby
-# Matchfile
-git_url("https://github.com/your-org/certificates")
-storage_mode("git")
-type("appstore")
-app_identifier(["com.yourcompany.app", "com.yourcompany.app.widget"])
-```
-
-```ruby
-# Fastfile
-lane :release do
-  match(type: "appstore")
-  build_app(scheme: "YourApp")
-  upload_to_app_store
-end
-```

package/pipeline/skills/shared/external/app-store-review/references/rejection-patterns.md

@@ -1,152 +0,0 @@
-# High-Risk Rejection Patterns
-
-Source: Apple App Store Review Guidelines + common rejection patterns from community data.
-
-## Contents
-- Critical Risk (Instant Rejection)
-- High Risk
-- Medium Risk
-- SDK Signature Requirements (ITMS-91065)
-
-## Critical Risk (Instant Rejection)
-
-### Private API Usage (2.5.1)
-Apple scans binaries for private API selectors. Any match = instant rejection.
-- Do not use `_` prefixed selectors
-- Do not call methods via `performSelector` to bypass detection
-- Third-party SDKs may contain private API calls — audit them
-
-### Dynamic Code Execution (2.5.2)
-- No downloading and executing code (except JavaScript in WKWebView)
-- No JSPatch, Rollout, or similar hot-patching frameworks
-- CodePush / OTA updates for JavaScript-only changes in React Native are allowed with restrictions
-
-### Hidden Features / Kill Switches (2.3.1)
-- No time-based feature reveals
-- No remote config that changes core functionality after review
-- No A/B tests that show reviewer different UI than users
-
-### Malware / Privacy Violations (5.1.1)
-- No accessing clipboard without user action
-- No scanning contacts/photos silently
-- No fingerprinting (device ID, ad ID without ATT)
-
-## High Risk
-
-### Missing SDK Signatures (ITMS-91065)
-Apple requires commonly used third-party SDKs to include a code signature. This applies to:
-- Binary frameworks (.framework, .xcframework) distributed via CocoaPods, Carthage, or manual embedding
-- SDKs on Apple's "commonly used" list
-
-**Fixes:**
-1. **Update SDK** to a version that includes a signature (preferred)
-2. **Sign the framework yourself** if the vendor hasn't updated:
-   ```bash
-   codesign --force --sign "Apple Distribution: Your Company (TEAM_ID)" \
-     --preserve-metadata=identifier,entitlements \
-     Frameworks/SDKName.framework
-   ```
-3. **Replace binary framework with source** — add the SDK's source files directly to your project instead of embedding the pre-built binary. This eliminates the signature requirement entirely.
-4. **Switch to XCFramework** — if the vendor provides an `.xcframework` with a signature, use that instead of the legacy `.framework`
-
-**Verification:**
-```bash
-# Check if a framework is signed
-codesign -dv --verbose=2 Frameworks/SDKName.framework
-
-# Verify signature validity
-codesign --verify --deep --strict Frameworks/SDKName.framework
-```
-
-### Push Notification Entitlement Mismatch (2.5)
-- `aps-environment` must be `production` in App Store builds
-- Profile must include Push Notification capability
-- If push not used, remove entitlement entirely
-
-### Background Mode Abuse (2.5.4)
-Apple audits background mode claims:
-- `audio` — must actually play audio, not just keep app alive
-- `location` — must have visible user-facing location feature
-- `voip` — must be an actual VoIP app
-- `fetch` — must fetch meaningful content
-- `processing` — must perform legitimate background processing
-
-Claiming unused background modes = rejection.
-
-### Incomplete App (2.1)
-- Broken features, placeholder content
-- Features requiring hardware reviewer lacks
-- Missing demo credentials
-- Server-dependent features that are down during review
-
-### WebView-Only Apps (4.2)
-- WKWebView wrapper without native features = rejected
-- Must add meaningful native functionality (push, offline, haptics, etc.)
-
-## Medium Risk
-
-### Missing Restore Purchases (3.1.1)
-- Every app with IAP must have a "Restore Purchases" button
-- It must work and actually restore prior purchases
-
-### Inaccurate Screenshots (2.3.1)
-- Screenshots must match actual app UI
-- No features shown that don't exist
-- No misleading marketing renders
-
-### Missing Privacy Policy (5.1.1)
-- Privacy policy URL required in App Store Connect
-- Must be accessible within the app
-- Must describe data collection accurately
-
-### Usage Description Too Vague (5.1.1)
-- "This app needs your camera" → REJECTED
-- "The camera scans boarding pass barcodes for check-in" → APPROVED
-- Must explain specific feature, not generic need
-
-### iPad Support Issues (4.1)
-- Universal apps must look proper on iPad
-- No letterboxed iPhone UI on iPad
-- Must support multitasking (Slide Over, Split View)
-
-### App Name Issues (2.3.7)
-- No generic descriptive names ("Photo Editor")
-- No competitor names or trademarked terms
-- Max 30 characters
-
-## SDK Signature Requirements (ITMS-91065) — Deep Dive
-
-Starting 2024, Apple requires third-party SDK binaries to be signed. This is one of the most common new rejection reasons.
-
-### Which SDKs Are Affected
-Apple maintains a list of "commonly used third-party SDKs." Known affected SDKs include (but are not limited to):
-- Firebase / Google Analytics
-- Facebook SDK
-- Alamofire (when embedded as binary)
-- Lottie (when embedded as binary)
-- SDWebImage (when embedded as binary)
-- Toast-Swift / Toast (when embedded as binary)
-- Kingfisher (when embedded as binary)
-- Any SDK on Apple's privacy-impacting SDK list
-
-### Resolution Priority
-1. **Best:** Use SPM or CocoaPods source integration (no binary = no signature needed)
-2. **Good:** Update to SDK version with included signature
-3. **Acceptable:** Replace binary framework with source files in project
-4. **Last resort:** Manually sign the binary framework
-
-### How to Check if Your Build Has Unsigned SDKs
-```bash
-# After archiving, inspect all frameworks
-find YourApp.xcarchive -name "*.framework" -exec codesign -dv {} \; 2>&1
-
-# Any framework showing "code object is not signed at all" needs attention
-```
-
-### Preventing Future Issues
-- Prefer SPM or source-based CocoaPods over binary frameworks
-- When adding new binary dependencies, verify signature:
-  ```bash
-  codesign --verify --deep --strict NewSDK.framework
-  ```
-- Add framework signature verification to CI/CD pipeline