@mmerterden/multi-agent-pipeline 14.1.1 → 14.2.2

package/pipeline/skills/shared/core/multi-agent-help/SKILL.md

@@ -94,7 +94,8 @@ Utility Commands (dash form on Copilot, colon form on Claude Code):
   /multi-agent:log [#id]      Show task log
   /multi-agent:resume [#id]   Resume a paused task
   /multi-agent:kill [#id]     Delete worktree (logs preserved)
-  /multi-agent:clear-logs     Clean global log directory
+  /multi-agent:prune-logs     Delete per-task logs (audit + metrics kept; dry-run first)
+  /multi-agent:garbage-collect  Sweep leftover /tmp scratch + worktree residue (dry-run first)
   /multi-agent:purge          Worktree + logs  -  full reset (double confirm)
   /multi-agent:channels       Post multi-channel report (Jira/Confluence/Wiki/PR)
   /multi-agent:review         Review a PR or branch diff; no URL -> pick open GitHub/Bitbucket PRs
@@ -104,6 +105,13 @@ Utility Commands (dash form on Copilot, colon form on Claude Code):
   /multi-agent:sync           Sync ecosystem (Claude + Copilot + website)
   /multi-agent:setup          Keychain tokens + Git identity + language onboarding
   /multi-agent:language [en|tr]  Show or set prompt language
+  /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=]  Pre-submission store readiness,
+                              iOS + Android, local-only. Three symmetric gates per platform: static package
+                              audit, the store's own validator, policy review vs source. Plus the running-app
+                              sweep. A skipped gate is never counted as a pass. Never uploads.
+  /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  iOS-pinned alias of :store-ready.
+  /multi-agent:ios-coding-standard [module]  Audit an iOS module against the 99-rule coding-standard
+                              registry -> remediation plan + onboarding summary -> hand off to dev.
 
 ------------------------------------------------------------
 
@@ -117,11 +125,22 @@ Interactive Launchers:
 UI Testing (standalone):
 
   /multi-agent:test                  Full simulator test (screenshot all screens)
-  /multi-agent:test "dark mode"      Dark mode bug test
-  /multi-agent:test "accessibility"  Accessibility audit
-  /multi-agent:test "dynamic type"   Large text size test
-  /multi-agent:test "screenshot tr"  App Store screenshots in Turkish
-  /multi-agent:test "store-ready"    App Store guideline pre-flight check
+
+  Fixed-scenario commands  -  no quoting, and they autocomplete off `test-`:
+
+  /multi-agent:test-dark-mode        Dark mode bug test
+  /multi-agent:test-accessibility    Accessibility audit
+  /multi-agent:test-dynamic-type     Large text size test
+  /multi-agent:test-screenshots [tr] App Store screenshot set in a locale (default tr)
+
+  The scenario-tag form still works and is not deprecated  -  each command above is
+  an alias for it.
+
+  /multi-agent:test "dark mode" | "accessibility" | "dynamic type" | "screenshot <lang>"
+
+  `store-ready` is NOT a UI test: it validates a built package, on iOS and Android,
+  and lives at /multi-agent:store-ready. The old /multi-agent:test "store-ready"
+  tag still works and hands off there.
 
 Manual Test (Phase 5 standalone  -  Xcode hint flow):
 
@@ -243,7 +262,8 @@ Utility Komutları:
   /multi-agent:log [#id]      Task log'unu göster
   /multi-agent:resume [#id]   Duraklamış task'ı devam ettir
   /multi-agent:kill [#id]     Worktree'yi sil (log'lar korunur)
-  /multi-agent:clear-logs     Global log dizinini temizle
+  /multi-agent:prune-logs     Task bazlı log'ları sil (audit + metrics korunur; önce dry-run)
+  /multi-agent:garbage-collect  /tmp artıkları + worktree residue süpür (önce dry-run)
   /multi-agent:purge          Worktree + log'lar  -  tam reset (çift onay)
   /multi-agent:channels       Multi-channel rapor gönder (Jira/Confluence/Wiki/PR)
   /multi-agent:review         PR veya branch diff'ini review et; URL yoksa -> açık GitHub/Bitbucket PR seç
@@ -253,6 +273,13 @@ Utility Komutları:
   /multi-agent:sync           Ekosistemi senkronize et
   /multi-agent:setup          Keychain token + Git kimliği + dil onboarding
   /multi-agent:language [en|tr]  Prompt dilini göster veya ayarla
+  /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=]  Yükleme öncesi store hazırlığı,
+                              iOS + Android, yalnızca lokal. Platform başına 3 simetrik kapı: statik paket
+                              denetimi, store'un kendi doğrulayıcısı, kaynağa karşı politika incelemesi.
+                              Artı çalışan-app sweep'i. Atlanan kapı asla pass sayılmaz. Asla yüklemez.
+  /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  :store-ready'nin iOS'a sabitlenmiş alias'ı.
+  /multi-agent:ios-coding-standard [modül]  Bir iOS modülünü 99 kurallık kodlama-standardı registry'sine
+                              göre denetler -> düzeltme planı + onboarding özeti -> dev'e devreder.
 
 ------------------------------------------------------------
 
@@ -266,11 +293,22 @@ Utility Komutları:
 UI Testing (standalone):
 
   /multi-agent:test                  Tam simulator testi (tüm ekran screenshot'ları)
-  /multi-agent:test "dark mode"      Dark mode bug testi
-  /multi-agent:test "accessibility"  Erişilebilirlik denetimi
-  /multi-agent:test "dynamic type"   Büyük metin boyutu testi
-  /multi-agent:test "screenshot tr"  App Store screenshot (Türkçe locale)
-  /multi-agent:test "store-ready"    App Store guideline pre-flight
+
+  Sabit-senaryo komutları  -  tırnak gerekmez, `test-` ile autocomplete'e düşer:
+
+  /multi-agent:test-dark-mode        Dark mode bug testi
+  /multi-agent:test-accessibility    Erişilebilirlik denetimi
+  /multi-agent:test-dynamic-type     Büyük metin boyutu testi
+  /multi-agent:test-screenshots [tr] Belirtilen dilde App Store screenshot seti (default tr)
+
+  Senaryo etiketli form çalışmaya devam eder, kaldırılmadı  -  yukarıdaki komutların
+  her biri onun alias'ı.
+
+  /multi-agent:test "dark mode" | "accessibility" | "dynamic type" | "screenshot <dil>"
+
+  `store-ready` bir UI testi DEĞİL: üretilmiş paketi doğrular, iOS + Android, ve
+  /multi-agent:store-ready altında. Eski /multi-agent:test "store-ready" etiketi
+  çalışmaya devam eder ve oraya devreder.
 
 Manuel Test (Phase 5 standalone  -  Xcode hint akışı):
 

package/pipeline/skills/shared/core/multi-agent-language/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: multi-agent-language
 language: en
-description: "Toggle outputLanguage (assistant explanations). promptLanguage is fixed to English. External payloads stay English. Use when the assistant should explain itself in a different language."
+description: "Toggle outputLanguage (assistant explanations, picker questions, PR/Jira/Confluence bodies). promptLanguage is fixed to English; commit messages, branch names and identifiers stay English. Use when the assistant should explain itself in a different language."
 user-invocable: true
 argument-hint: "[en|tr]  -  sets outputLanguage; omit for interactive picker; use 'output en|tr' for explicit form"
 ---

package/pipeline/skills/shared/core/multi-agent-local/SKILL.md

@@ -35,3 +35,7 @@ multi-agent-local "PROJ-12345"                                 # Jira
 multi-agent-local "#42"                                        # GitHub issue
 multi-agent-local "LoginView dark mode fix"                    # Free-text
 ```
+
+## Required: outward-facing payload contracts
+
+Before writing anything outward-facing  -  PR body, Jira comment, Confluence page, closing report  -  load `$HOME/.claude/multi-agent-refs/payload-contracts.md`. It names the canonical section set for each payload, the markup dialect per surface (PR body is Markdown, Jira is wiki markup  -  mixing them is a defect), and the token/duration numbers the closing report must carry. Improvising a payload shape from memory is the most common failure of the short modes.

package/pipeline/skills/shared/core/multi-agent-local-autopilot/SKILL.md

@@ -51,3 +51,7 @@ multi-agent-local-autopilot "#3"
 ## Delegation
 
 The orchestrator skill (`multi-agent/SKILL.md`) takes the `--local` + `"autopilot": true` state flags together. Contract: `refs/phases/phase-0-init.md` Step 8 (local branch) + `refs/phases/phase-2-planning.md` Step 5 (gate skip) + Step 5c (safety classifier, v7.0.0+).
+
+## Required: outward-facing payload contracts
+
+Before writing anything outward-facing  -  PR body, Jira comment, Confluence page, closing report  -  load `$HOME/.claude/multi-agent-refs/payload-contracts.md`. It names the canonical section set for each payload, the markup dialect per surface (PR body is Markdown, Jira is wiki markup  -  mixing them is a defect), and the token/duration numbers the closing report must carry. Improvising a payload shape from memory is the most common failure of the short modes.

package/pipeline/skills/shared/core/multi-agent-purge/SKILL.md

@@ -9,14 +9,29 @@ user-invocable: true
 
 Reset every multi-agent state. Nuclear option  -  requires double confirmation.
 
+Backed by `$HOME/.copilot/scripts/purge.sh`, which is safe by default (dry-run,
+deletes nothing until `--yes`), resolves every `rm` target strictly inside
+`<repo>/.worktrees/`, and never touches the main worktree or main/master/develop.
+
+Task log dirs are NOT purge territory  -  use `multi-agent-prune-logs`. The audit
+trail and metrics corpus at the log root are always preserved.
+
 ## Steps
 
-1. **Scan**  -  Find all worktrees:
+1. **Preview (dry-run)**  -  let the script enumerate; do not hand-roll a scan:
    ```bash
-   find {repo}/.worktrees/ -name "agent-state.json" -maxdepth 2
+   bash $HOME/.copilot/scripts/purge.sh
    ```
+   Nothing to remove -> report "nothing to purge" and stop.
+
+   **Never discover worktrees by looking for `agent-state.json` inside them.** That
+   was this skill's scan until v14.2.1 and it finds nothing: state lives at
+   `$HOME/.claude/logs/multi-agent/{project}/{task-id}/`, not in the worktree, so
+   the marker is absent from every real worktree. The scan returned zero while live
+   worktrees sat on disk, and purge reported "nothing to purge" as success. The
+   script enumerates `<repo>/.worktrees/*/` directly, which is why it works.
 
-2. **Show list**:
+2. **Show list** (the script prints it; this is the shape):
    ```
    ⚠️ WARNING: Will be deleted:
    - .worktrees/PROJ-133139/ (branch: feature/PROJ-133139-...)

package/pipeline/skills/shared/core/multi-agent-ship/SKILL.md

@@ -45,3 +45,7 @@ multi-agent ship autopilot          # no gate prompts: auto-fix, auto-PR, auto-c
 - Build+Test is the automated success gate (not the interactive device user-test  -  that is `multi-agent:manual-test`). If the repo has no tests, it reports "no tests present"  -  never fabricates results.
 - Commit/PR follows house rules: conventional message, `Ref: #N` (never Closes/Fixes), NO AI/bot attribution. PR opened only if one does not already exist.
 - Full phase contract lives in the Claude Code command `commands/multi-agent/ship/SKILL.md`; this skill is the Copilot-CLI counterpart.
+
+## Required: outward-facing payload contracts
+
+Before writing anything outward-facing  -  PR body, Jira comment, Confluence page, closing report  -  load `$HOME/.claude/multi-agent-refs/payload-contracts.md`. It names the canonical section set for each payload, the markup dialect per surface (PR body is Markdown, Jira is wiki markup  -  mixing them is a defect), and the token/duration numbers the closing report must carry. Improvising a payload shape from memory is the most common failure of the short modes.

package/pipeline/skills/shared/core/multi-agent-store-ready/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: multi-agent-store-ready
+language: en
+description: "Pre-submission store readiness for a built package, iOS and Android, local-only. Three symmetric gates per platform: a static package audit, the store's own authoritative validation, and a policy review against repo source. Separate verdict per gate, a skipped gate never counted as a pass. Validates only, never uploads. Use when a build is about to go to TestFlight or a Play track, or when a submission was rejected and the reason is not obvious."
+user-invocable: true
+argument-hint: "[repo]  -  empty = pick; repo name or path; --ipa= | --archive= | --aab= | --apk=; --skip-sweep; --resume"
+---
+
+# multi-agent-store-ready  -  pre-submission validation, iOS + Android
+
+Catch, before you upload, what App Store Connect or the Play Console would send
+back after you do.
+
+**Local-only.** No commits, no push, no PR. **It never uploads**: iOS runs
+`--validate-app`, never `--upload-app`; Android never commits a Play edit.
+
+**Input**: $ARGUMENTS
+
+## Dispatcher
+
+The full flow  -  input parsing, pickers, pre-flight, the running-app sweep, the
+three gates per platform, the report format and the next-action offer  -  lives in
+one place. Read and follow:
+
+```
+$HOME/.copilot/multi-agent/commands/store-ready.md
+```
+
+(Equivalent on Claude Code: `$HOME/.claude/commands/multi-agent/store-ready/SKILL.md`.)
+
+Do not re-derive the gate structure from this file; it is a summary, and the target
+doc is the contract.
+
+## Gate matrix (summary  -  the target doc is authoritative)
+
+| Gate | iOS | Android |
+|---|---|---|
+| 1 Static | `ios_app_store_audit` 18 rules, needs an `.xcarchive` | `android_apk_audit` + `google-play-compliance` 21 rules, needs an `.aab` |
+| 2 Authoritative | `ios_testflight_validate` → `altool --validate-app`, needs credentials | `SKIPPED`  -  Play's authoritative check is server-side only and no client ships here |
+| 3 Policy | `app-store-review` skill vs repo source | `play-store-review` skill vs repo source |
+
+Gate 2's asymmetry is reported as an asymmetry. An Android run clears at most 2 of 3
+gates and must never print `passed`. A skipped gate is never folded into the pass
+count on either platform.
+
+## Related surfaces
+
+`multi-agent-testflight-validation` is a thin alias onto this skill, kept so the
+iOS-only name keeps working; it resolves here with the platform pinned to iOS.
+`multi-agent-test "store-ready"` also resolves here. There is one implementation.

package/pipeline/skills/shared/core/multi-agent-sync/SKILL.md

@@ -31,8 +31,8 @@ Run all steps automatically:
 
 ```
 Step 1: DETECT      Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 44 sub-command skills)
-Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 44 specs as refs + 8 agent TOML)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 49 sub-command skills)
+Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 49 specs as refs + 8 agent TOML)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub)
 Step 3d: DEV-TOOLKIT Companion MCP server -> detect movement, ship gates, commit + publish
 Step 4: WEBSITE     Version + phase/model counts -> {website-host} (i18n + projects.ts)
@@ -98,7 +98,7 @@ If nothing is stale -> report "All targets up to date" and stop.
 ## Codex Sync (Step 2b)
 
 This step does **not** hand-copy files. The Codex tree is a *transform* of the Claude
-tree, not a mirror: the 43 sub-command specs become reference files (Codex silently
+tree, not a mirror: the 49 sub-command specs become reference files (Codex silently
 truncates its skills block  -  see `cross-cli-contract.md` 2.6), every reference to a
 CLI-owned tree is retargeted (`agents/<persona>.md` becomes `.toml`, the dispatcher
 becomes the router skill), the 8 personas are regenerated as TOML with a model +
@@ -223,14 +223,15 @@ When invoked with the `release` argument:
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
-**44 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**49 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
 analysis, analysis-resolve, autopilot, build-optimize, channels, create-jira, design-check, dev,
 dev-autopilot, dev-local, dev-local-autopilot, diff-explain, forget, garbage-collect,
 help, ios-coding-standard, issue, jira, kill, language, local,
 local-autopilot, log, manual-test, prune-logs, purge, refactor, resume, review, review-issue, review-jira,
-routines, save, scan, search, setup, ship, stack, status, sync, test, testflight-validation, uninstall, update
+routines, save, scan, search, setup, ship, stack, status, store-ready, sync, test, test-accessibility,
+test-dark-mode, test-dynamic-type, test-screenshots, testflight-validation, uninstall, update
 ```
 
 **NOT synced**: `refs/*`  -  Lazy-load references, Claude Code specific

package/pipeline/skills/shared/core/multi-agent-test/SKILL.md

@@ -26,14 +26,24 @@ Pass `$ARGUMENTS` through verbatim  -  the target doc picks the right test matri
 
 ## Quick reference
 
-| Invocation | What it does |
-|---|---|
-| `multi-agent-test` | Walk all screens, collect screenshot + UI tree, general report |
-| `multi-agent-test "dark mode"` | Light/dark comparison, contrast + color bugs |
-| `multi-agent-test "accessibility"` | VoiceOver label + tap target + contrast audit |
-| `multi-agent-test "dynamic type"` | XL-XXXL text-size layout check |
-| `multi-agent-test "screenshot tr"` | App Store screenshot set (Turkish locale) |
-| `multi-agent-test "store-ready"` | App Store guideline pre-flight check |
+| Invocation | Fixed-scenario alias | What it does |
+|---|---|---|
+| `multi-agent-test` | - | Walk all screens, collect screenshot + UI tree, general report |
+| `multi-agent-test "dark mode"` | `multi-agent-test-dark-mode` | Light/dark comparison, contrast + color bugs |
+| `multi-agent-test "accessibility"` | `multi-agent-test-accessibility` | VoiceOver label + tap target + contrast audit |
+| `multi-agent-test "dynamic type"` | `multi-agent-test-dynamic-type` | XL-XXXL text-size layout check |
+| `multi-agent-test "screenshot <lang>"` | `multi-agent-test-screenshots [locale]` | App Store screenshot set in a locale (alias defaults to tr) |
+| `multi-agent-test "store-ready" [path]` | hands off to `multi-agent-store-ready` | package validation, not a UI test |
+
+Both columns are supported and neither is deprecated; the aliases exist so the
+scenario list autocompletes off `test-` instead of having to be remembered.
+
+`store-ready` is the odd one out: it validates a built **package** rather than a
+running app, so it is not implemented here at all. `multi-agent-store-ready` owns
+it on both platforms  -  three gates per platform, plus this file's sweep as its
+Step A. `multi-agent-testflight-validation` is the iOS-pinned alias of that skill.
+The quoted tag is kept as a hand-off so an existing invocation still lands
+somewhere correct.
 
 ## Requirements
 

package/pipeline/skills/shared/core/multi-agent-test-accessibility/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: multi-agent-test-accessibility
+language: en
+description: "Accessibility audit on a booted simulator / emulator: VoiceOver labels, sub-44pt tap targets, contrast, traits. Alias pinning the accessibility scenario. Use when auditing a screen for assistive-technology support."
+user-invocable: true
+argument-hint: "(no arguments  -  the scenario is fixed)"
+---
+
+# multi-agent-test-accessibility  -  Accessibility audit
+
+Fixed-scenario alias. The implementation is the UI Bug Hunter flow; this skill only
+pins the scenario so the tag does not have to be typed or quoted.
+
+## Dispatcher
+
+Read and follow:
+
+```
+$HOME/.copilot/multi-agent/sim-test.md
+```
+
+(Equivalent on Claude Code: `$HOME/.claude/commands/sim-test.md`.)
+
+Run it with **scenario = `accessibility`**. Ignore `$ARGUMENTS`; the scenario is fixed
+by the skill name. Anything the user adds is context for the report, never a scenario
+override  -  to run a different matrix they invoke that skill.
+
+## Equivalent
+
+`multi-agent-test "accessibility"`  -  identical behaviour. Both forms are supported;
+neither is deprecated.
+
+## Requirements
+
+- **iOS**: Xcode + booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + running emulator or USB device (`adb devices`)
+- **MCP**: `dev-toolkit` MCP server registered (tool names start with `mcp__dev-toolkit__*`)

package/pipeline/skills/shared/core/multi-agent-test-dark-mode/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: multi-agent-test-dark-mode
+language: en
+description: "Dark mode UI test on a booted simulator / emulator: walk every screen light then dark, report contrast + colour bugs. Alias pinning the dark-mode scenario. Use when a dark-mode rendering bug is suspected."
+user-invocable: true
+argument-hint: "(no arguments  -  the scenario is fixed)"
+---
+
+# multi-agent-test-dark-mode  -  Dark mode UI test
+
+Fixed-scenario alias. The implementation is the UI Bug Hunter flow; this skill only
+pins the scenario so the tag does not have to be typed or quoted.
+
+## Dispatcher
+
+Read and follow:
+
+```
+$HOME/.copilot/multi-agent/sim-test.md
+```
+
+(Equivalent on Claude Code: `$HOME/.claude/commands/sim-test.md`.)
+
+Run it with **scenario = `dark mode`**. Ignore `$ARGUMENTS`; the scenario is fixed by
+the skill name. Anything the user adds is context for the report, never a scenario
+override  -  to run a different matrix they invoke that skill.
+
+## Equivalent
+
+`multi-agent-test "dark mode"`  -  identical behaviour. Both forms are supported;
+neither is deprecated.
+
+## Requirements
+
+- **iOS**: Xcode + booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + running emulator or USB device (`adb devices`)
+- **MCP**: `dev-toolkit` MCP server registered (tool names start with `mcp__dev-toolkit__*`)

package/pipeline/skills/shared/core/multi-agent-test-dynamic-type/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: multi-agent-test-dynamic-type
+language: en
+description: "Dynamic Type layout test on a booted simulator / emulator: re-walk every screen at XL through accessibility-extra-large, report truncation and clipping. Alias pinning the dynamic-type scenario. Use when checking a layout survives large text."
+user-invocable: true
+argument-hint: "(no arguments  -  the scenario is fixed)"
+---
+
+# multi-agent-test-dynamic-type  -  Dynamic Type layout test
+
+Fixed-scenario alias. The implementation is the UI Bug Hunter flow; this skill only
+pins the scenario so the tag does not have to be typed or quoted.
+
+## Dispatcher
+
+Read and follow:
+
+```
+$HOME/.copilot/multi-agent/sim-test.md
+```
+
+(Equivalent on Claude Code: `$HOME/.claude/commands/sim-test.md`.)
+
+Run it with **scenario = `dynamic type`**. Ignore `$ARGUMENTS`; the scenario is fixed
+by the skill name. Anything the user adds is context for the report, never a scenario
+override  -  to run a different matrix they invoke that skill.
+
+## Equivalent
+
+`multi-agent-test "dynamic type"`  -  identical behaviour. Both forms are supported;
+neither is deprecated.
+
+## Requirements
+
+- **iOS**: Xcode + booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + running emulator or USB device (`adb devices`)
+- **MCP**: `dev-toolkit` MCP server registered (tool names start with `mcp__dev-toolkit__*`)

package/pipeline/skills/shared/core/multi-agent-test-screenshots/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: multi-agent-test-screenshots
+language: en
+description: "App Store screenshot set from a booted simulator / emulator in a given locale, taken as an argument and defaulting to tr. Alias pinning the screenshot scenario. Use when generating store screenshots or checking a localised build renders."
+user-invocable: true
+argument-hint: "[locale]  -  empty = tr; e.g. tr | en | de | ar"
+---
+
+# multi-agent-test-screenshots  -  Locale screenshot set
+
+Fixed-scenario alias, **parameterised by locale**. The scenario is pinned; the language
+is not, because one skill per language would put a parameter in a name.
+
+## Locale resolution
+
+1. `$ARGUMENTS` names a locale (`tr`, `en`, `de`, `ar`, ...) → use it.
+2. `$ARGUMENTS` empty → `tr`.
+3. `$ARGUMENTS` is something other than a locale → do not guess a language and do not
+   silently fall back. Ask which locale, rendered in `outputLanguage`.
+
+## Dispatcher
+
+Read and follow:
+
+```
+$HOME/.copilot/multi-agent/sim-test.md
+```
+
+(Equivalent on Claude Code: `$HOME/.claude/commands/sim-test.md`.)
+
+Run it with **scenario = `screenshot <locale>`**, substituting the locale resolved
+above. That is the tag the target doc matches; passing a bare `screenshot` leaves the
+language unset.
+
+## Equivalent
+
+`multi-agent-test "screenshot tr"`  -  identical behaviour. Both forms are supported;
+neither is deprecated.
+
+## Requirements
+
+- **iOS**: Xcode + booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + running emulator or USB device (`adb devices`)
+- **MCP**: `dev-toolkit` MCP server registered (tool names start with `mcp__dev-toolkit__*`)

package/pipeline/skills/shared/core/multi-agent-testflight-validation/SKILL.md

@@ -1,120 +1,48 @@
 ---
 name: multi-agent-testflight-validation
 language: en
-description: "Pre-submission validation for a TestFlight / App Store build (iOS, local-only). Three gates: static archive audit, Apple's own `altool --validate-app`, and a Review-Guidelines check. ITMS codes are mapped to the rule each implies. Validates only, never uploads. Use when a build is about to go to TestFlight, or a submission was rejected and you need why."
+description: "iOS-pinned alias of store-ready: same three gates on an iOS build, one implementation. Validates a TestFlight / App Store package, never uploads. Use when an iOS build is about to go to TestFlight, or a submission was rejected and you need why."
 user-invocable: true
 argument-hint: "[repo]  -  empty = pick from prefs; repo name or path; --ipa=<path>; --archive=<path>; --resume"
 ---
 
-# multi-agent-testflight-validation  -  pre-submission validation
+# multi-agent-testflight-validation  -  iOS alias for store-ready
 
-Catch, before you upload, what App Store Connect would send back after you do.
+This skill is an alias. The implementation it used to carry was merged into
+`multi-agent-store-ready`, which runs the same three gates on iOS and adds the
+Android side, so there is one flow to maintain instead of two that had already
+started to drift.
 
-**Local-only**: no commits, no push, no PR, no channels. **It never uploads**  -  only
-`--validate-app` is ever invoked, never `--upload-app`.
+The name is kept because it is the one people reach for when the target is
+TestFlight, and removing a surface is a breaking change.
 
-## Why three gates
+## Dispatcher
 
-Each sees something the others structurally cannot, so reporting one as "the check"
-is how a build passes locally and gets rejected anyway.
+Read and follow:
 
-| Gate | Runs | Needs | Sees | Blind to |
-|---|---|---|---|---|
-| **1. Static** | `ios_app_store_audit` (18 rules) | `.xcarchive` | privacy manifest, required-reason API, Info.plist, signing, entitlements, embedded SDK, IPv6, debug leak | anything account-dependent |
-| **2. Authoritative** | `ios_testflight_validate` → `altool --validate-app` | `.ipa` + credentials | unregistered bundle ID, profile/app-record mismatch, **version+build already used**, entitlement not provisioned | the Review Guidelines |
-| **3. Guideline** | `app-store-review` skill + repo evidence | repo checkout | ATT, privacy policy, account deletion, IAP, purpose-string wording | anything not in source |
-
-Most "we passed validation and still got rejected" cases are Gate 3 findings:
-Apple's validator does not read the Review Guidelines.
-
-## Flow
-
-**0. Input.** `(empty)` → ask · `my-ios-app`/path → that repo · `--ipa=<path>` →
-Mode B without Gate 1 · `--archive=<path>` → Mode B with all gates · `--resume`.
-State at `~/.claude/logs/multi-agent/<task_id>/agent-state.json`,
-`taskId = TFV-<repo>-<yyyymmddHHMM>`. Register phases with
-`bash ~/.copilot/scripts/phase-tracker.sh` and render with
-`phase-tracker.sh render` at every boundary.
-
-**1. Pickers.** Repo (iOS entries in `prefs.projects`; a single match auto-resolves,
-and the breadcrumb says so) → branch → mode. Print
-`Step <i>/<n>: <what this decides>` for each. On `git fetch` failure do **not**
-silently use a cached ref, and **classify the failure before naming a cause**:
-`could not read Password` / `Authentication failed` / `403` is a credential
-problem, not a network one, and a VPN cannot fix it; `Could not resolve host` /
-`Operation timed out` is the network. Show the stderr line verbatim next to your
-classification, then offer the remedy that matches it. Only the network case gets
-the continue-on-a-stale-ref option: for a credential failure, staleness is
-unrelated to what broke.
-
-**2. Pre-flight.** `xcrun --find altool` and `xcodebuild -version`; a missing
-prerequisite halts. Resolve credentials and name the active tier in the report:
-tier 1 ASC API key (key id + issuer id from the keychain via
-`prefs.global.keychainMapping`, `.p8` at
-`~/.appstoreconnect/private_keys/AuthKey_<keyId>.p8`), tier 2 Apple ID +
-app-specific password by keychain reference, tier 3 none → **Gate 2 is `SKIPPED`
-and the verdict line says so**. Credentials come from `/multi-agent:setup`; never
-prompt for a secret value in chat. Tier 2 needs no elevated App Store Connect
-role, which matters when API-key creation is not permitted on the account.
-
-**3. Obtain the build.**
-- Mode B `.xcarchive` → Gate 1 runs; export with `ios_export_ipa` to reach Gate 2.
-- Mode B `.ipa` only → **Gate 1 `SKIPPED (needs .xcarchive)`**. The static audit
-  reads archive structure an `.ipa` does not carry. Do not present a two-gate run
-  as a full pass.
-- Mode A → worktree at `{projectRoot}/{worktreeBasePath}/{taskId}` (**never under
-  `$HOME`**) → `ios_xcodebuild({action: "archive", configuration: "Release",
-  destination: "generic/platform=iOS"})`  -  the simulator default would produce a
-  non-distributable archive  -  then `ios_export_ipa({method:
-  "app-store-connect", team_id, ...})`. Leave `allow_provisioning_updates` off
-  unless asked: it lets xcodebuild create or modify profiles in the developer
-  account, which a validation run has no business doing.
-
-**4. Gate 1.** `ios_app_store_audit({archive_path, rules: "all"})`. `error` blocks,
-`warning` advises. Keep each ITMS code  -  Gate 2 may return the same one, and that
-agreement tells the user it is real.
-
-**5. Gate 2.** `ios_testflight_validate({ipa_path, platform: "ios", <creds>})`.
-Render the verdict as returned: `PASS` / `FAIL` (each issue with ITMS code, mapped
-guideline, hint) / `SKIPPED` (with the reason, **never as a pass**). This is the
-only gate that catches an already-used build number  -  the most common wasted
-upload  -  so when it fails on that, name the next free build number.
-
-**6. Gate 3.** Load `app-store-review` and check, with an evidence path each:
-purpose strings (present, specific, matching actual use) · `PrivacyInfo.xcprivacy`
-(exists, declares required-reason APIs, matches linked SDKs) · ATT before any
-tracking · in-app account deletion when accounts are created · privacy policy
-reachable · IAP through StoreKit with no external purchase path · Sign in with
-Apple alongside third-party social login. Mark `pass` / `fail` /
-`not-applicable`, and `not-applicable` needs a reason  -  an unexamined area is not
-a pass.
+```
+$HOME/.copilot/multi-agent/commands/store-ready.md
+```
 
-**7. Report.** `~/TestFlightChecks/<repo>-<branch>-<timestamp>/report.md` plus a
-printed summary:
+(Equivalent on Claude Code: `$HOME/.claude/commands/multi-agent/store-ready/SKILL.md`.)
 
-```
-Verdict: <N> of 3 gates cleared[, <M> skipped]
-Build:   <path>  ·  <bundle id> <version> (<build>)
-Auth:    tier <1|2|none>  ·  <method>
+Run it with **platform pinned to `ios`** and skip its platform-detection step. Pass
+`$ARGUMENTS` through verbatim: `--ipa=`, `--archive=`, a repo name or path, and
+`--resume` all mean exactly what they mean there.
 
-Gate 1  static audit        PASS | FAIL (<n> blocking, <n> advisory) | SKIPPED (<reason>)
-Gate 2  Apple validation    PASS | FAIL (<n> issues) | SKIPPED (<reason>)
-Gate 3  guideline review    PASS | FAIL (<n> findings) | <n> not-applicable
+`--aab=` / `--apk=` are Android inputs and are not valid here. If one is supplied,
+do not silently switch platform  -  say the Android inputs belong to
+`multi-agent-store-ready`, and stop.
 
-Blocking  -  fix before uploading
-  [ITMS-90683] Info.plist: NSCameraUsageDescription missing
-      guideline 5.1.1 Data Collection and Storage
-      <hint>  ·  <file:line>
+## What you get
 
-Not run
-  Gate 1: needs an .xcarchive; only an .ipa was supplied
-```
+Unchanged from before the merge, on the iOS path:
 
-A skipped gate is never folded into the pass count. Every blocking finding carries
-a file path or an ITMS code. No AI or assistant attribution anywhere; real
-newlines, no HTML entities.
+| Gate | What runs | Needs |
+|---|---|---|
+| **1. Static** | `ios_app_store_audit` (18 rules, real ITMS codes) | an `.xcarchive` |
+| **2. Authoritative** | `ios_testflight_validate` → `altool --validate-app` | an `.ipa` + credentials |
+| **3. Policy** | `app-store-review` skill vs repo source | repo checkout |
 
-**8. Offer, do not act.** Print the exact `xcrun altool --upload-app` command for
-when the gates are clear (uploading stays an explicit human act), plus
-`--resume` after fixes and `/multi-agent:fix-bug` for code-level Gate 3 findings.
-Never upload, never bump the build number, never commit.
+A skipped gate is never folded into the pass count, and the run never uploads. The
+report lands in `~/StoreChecks/ios-<repo>-<branch>-<timestamp>/report.md`.

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

@@ -1,6 +1,6 @@
 ---
 name: firebase
-description: "You're a developer who has shipped dozens of Firebase projects. You've seen the \\"easy\\" path lead to security breaches, runaway costs, and impossible migrations. You know Firebase is powerful, but you also know its sharp edges. Use when integrating or reviewing Firebase: auth, Firestore, functions, or its cost and scaling traps."
+description: "You're a developer who has shipped dozens of Firebase projects. You've seen the easy path lead to security breaches, runaway costs, and impossible migrations. You know Firebase is powerful, but you also know its sharp edges. Use when integrating or reviewing Firebase: auth, Firestore, functions, or its cost and scaling traps."
 risk: unknown
 source: "vibeship-spawner-skills (Apache 2.0)"
 date_added: "2026-02-27"