@mmerterden/multi-agent-pipeline 14.1.1 → 14.2.1

package/pipeline/commands/multi-agent/sync/SKILL.md

@@ -59,7 +59,7 @@ Run every step automatically:
 ```
 Step 1: PLATFORM    Detect macOS / Linux / Windows (Git Bash / WSL); export PLATFORM env
 Step 1.5: DETECT    Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 44 sub-command skills)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 49 sub-command skills)
 Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 44 specs as refs + 8 agent TOML)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub, bash -n on all sh)
 Step 3c: PLUGINS    pipeline shared/external -> multi-agent-plugins marketplace (rebuild knowledge/,
@@ -491,14 +491,15 @@ same 43 specs as reference files rather than as peer skills, via Step 2b -  see
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}/SKILL.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**: `$HOME/.claude/multi-agent-refs/*`  -  lazy-load references, Claude Code specific

package/pipeline/commands/multi-agent/test/SKILL.md

@@ -22,14 +22,24 @@ Pass `$ARGUMENTS` through verbatim  -  sim-test.md decides which test matrix to
 
 ## Quick reference
 
-| Invocation | What it does |
-|---|---|
-| `/multi-agent:test` | Walk every screen, collect screenshots + UI tree, produce a general report |
-| `/multi-agent:test "dark mode"` | Light vs dark comparison, contrast + colour bugs |
-| `/multi-agent:test "accessibility"` | VoiceOver label + tap-target + contrast audit |
-| `/multi-agent:test "dynamic type"` | Layout check at XL-XXXL text sizes |
-| `/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 every screen, collect screenshots + UI tree, produce a general report |
+| `/multi-agent:test "dark mode"` | `/multi-agent:test-dark-mode` | Light vs dark comparison, contrast + colour 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` | Layout check at XL-XXXL text sizes |
+| `/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
+command. The quoted tag is kept as a hand-off so an existing invocation still lands
+somewhere correct.
 
 ## Requirements
 

package/pipeline/commands/multi-agent/test-accessibility/SKILL.md

@@ -0,0 +1,33 @@
+---
+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."
+description-tr: "Booted simulator / emulator üzerinde erişilebilirlik denetimi: VoiceOver label'ları, 44x44pt altı tap target'lar, kontrast oranları ve trait'ler; her ekranda canlı UI tree'ye karşı denetlenir. /multi-agent:test \"accessibility\" için sabit-senaryo alias'ı."
+argument-hint: "(argümansız  -  senaryo sabit)"
+---
+
+# /multi-agent:test-accessibility  -  Accessibility audit
+
+Fixed-scenario alias. The implementation is the UI Bug Hunter flow; this command
+only pins the scenario so the tag does not have to be typed or quoted.
+
+## Dispatcher
+
+Read this file and apply its instructions:
+
+```
+$HOME/.claude/commands/sim-test.md
+```
+
+Run it with **scenario = `accessibility`**. Ignore `$ARGUMENTS`; the scenario is
+fixed by the command name. Anything the user adds is context for the report, never
+a scenario override  -  to run a different matrix they invoke that command.
+
+## Equivalent
+
+`/multi-agent:test "accessibility"`  -  identical behaviour. Both forms are
+supported; neither is deprecated.
+
+## Requirements
+
+- **iOS**: Xcode + a booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + a running emulator or USB device (`adb devices`)
+- **MCP**: the `dev-toolkit` MCP server must be installed (tool names start with `mcp__dev-toolkit__`)

package/pipeline/commands/multi-agent/test-dark-mode/SKILL.md

@@ -0,0 +1,33 @@
+---
+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."
+description-tr: "Booted simulator / emulator üzerinde dark mode UI testi. Her ekranı light'ta gezer, görünümü değiştirir, tekrar gezer; farktan kontrast + renk + sabit-palet buglarını raporlar. /multi-agent:test \"dark mode\" için sabit-senaryo alias'ı."
+argument-hint: "(argümansız  -  senaryo sabit)"
+---
+
+# /multi-agent:test-dark-mode  -  Dark mode UI test
+
+Fixed-scenario alias. The implementation is the UI Bug Hunter flow; this command
+only pins the scenario so the tag does not have to be typed or quoted.
+
+## Dispatcher
+
+Read this file and apply its instructions:
+
+```
+$HOME/.claude/commands/sim-test.md
+```
+
+Run it with **scenario = `dark mode`**. Ignore `$ARGUMENTS`; the scenario is fixed
+by the command name. Anything the user adds is context for the report, never a
+scenario override  -  to run a different matrix they invoke that command.
+
+## Equivalent
+
+`/multi-agent:test "dark mode"`  -  identical behaviour. Both forms are supported;
+neither is deprecated.
+
+## Requirements
+
+- **iOS**: Xcode + a booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + a running emulator or USB device (`adb devices`)
+- **MCP**: the `dev-toolkit` MCP server must be installed (tool names start with `mcp__dev-toolkit__`)

package/pipeline/commands/multi-agent/test-dynamic-type/SKILL.md

@@ -0,0 +1,33 @@
+---
+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."
+description-tr: "Booted simulator / emulator üzerinde Dynamic Type layout testi. Her ekranı XL'den accessibility-extra-large'a kadar yeniden gezer; kırpılma, taşma, üst üste binme ve ölçeklenmeyi bırakan sabit yükseklikli container'ları raporlar. /multi-agent:test \"dynamic type\" için sabit-senaryo alias'ı."
+argument-hint: "(argümansız  -  senaryo sabit)"
+---
+
+# /multi-agent:test-dynamic-type  -  Dynamic Type layout test
+
+Fixed-scenario alias. The implementation is the UI Bug Hunter flow; this command
+only pins the scenario so the tag does not have to be typed or quoted.
+
+## Dispatcher
+
+Read this file and apply its instructions:
+
+```
+$HOME/.claude/commands/sim-test.md
+```
+
+Run it with **scenario = `dynamic type`**. Ignore `$ARGUMENTS`; the scenario is
+fixed by the command name. Anything the user adds is context for the report, never
+a scenario override  -  to run a different matrix they invoke that command.
+
+## Equivalent
+
+`/multi-agent:test "dynamic type"`  -  identical behaviour. Both forms are
+supported; neither is deprecated.
+
+## Requirements
+
+- **iOS**: Xcode + a booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + a running emulator or USB device (`adb devices`)
+- **MCP**: the `dev-toolkit` MCP server must be installed (tool names start with `mcp__dev-toolkit__`)

package/pipeline/commands/multi-agent/test-screenshots/SKILL.md

@@ -0,0 +1,41 @@
+---
+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."
+description-tr: "Booted simulator / emulator'dan belirtilen dilde App Store screenshot seti: temiz status bar, her ekran gezilip yakalanır. Dili isim içine gömmek yerine argüman olarak alır (default tr). /multi-agent:test \"screenshot <lang>\" için sabit-senaryo alias'ı."
+argument-hint: "[locale]  -  boş = tr; örn. 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 command 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 with `AskUserQuestion`, rendered in
+   `outputLanguage`.
+
+## Dispatcher
+
+Read this file and apply its instructions:
+
+```
+$HOME/.claude/commands/sim-test.md
+```
+
+Run it with **scenario = `screenshot <locale>`**, substituting the locale resolved
+above. That is the tag sim-test.md 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 + a booted Simulator (`xcrun simctl list | grep Booted`)
+- **Android**: Android SDK + a running emulator or USB device (`adb devices`)
+- **MCP**: the `dev-toolkit` MCP server must be installed (tool names start with `mcp__dev-toolkit__`)

package/pipeline/commands/multi-agent/testflight-validation/SKILL.md

@@ -1,219 +1,46 @@
 ---
-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-tr: "TestFlight / App Store yüklemesi öncesi doğrulama (iOS, yalnızca lokal). Repo + branch seç, sonra ya build'i sen ver ya da koşu archive alsın; üç kapıyı geç: statik 18-kurallı archive denetimi, Apple'ın kendi `altool --validate-app`'i, ve App Store Review Guidelines'a karşı guideline incelemesi. Her kapı için ayrı verdict, ITMS kodları ilgili kurala eşlenmiş. Sadece doğrular  -  asla yüklemez."
+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."
+description-tr: "store-ready komutunun iOS'a sabitlenmiş alias'ı: iOS build'inde aynı üç kapı, tek implementasyon. TestFlight / App Store paketini doğrular, asla yüklemez."
 argument-hint: "[repo]  -  empty = pick from prefs; repo name or path; --ipa=<path>; --archive=<path>; --resume"
 allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, AskUserQuestion, Skill, mcp__dev-toolkit__ios_app_store_audit, mcp__dev-toolkit__ios_export_ipa, mcp__dev-toolkit__ios_testflight_validate, mcp__dev-toolkit__ios_xcodebuild, mcp__dev-toolkit__ios_xcresult
 ---
 
-# /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 command 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. The worktree exists only
-to archive without touching your working tree.
+The name is kept because it is the one people reach for when the target is
+TestFlight, and removing a command is a breaking change to the slash-command
+surface.
 
-**It never uploads.** Only `--validate-app` is ever invoked, never `--upload-app`.
-A validation run must not be able to ship a build by accident.
+## Dispatcher
 
-## Why three gates and not one
-
-Each gate sees something the others structurally cannot. Reporting one of them as
-"the check" is how a build passes locally and gets rejected anyway.
-
-| Gate | What runs | Needs | Sees | Blind to |
-|---|---|---|---|---|
-| **1. Static** | `ios_app_store_audit` (18 rules, real ITMS codes) | an `.xcarchive` | privacy manifest, required-reason API, Info.plist, code signing, entitlements, embedded SDK, IPv6, debug-tool leak, binary size | anything that depends on the App Store Connect account |
-| **2. Authoritative** | `ios_testflight_validate` → `altool --validate-app` | an `.ipa` + credentials | unregistered bundle ID, profile that does not match the app record, **a version+build pair already used**, entitlements not provisioned for the App ID | the Review Guidelines  -  Apple's validator does not read them |
-| **3. Guideline** | `app-store-review` skill + repo evidence | repo checkout | ATT flow, privacy policy, account deletion, IAP rules, purpose-string wording, permission justification | anything not visible in source |
-
-Gate 2 is the only one that asks Apple, and Gate 3 is the only one that covers the
-rejections a human reviewer writes. Most "we passed validation and still got
-rejected" cases are Gate 3 findings.
-
-## Step 0  -  parse input
-
-| Input | Meaning |
-|---|---|
-| (empty) | ask which repo (Step 1) |
-| `my-ios-app` or a path | that repo |
-| `--ipa=<path>` | Mode B with an `.ipa`; Gate 1 cannot run (see Step 3) |
-| `--archive=<path>` | Mode B with an `.xcarchive`; all three gates run |
-| `--resume` | continue the last run from its state file |
-
-State lives at `$HOME/.claude/logs/multi-agent/<task_id>/agent-state.json` with
-`taskId = TFV-<repo>-<yyyymmddHHMM>`. Register phases with the tracker
-(`$HOME/.claude/multi-agent-refs/tracker-contract.md`) so `:resume` and `:status`
-work like any other run.
-
-## Step 1  -  pickers (native, always)
-
-Use `AskUserQuestion` for every step  -  never a numbered text menu. Questions and
-descriptions render in `prefs.global.outputLanguage`; `label` and `header` stay
-English, per `$HOME/.claude/multi-agent-refs/picker-contract.md`. Print the
-`Step <i>/<n>: <what this decides>` breadcrumb for each.
-
-1. **Repo**  -  from `prefs.projects` where the stack is iOS. A single match
-   auto-resolves (say so in the breadcrumb, do not silently skip the step).
-2. **Branch**  -  the branch to validate. Resolution order:
-   - `git fetch --prune` first, capturing **stderr**. **If the fetch fails, do not
-     silently fall back to a cached ref**, and **classify before naming a cause**  -
-     the same rule as the `/multi-agent:dev` remote gate:
-
-     | stderr contains | Cause | Remedy |
-     |---|---|---|
-     | `could not read Password`, `Authentication failed`, `403` | credential | store the PAT in the credential helper or switch the remote to SSH. **A VPN cannot fix this**, and the base ref being stale is unrelated to what broke  -  do not offer the cached-ref fallback. |
-     | `Could not resolve host`, `Operation timed out`, `Connection refused` | network | retry / continue on the cached ref with an explicit warning / switch remote / abort, per `$HOME/.claude/multi-agent-refs/rules.md` |
-     | `Repository not found`, `404` | wrong remote | show `git remote -v` and ask |
-
-     Always print the observed stderr line next to the classification. Asserting
-     `unreachable (VPN/DNS)` for a missing-credential error that returns in under a
-     second sends the user to fix something that was never broken.
-   - Offer the current branch, the default branch, and any `release/*` /
-     `tkdevelop/*` heads.
-3. **Mode**  -  how the build is obtained:
-   - `Supply a build` (Mode B, default)  -  fastest, no signing needed in-run.
-   - `Archive from this branch` (Mode A)  -  needs a distribution certificate and
-     profile in the keychain, and takes as long as a release archive.
-
-## Step 2  -  pre-flight, before anything expensive
-
-Report every line; a missing prerequisite is a halt, not a warning.
-
-```bash
-xcrun --find altool >/dev/null 2>&1 || echo "MISSING: altool (install Xcode)"
-xcodebuild -version | head -1
-```
-
-Then resolve credentials, and **state which tier is active in the report**:
-
-| Tier | Source | Effect |
-|---|---|---|
-| 1 | ASC API key  -  key id + issuer id from the keychain via `prefs.global.keychainMapping`, `.p8` at `~/.appstoreconnect/private_keys/AuthKey_<keyId>.p8` | Gate 2 runs |
-| 2 | Apple ID + app-specific password, referenced as a keychain item | Gate 2 runs |
-| 3 | neither | **Gate 2 reports `SKIPPED`, and the run says so in the verdict line** |
-
-Credentials come from `/multi-agent:setup`; never prompt for a secret value in
-chat. If nothing is configured, tell the user which of the two tiers they can set
-up and that tier 2 needs no elevated App Store Connect role.
-
-Multi-provider accounts need `--provider-public-id`. When it is not in prefs, run
-`ios_testflight_validate({list_providers: true})` once and ask which provider.
-
-## Step 3  -  obtain the build
-
-### Mode B  -  a build you supply
-
-- `.xcarchive` → Gate 1 runs on it. To reach Gate 2 the archive must be exported,
-  so run `ios_export_ipa` (see Mode A step 3 for the signing inputs).
-- `.ipa` only → **Gate 1 is reported `SKIPPED (needs .xcarchive)`.** The static
-  audit reads archive structure that an `.ipa` does not carry. Do not present a
-  two-gate run as a full pass; say which gate did not run and why, and offer to
-  re-run with the archive.
-
-### Mode A  -  archive from the branch
-
-1. Worktree at `{projectRoot}/{worktreeBasePath}/{taskId}` on the chosen branch.
-   **Never under `$HOME`**, never a direct checkout of the main working tree.
-2. Resolve the scheme and workspace/project from prefs; ask if ambiguous.
-3. Archive:
-   `ios_xcodebuild({workspace|project, scheme, action: "archive", configuration: "Release", destination: "generic/platform=iOS"})`
-   Note the destination: the simulator default would produce an archive that
-   cannot be exported for distribution.
-4. Export:
-   `ios_export_ipa({archive_path, output_dir, method: "app-store-connect", team_id, provisioning_profiles?, signing_style?})`
-   Leave `allow_provisioning_updates` off unless the user asks: it lets xcodebuild
-   create or modify profiles in the developer account, which a validation run has
-   no business doing.
-5. A failed export halts with the parsed errors. The usual causes are a missing
-   distribution certificate, a profile that does not match the bundle ID, or
-   `signing_style: "manual"` with no `provisioning_profiles` map.
-
-## Step 4  -  Gate 1, static audit
-
-`ios_app_store_audit({archive_path, rules: "all"})`.
-
-`error` findings are blocking; `warning` is advisory. Group the output by severity
-and keep each finding's ITMS code  -  Gate 2 may return the same code, and seeing
-it in both places tells the user it is real rather than a heuristic.
-
-## Step 5  -  Gate 2, Apple's own validation
-
-`ios_testflight_validate({ipa_path, platform: "ios", <credential args>})`.
-
-Render the verdict exactly as returned:
-
-- `PASS`  -  Apple accepted the binary for delivery.
-- `FAIL`  -  list each issue with its ITMS code, the mapped guideline, and the hint.
-- `SKIPPED`  -  print the reason. **Never render this as a pass.** The verdict line
-  for the whole run must read `2 of 3 gates cleared, 1 skipped`, not `passed`.
-
-Gate 2 is the only gate that catches a build number already used  -  the most
-common wasted upload  -  so when it fails on that, say so plainly and name the next
-free build number.
-
-## Step 6  -  Gate 3, guideline review
-
-Load the `app-store-review` skill and review the repo against it. This is the gate
-that catches what a human reviewer rejects, so it reads source, not the binary:
-
-| Area | Evidence to gather |
-|---|---|
-| Purpose strings | every `NS*UsageDescription` in Info.plist  -  present, specific, user-facing, and matching what the code actually does with the data |
-| Privacy manifest | `PrivacyInfo.xcprivacy` exists, declares required-reason APIs, and matches the SDKs actually linked |
-| Tracking | if any tracking API or SDK is present, an ATT prompt exists and runs before collection |
-| Account deletion | if the app creates accounts, an in-app deletion path exists (guideline 5.1.1(v)) |
-| Privacy policy | reachable in-app and in the metadata |
-| IAP | anything unlocking features goes through StoreKit, with no external purchase path |
-| Sign in with Apple | present when a third-party social login is offered |
-
-For each: `pass` / `fail` / `not-applicable` with the evidence path that justifies
-it. `not-applicable` needs a reason  -  an unexamined area is not a pass.
-
-## Step 7  -  report
-
-Write to `~/TestFlightChecks/<repo>-<branch>-<timestamp>/report.md` and print a
-summary. Structure:
+Read this file and apply its instructions:
 
 ```
-Verdict: <N> of 3 gates cleared[, <M> skipped]
-Build:   <ipa or archive path>  ·  <bundle id> <version> (<build>)
-Auth:    tier <1|2|none>  ·  <method>
-
-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
-
-Blocking  -  fix before uploading
-  [ITMS-90683] Info.plist: NSCameraUsageDescription missing
-      guideline 5.1.1 Data Collection and Storage
-      <hint>
-      <file:line>
-
-Advisory
-  ...
-
-Not run
-  Gate 1: needs an .xcarchive; only an .ipa was supplied
+$HOME/.claude/commands/multi-agent/store-ready/SKILL.md
 ```
 
-Rules for the report:
+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.
 
-- A skipped gate is never folded into the pass count. The verdict line states the
-  skip.
-- Every blocking finding carries a file path or an ITMS code. A finding the user
-  cannot act on is noise.
-- No AI or assistant attribution anywhere, per
-  `$HOME/.claude/rules/git-conventions.md`.
-- Real newlines, no HTML entities, per
-  `$HOME/.claude/multi-agent-refs/rules.md "External System Outputs"`.
+`--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.
 
-## Step 8  -  offer the next action, do not take it
+## What you get
 
-Print, and stop:
+Unchanged from before the merge, on the iOS path:
 
-- the exact `xcrun altool --upload-app` command for when the gates are clear, so
-  uploading stays an explicit human act
-- `/multi-agent:testflight-validation --resume` to re-run after fixes
-- `/multi-agent:fix-bug` when Gate 3 produced code-level findings
+| 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 |
 
-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/commands/sim-test.md

@@ -35,12 +35,36 @@ For Android: use `mcp__dev-toolkit__android_*` tools
 /multi-agent test "accessibility"      -> accessibility audit (visual + MCP audit tool)
 /multi-agent test "dynamic type"       -> large text test
 /multi-agent test "screenshot tr"      -> locale screenshots
-/multi-agent test "store-ready"        -> full audit: visual + accessibility + archive/APK compliance
-/multi-agent test "biometric"          -> Face ID / Touch ID flow test
-/multi-agent test "performance"        -> launch time + scroll performance
+/multi-agent test "store-ready"        -> hands off to /multi-agent:store-ready (package validation)
 /sim-test                              -> standalone (same thing)
 ```
 
+Not offered, deliberately  -  `"biometric"` and `"performance"` were listed here with
+no implementation section, so reaching one fell through to the general sweep and got
+reported as the scenario asked for. Neither can be implemented symmetrically today:
+biometric has an iOS tool (`ios_biometric`) and no Android counterpart, and launch
+timing has `android_launch_time` and no iOS counterpart. Platform is auto-detected,
+so either one would work on one platform and silently do nothing on the other. They
+come back when the missing side exists, not before  -  do not re-add the rows to make
+the list look complete.
+
+Four scenarios also have a fixed-scenario command that pins the tag, so it does not
+have to be typed or quoted. They arrive here with the scenario already resolved  -
+treat them as identical to the quoted form:
+
+```
+/multi-agent:test-dark-mode            -> scenario "dark mode"
+/multi-agent:test-accessibility        -> scenario "accessibility"
+/multi-agent:test-dynamic-type         -> scenario "dynamic type"
+/multi-agent:test-screenshots [locale] -> scenario "screenshot <locale>", locale defaults to tr
+```
+
+`store-ready` is not one of them, and does not belong to this file at all: it
+validates a built package on either platform and lives at
+`/multi-agent:store-ready`. The `"store-ready"` tag is kept as a hand-off so an
+existing invocation still lands somewhere correct. `/multi-agent:testflight-validation`
+is the iOS-pinned alias of that same command.
+
 ## Flow
 
 ### Step 1  -  Device & App Discovery
@@ -121,43 +145,28 @@ Call: ios_set_locale(language: "<lang>", bundle_id: "...")
 
 **"store-ready":**
 
-Runs visual + accessibility pass AND dispatches the platform-matching compliance skill so the build is pre-validated against Apple / Google store requirements before submission.
+Not implemented here. `store-ready` validates a built **package**, which is a
+different job from driving a running app, and it is owned by one command on both
+platforms:
 
 ```
-Platform detection:
-  cwd contains .xcodeproj OR Package.swift             -> iOS
-  cwd contains build.gradle OR build.gradle.kts        -> Android
-  Otherwise                                            -> error: "store-ready needs an iOS or Android project"
-
-Step A  -  run the standard visual + accessibility sweep (light + dark + large text).
-
-Step B  -  dispatch compliance skill:
-  iOS:
-    Load $HOME/.claude/skills/apple-archive-compliance/SKILL.md
-    Prereq: @mmerterden/dev-toolkit-mcp ≥ v2.9.0 (provides ios_app_store_audit MCP tool)
-             -  installable via npm; standalone ArchiveGuard binary deprecated in v8.4.0
-    Artifact: pick newest .xcarchive under ~/Library/Developer/Xcode/Archives/**
-              OR accept explicit path argument after "store-ready"
-    Invoke:   mcp__dev-toolkit__ios_app_store_audit({ archive_path: <path>, rules: "all" })
-              OR (Node fallback): node -e "import('@mmerterden/dev-toolkit-mcp/tools/ios-app-store-audit/index.js').then(m => m.runAudit({ archivePath: '<path>', rules: 'all' }).then(r => console.log(JSON.stringify(r))))"
-              Humanize via --lang en (promptLanguage is locked to "en"; pass --lang=tr explicitly to opt into Turkish)
-  Android:
-    Load $HOME/.claude/skills/google-play-compliance/SKILL.md
-    Prereq: bundletool, aapt2, apksigner in PATH (Android SDK build-tools)
-    Artifact: newest .aab under **/build/outputs/bundle/**/*.aab
-              OR explicit path argument
-    Invoke:   bundletool validate + dump manifest, aapt2 dump badging,
-              apksigner verify, ABI/native scan
-  Merge findings with UI-hunter findings -> single report, severity-grouped.
-
-Step C  -  humanize via `--lang en` by default (promptLanguage is locked to "en"; pass --lang=tr explicitly to opt into Turkish), group by severity
-  (error = blocker, warning = risk, info = hygiene), link each finding to the
-  Apple ITMS / Play policy reference supplied by the skill catalog.
-
-Step D  -  offer `/multi-agent:channels` follow-up so findings can land in
-  Jira / Confluence / Wiki / PR body via the normal Phase 7 machinery.
+$HOME/.claude/commands/multi-agent/store-ready/SKILL.md
 ```
 
+Read that file and follow it. Pass through any artifact path given after
+`store-ready` as its `--archive=` / `--ipa=` / `--aab=` / `--apk=` input.
+
+Its Step A is the visual + accessibility sweep in this file  -  it calls back here
+for the running-app half, then runs three gates per platform that nothing in this
+file can do: the static package audit, the store's own validator, and a policy
+review against repo source. It merges both halves into one severity-grouped report
+and offers the `/multi-agent:channels` follow-up.
+
+The archive-compliance audit used to be duplicated here, invoking
+`ios_app_store_audit` with exactly the arguments the store-ready command's Gate 1
+uses. Two copies of one call is how the iOS path grew a second door with no Gate 2,
+no Gate 3 and no Android parity, so the copy is gone rather than kept in sync.
+
 **No argument (full test):**
 
 - Run light mode -> all screens

package/pipeline/multi-agent-refs/cross-cli-contract.md

@@ -6,14 +6,15 @@
 
 ---
 
-## 1. Command Inventory (44 commands)
+## 1. Command Inventory (49 commands)
 
 ```
 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
 ```
 
 Categories:

package/pipeline/multi-agent-refs/knowledge.md

@@ -56,7 +56,7 @@ Knowledge files grow over time. Maintenance rules:
 - 90-day-old entries are considered "stale"  -  not used without verification
 - Stale check: orchestrator checks file mtime during Phase 1 knowledge injection
 - Stale entries are added to the prompt with a "STALE  -  verify before relying" tag
-- `clear-logs` does not touch knowledge  -  only deletes logs and state
+- `prune-logs` does not touch knowledge  -  only deletes logs and state
 - `purge` does not touch knowledge either  -  separate command: `/multi-agent clear-knowledge {project}`
 
 ---

package/pipeline/multi-agent-refs/phases/phase-0-init.md

@@ -406,7 +406,7 @@ git -C $PROJECT_ROOT config user.email "{identity.email}"
 
 `worktreePath` = `$PROJECT_ROOT`, `localMode` = `true`.
 
-**If normal mode** (worktree  -  default): 2. Worktree path: Jira → `.worktrees/{jiraId}/`, GitHub → `.worktrees/GH{issueNo}/`, free-text → `.worktrees/task-{shortId}/` 3. **Heal stale admin state first** (see "Worktree stale-lock heal" below) and **apply the residue guard** (see "Worktree residue guard" below), then `git -C $PROJECT_ROOT worktree add {path} -b {branch} origin/{baseBranch}` (if exists: enter, pull) 4. Set identity: `git -C {worktree-path} config user.name/email` 5. Create log dir + `agent-log.md` + `agent-state.json`:
+**If normal mode** (worktree  -  default): 2. Worktree path: Jira → `.worktrees/{jiraId}/`, GitHub → `.worktrees/GH{issueNo}/`, free-text → `.worktrees/task-{shortId}/` 3. **Heal stale admin state first** (see "Worktree stale-lock heal" below) and **apply the residue guard** (see "Worktree residue guard" below), then `git -C $PROJECT_ROOT worktree add {path} -b {branch} origin/{baseBranch}` (if exists: enter, pull) 4. Set identity: `git -C {worktree-path} config user.name/email` 5. Create log dir + `agent-log.md` + `agent-state.json` at `$HOME/.claude/logs/multi-agent/{project}/{task-id}/`, never inside the worktree:
 
 **Worktree stale-lock heal (required before every `worktree add`):** a run killed mid-`worktree add` (OOM, SIGTERM, disk full) leaves a locked or broken admin entry under `.git/worktrees/{id}/`, so the retry fails with `fatal: '<path>' already exists`. Always run the heal first  -  it is a no-op on a clean repo:
 

package/pipeline/schemas/prefs.schema.json

@@ -184,7 +184,7 @@
             },
             "appstore_connect_key_id": {
               "type": ["string", "null"],
-              "description": "App Store Connect API key ID. Tier 1 of the App Store Connect access chain, used by /multi-agent:testflight-validation Gate 2. An identifier rather than a secret; mapped anyway so every credential is read through the same layer. Creating an API key needs an Admin or App Manager role, which is why Tier 2 exists."
+              "description": "App Store Connect API key ID. Tier 1 of the App Store Connect access chain, used by /multi-agent:store-ready Gate 2 (and its iOS alias /multi-agent:testflight-validation). An identifier rather than a secret; mapped anyway so every credential is read through the same layer. Creating an API key needs an Admin or App Manager role, which is why Tier 2 exists."
             },
             "appstore_connect_issuer_id": {
               "type": ["string", "null"],