@mmerterden/multi-agent-pipeline 8.6.0

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

@@ -0,0 +1,309 @@
+---
+name: multi-agent-setup
+language: tr
+description: "First-run setup wizard: keychain token discovery, Git Identity onboarding, and pipeline preparation."
+user-invocable: true
+---
+
+## Setup (Keychain Token + Git Identity Onboarding)
+
+Self-contained setup — works with inline `security` commands, no external script **required**. If `$HOME/.claude/scripts/keychain-save.sh` exists, it can be used as an interactive alternative but is not mandatory. The `setup` command starts interactive onboarding.
+
+### Step 0 — Language Selection
+
+Ask BEFORE anything else. The pipeline has two language fields:
+
+| Field | Controls | Configurable? |
+|---|---|---|
+| `promptLanguage` | Interactive pickers and prompts during pipeline runs (account, project, branch, channels, Phase 5/6 confirmations) | **No — fixed to `en`.** Picker UI is always English. |
+| `outputLanguage` | The assistant's non-interactive explanations, status updates, error messages, and pipeline-generated reports | Yes — set here, change later via `/multi-agent-language <en\|tr>` |
+
+`promptLanguage` is seeded as `"en"` and never offered to the user. External payloads (commits, PR/Jira/wiki, reviewer/triage prompts, agent-log.md) always stay English regardless.
+
+**Step 0 — outputLanguage** (English UI per skill-prompt rules):
+
+```
+Which language should the assistant use for ITS OWN explanations,
+status updates, and pipeline-generated reports?
+  1) English
+  2) Türkçe
+Select (1-2):
+```
+
+**Rules:**
+
+- Already set in prefs → skip silently. Change later via `/multi-agent-language <en|tr>` or `/multi-agent-language output <en|tr>`.
+- New value → validate against `["en", "tr"]`, atomic write to `prefs.global.outputLanguage`, force `prefs.global.promptLanguage = "en"`, echo confirmation in the chosen `outputLanguage`.
+- Unknown input → re-ask once, then abort with a hint pointing to `/multi-agent-language`.
+
+### Step 1 — Dynamic Keychain Discovery
+
+Instead of checking only hardcoded key names, discover ALL user keys and intelligently map them to services.
+
+**1a. Discover all keys:**
+```bash
+DISCOVERED=$(security dump-keychain 2>/dev/null | grep '"svce"' | awk -F'"' '{print $4}' | grep -i "^${USER}" | sort -u)
+echo "$DISCOVERED"
+```
+
+**1b. Standard key names (convention):**
+
+These are the RECOMMENDED key names. When creating NEW keys, use these. But existing keys under different names are perfectly valid — the discovery step will find them.
+
+| Service ID | Standard Key Name | Search Keywords |
+|------------|------------------|-----------------|
+| `jira` | `${USER}_Jira_Access_Token` | `jira` |
+| `bitbucket_token` | `${USER}_Bitbucket_Access_Token` | `bitbucket` + (`token` or `access` or `pass`) |
+| `bitbucket_user` | `${USER}_Bitbucket_Username` | `bitbucket` + (`user` or `name`) |
+| `github` | `${USER}_Github_Access_Token` | `github` or `gh` (exclude `ssh`) |
+| `confluence` | `${USER}_Confluence_Access_Token` | `confluence` |
+| `figma` | `${USER}_Figma_Access_Token` | `figma` + NOT `mcp` |
+| `figma_mcp` | `${USER}_Figma_Mcp_Access_Token` | `figma` + `mcp` |
+| `fortify` | `${USER}_Fortify_Access_Token` | `fortify` |
+| `firebase` | `${USER}_Firebase_Access_Json` | `firebase` (any variant: `sa`, `service`, `account`, `access`, `json`) |
+| `jenkins` | `${USER}_Jenkins_Access_Token` | `jenkins` |
+
+**1c. Resolution logic (per service):**
+
+For each service in the table above, follow this order:
+
+1. **Check standard key** -> `~/.copilot/lib/credential-store.sh get "<standard_key>" 2>/dev/null`
+   - Found -> auto-map, done
+2. **Search discovered keys** -> filter `$DISCOVERED` by the service's search keywords (case-insensitive)
+   - Exactly 1 match -> show: `"Found '${matched_key}' for ${service} — use this? (enter=yes / n=skip)"` -> if yes, map it
+   - Multiple matches -> show numbered list, user picks:
+     ```
+     Multiple keys found for GitHub:
+       1. ${USER}_Github
+       2. ${USER}_Github_Access_Token_Old
+       3. ${USER}_Github_Access_Token
+     Select [number] or skip:
+     ```
+   - 0 matches -> MISSING
+
+**1d. Check preferences for existing mapping:**
+
+Before running discovery, check `prefs.global.keychainMapping`. If a mapping already exists for a service AND the mapped key still exists in Keychain -> skip discovery for that service (show as already mapped from preferences).
+
+If a previously mapped key NO LONGER exists in Keychain -> clear the stale mapping, re-run discovery for that service.
+
+### Step 2 — Show Discovery Summary + Save Mapping
+
+Show results grouped by status:
+
+```
+Keychain Token Discovery (${USER}):
+
+  Jira               -> ${USER}_Jira_Access_Token
+  GitHub             -> ${USER}_Github
+  Figma              -> ${USER}_Figma_Access_Token
+  Firebase           -> ${USER}_Firebase_Access_Json
+  Confluence         -> MISSING
+  Jenkins            -> MISSING
+  ---
+  Git identities: check preferences file (see Step 3)
+
+  Mapped: 8 | Missing: 4
+```
+
+Save the resolved mapping to preferences:
+```json
+{
+  "global": {
+    "keychainMapping": {
+      "jira": "${USER}_Jira_Access_Token",
+      "bitbucket_token": "${USER}_Bitbucket_Access_Token",
+      "bitbucket_user": "${USER}_Bitbucket_Username",
+      "github": "${USER}_Github",
+      "confluence": null,
+      "figma": "${USER}_Figma_Access_Token",
+      "figma_mcp": "${USER}_Figma_Mcp_Access_Token",
+      "fortify": null,
+      "firebase": "${USER}_Firebase_Access_Json",
+      "jenkins": null
+    }
+  }
+}
+```
+
+`null` = not mapped (missing or skipped). Pipeline phases read this mapping to retrieve tokens dynamically — never hardcoded key names.
+
+### Step 3 — Jira Project Key (auto-learned)
+
+Jira project keys are NOT asked during setup. They are auto-learned from pipeline usage:
+- User runs `/multi-agent ABC-123` → `ABC` is extracted and saved to `prefs.global.defaultJiraKey` (first ever) and `prefs.projects[{project}].jiraProjectKeys` (per-project).
+- User later runs `/multi-agent MOBILE-456` in a different project → `MOBILE` is added to that project's keys.
+- Multiple keys accumulate over time — most recent first, deduped.
+
+Phase 0 Step 1 (Parse Input) handles extraction and persistence. No setup interaction needed.
+
+### Step 4 — Git Identity Setup (one-time)
+
+Git identities are NOT secrets — stored in the preferences file, not Keychain:
+
+```bash
+PREFS_FILE="$HOME/.claude/multi-agent-preferences.json"
+```
+
+If no identities exist in `prefs.global.gitIdentities` (first run):
+```
+Let's set up git identity.
+
+Identity 1 (corporate):
+  Author name: ___
+  Email: ___
+
+Add another identity? (y/n)
+
+Identity 2 (personal):
+  Author name: ___
+  Email: ___
+```
+
+Save to preferences JSON:
+```json
+{
+  "global": {
+    "gitIdentities": [
+      {"name": "AUTHOR_NAME", "email": "AUTHOR_EMAIL"},
+      {"name": "AUTHOR_NAME_2", "email": "AUTHOR_EMAIL_2"}
+    ]
+  }
+}
+```
+
+Show result:
+```
+Git Identities (saved to preferences):
+  1. {Full Name - Organization} <{corporate@email.com}>
+  2. {Full Name} <{personal@email.com}>
+```
+
+### Step 5 — Interactive token onboarding (for missing tokens)
+
+For each MISSING service, run the **Token Save Flow** (see `setup.md` for full spec).
+
+Summary: ask `[1] Add now / [2] Skip` → if add, user copies token to clipboard, presses Enter → pipeline reads from clipboard via `pbpaste`, saves to Keychain, clears clipboard. Token never appears in terminal.
+
+The same flow is reused at Phase 0 runtime when a token is expired (401/403).
+
+### Step 6 — Verify all
+
+Re-run scan from Step 1. Show final status:
+```
+All tokens present. Pipeline ready to use.
+
+Optional per-project features (configured on first use, nothing to do now):
+  • Phase 7 Report Step 2 Wiki — auto-generates component wiki pages + Figma
+    screenshots. Activates when (a) task is a component AND (b) a Figma token
+    is in Keychain. Four adapters supported: submodule / in-repo / github-wiki
+    / separate-repo. First run asks: use auto-detected path, use a custom
+    path, skip once, or disable for this project (persisted).
+  • channels — post-hoc multi-channel reporter (Jira/Confluence/Wiki/PR), works on any branch with an open PR. v5.7+ replaces the older `enrich` command.
+  • Default reviewers — auto-fetched from Bitbucket default-reviewers endpoint
+    or GitHub CODEOWNERS on first PR.
+
+Next step:
+  /multi-agent "PROJ-12345"              -> start your first task
+  /multi-agent help                      -> full usage guide
+```
+
+If still missing, show which ones and let user skip (pipeline will re-ask for any needed token at Phase 0).
+
+### Token -> Source Mapping
+
+Standard key names (used when creating NEW tokens). Discovery may find existing keys under different names — that's fine, the mapping in preferences handles it.
+
+| Service ID | Standard Key Name | Type | Where to Get |
+|------------|------------------|------|---------------|
+| `jira` | `${USER}_Jira_Access_Token` | PAT | Jira -> Profile -> Personal Access Tokens (VPN required) |
+| `bitbucket_token` | `${USER}_Bitbucket_Access_Token` | App Password | Bitbucket -> Personal settings -> App passwords |
+| `bitbucket_user` | `${USER}_Bitbucket_Username` | Plain text | Bitbucket profile username |
+| `github` | `${USER}_Github_Access_Token` | PAT | GitHub Settings -> Tokens (scopes: repo, read:org, project) |
+| `confluence` | `${USER}_Confluence_Access_Token` | PAT | Confluence -> Profile -> Personal Access Tokens (VPN required) |
+| `figma` | `${USER}_Figma_Access_Token` | PAT | Figma Developer Settings (max 90 days) |
+| `figma_mcp` | `${USER}_Figma_Mcp_Access_Token` | OAuth | Automatic via Claude Code Figma MCP remote auth |
+| `fortify` | `${USER}_Fortify_Access_Token` | API Token | Fortify SSC -> Token Management (VPN required) |
+| `firebase` | `${USER}_Firebase_Access_Json` | Firebase JSON (base64) | Firebase Console -> Project settings -> Service accounts -> Generate new private key. Project id is parsed from the decoded JSON. |
+| `jenkins` | `${USER}_Jenkins_Access_Token` | API Token | Jenkins -> User -> Configure -> API Token |
+| — | Git Identities | JSON (preferences) | Stored in `$HOME/.claude/multi-agent-preferences.json` — not Keychain |
+
+### Inline Token Save Pattern
+
+All tokens go through `~/.copilot/lib/credential-store.sh`, which auto-delegates to `~/.copilot/scripts/keychain.py` on macOS / Linux and the PowerShell `CredentialManager` module on Windows. The Python path writes both `-l` (label) and `-s` (service) attributes so existing manually-added entries with either convention remain findable.
+
+```bash
+# PAT / API Key (from clipboard)
+pbpaste | ~/.copilot/lib/credential-store.sh set "<SERVICE_NAME>" "$(cat)"
+pbcopy < /dev/null  # clear clipboard
+
+# Plain text (direct value)
+~/.copilot/lib/credential-store.sh set "<SERVICE_NAME>" "<VALUE>"
+
+# JSON file (base64 encode)
+~/.copilot/lib/credential-store.sh set "<SERVICE_NAME>" "$(base64 < /path/to/file.json)"
+
+# Read
+~/.copilot/lib/credential-store.sh get "<SERVICE_NAME>"
+
+# Decode JSON
+~/.copilot/lib/credential-store.sh get "<SERVICE_NAME>" | base64 -d
+```
+
+For maximum stdin hygiene (the secret never lands on argv / shell history), use the Python helper directly with the `-` sentinel:
+
+```bash
+pbpaste | ~/.copilot/scripts/keychain.py set "<SERVICE_NAME>" -
+```
+
+### Figma MCP Setup (optional)
+
+Figma MCP works in two modes:
+
+**Remote MCP** (Claude Code built-in):
+- Automatic — comes as `claude_ai_Figma` in Claude Code settings.json
+- If token renewal needed: re-auth from within Claude Code
+
+**Local MCP** (@anthropic-ai/figma-mcp package, with PAT):
+```bash
+# 1. Save PAT to keychain
+security delete-generic-password -a "$USER" -s "${USER}_Figma_Access_Token" 2>/dev/null
+security add-generic-password -a "$USER" -s "${USER}_Figma_Access_Token" -w "$(pbpaste)"
+pbcopy < /dev/null
+
+# 2. Add MCP to Claude Code settings.json
+# ~/.claude/settings.json -> mcpServers -> figma
+```
+
+### Security Rules
+
+- Never paste tokens into terminal or chat — use `pbpaste` for input
+- Never hardcode tokens in source code
+- Never commit tokens to git history
+- Clear clipboard immediately: `pbcopy < /dev/null`
+- `2>/dev/null` suppresses stderr (prevents metadata leakage)
+
+### Setup from Scratch Summary
+
+To set up multi-agent on a new machine:
+
+```
+1. Install the toolkit:
+   npx @mmerterden/multi-agent-pipeline install
+
+2. Start setup:
+   /multi-agent setup
+
+3. Interactive flow:
+   -> Token scan (shows what is missing)
+   -> Git Identity creation (name + email)
+   -> Inline commands for missing tokens
+   -> Final verification
+
+4. Ready:
+   /multi-agent "PROJ-12345"
+   /multi-agent "https://github.com/.../issues/42"
+   /multi-agent "bug description"
+```
+
+All tokens are optional — pipeline will ask for any needed token at Phase 0. Setup only does pre-preparation.

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

@@ -0,0 +1,55 @@
+---
+name: multi-agent-stack
+language: tr
+description: "Manually switch the active skill set by platform (ios/android/mobile/backend/frontend/fullstack/all)."
+user-invocable: true
+---
+
+# multi-agent stack — Manual Stack Swap
+
+`pipeline/scripts/stack-swap.sh` SessionStart hook'u stack'i projeye göre otomatik tespit eder. Bu komut o kararı manuel olarak geçersiz kılar — aktif skill setini değiştirir ve eşleşmeyen skill'leri `skills-inactive/`'e taşır.
+
+## Usage
+
+```bash
+multi-agent-stack                  # mevcut durumu göster
+multi-agent-stack ios              # SwiftUI + Xcode
+multi-agent-stack android          # Compose + Gradle
+multi-agent-stack mobile           # iOS + Android birlikte
+multi-agent-stack backend          # Python / Node / Go
+multi-agent-stack frontend         # React / Vue / Next
+multi-agent-stack fullstack        # backend + frontend
+multi-agent-stack all              # hepsini aktif et
+```
+
+## Behaviour
+
+1. Arg yoksa → status modu: aktif skill sayısını göster, herhangi bir dosya taşıma **yapma**.
+2. Arg varsa → `stack-swap.sh <arg>` çalıştır.
+3. Script stdout'u JSON (`{"systemMessage": "..."}`) — kullanıcıya `systemMessage` değerini yazdır.
+4. Bilinmeyen arg → script `exit 1` + hata mesajı döner; değeri tekrar sorma, kullanıcıya listeyi göster.
+
+## Implementation
+
+```bash
+# Both CLIs install pipeline scripts under their own home dir. Prefer Copilot's
+# own scripts if present; fall back to Claude Code's scripts when running under
+# --all install (shared machine, either CLI's copy is up-to-date).
+if [ -x "$HOME/.copilot/scripts/stack-swap.sh" ]; then
+  SCRIPT="$HOME/.copilot/scripts/stack-swap.sh"
+elif [ -x "$HOME/.claude/scripts/stack-swap.sh" ]; then
+  SCRIPT="$HOME/.claude/scripts/stack-swap.sh"
+else
+  echo "stack-swap.sh not found — run install.js --copilot (or --all) to deploy pipeline scripts."
+  exit 1
+fi
+
+ARG="${1:-status}"
+"$SCRIPT" "$ARG"
+```
+
+## Notes
+
+- Manuel swap anlık etki eder ama Copilot CLI'ın skill keşfini tam yenilemek için **konuşmayı yeniden başlat**.
+- Auto-detect tekrar devreye girsin istersen sonraki SessionStart yeterli — hook `cwd`'a bakıp tekrar karar verir. Manuel override kalıcı değildir.
+- Pipeline Phase 1 stack tespiti bu komuttan bağımsızdır (proje dosyalarına bakar). `stack` sadece hangi skill set'inin aktif olduğunu etkiler.

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

@@ -0,0 +1,41 @@
+---
+name: multi-agent-status
+language: tr
+description: "Show every multi-agent task's ID, phase, branch, and status."
+user-invocable: true
+---
+
+# multi-agent status — Task Status Dashboard
+
+Show every active and completed task as a table.
+
+## Steps
+
+1. **Proje tespit et** — cwd'deki repo kökünü bul (yoksa tüm bilinen repo'lara bak):
+   - `~/my-ui-components/.worktrees/`
+   - `~/my-figma-app/.worktrees/`
+   - `~/my-ios-app/.worktrees/`
+
+2. **Worktree'leri tara** — Her worktree dizininde `agent-state.json` dosyasını oku:
+   ```bash
+   find {repo}/.worktrees/ -name "agent-state.json" -maxdepth 2
+   ```
+
+3. **State parse et** — Her task için:
+   - `taskId`, `branch`, `currentPhase`, `status`, `startedAt`, `autopilot`
+
+4. **Tablo formatında göster**:
+   ```
+   🤖 Multi-Agent Tasks
+
+   | ID | Jira/Task | Branch | Phase | Status | Duration |
+   |----|-----------|--------|-------|--------|----------|
+   | #1 | PROJ-133139 | feature/PROJ-133139-... | 7/7 DONE | ✅ Complete | 12m |
+   | #3 | PROJ-133408 | feature/PROJ-133408-... | 7/7 DONE | ✅ Complete | 8m |
+
+   💡 log #1 | resume #N | kill #N
+   ```
+
+5. **Kısa komut önerileri** — Duruma göre:
+   - Paused task varsa → `resume #N` öner
+   - Done task varsa → `log #N` öner

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

@@ -0,0 +1,184 @@
+---
+name: multi-agent-sync
+language: en
+description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and remote-control."
+user-invocable: true
+argument-hint: 'release | "degisiklik aciklamasi"'
+---
+
+# Multi-Agent Sync
+
+**Tek komut. Full ecosystem sync. Arguman gerekmez.**
+
+Cagrildiginda 6 hedefin tamamini sirayla senkronize eder. Neyin degistigini algilar, sadece stale olanlari gunceller, sonuc raporu verir.
+
+**Input**: $ARGUMENTS (opsiyonel — `release` veya tum hedeflere uygulanacak degisiklik aciklamasi)
+
+## Hedefler (her zaman 6'si birden)
+
+| # | Hedef | Yol | Yon |
+|---|-------|-----|-----|
+| 0 | Figma source (opt-in) | `prefs.global.figmaSource.path` -> `pipeline/skills/figma-ios/` + `figma-common/` | <- upstream |
+| 1 | Claude Code (source of truth) | `~/.claude/commands/multi-agent.md` + `~/.claude/commands/multi-agent/` + `~/.claude/agents/` + `~/.claude/scripts/` | kaynak |
+| 2 | Copilot CLI | `~/.copilot/copilot-instructions.md` + `~/.copilot/skills/` | <- Claude'dan |
+| 3 | multi-agent-pipeline repo | `~/multi-agent-pipeline/pipeline/` | <- Claude'dan (genericized) |
+| 4 | Website | `{owner}/{website-host}` | <- versiyon + ozellikler |
+| 5 | Remote Control | `{owner}/remote-control` | <- pipeline referanslari |
+
+## Varsayilan Davranis (argumansiz)
+
+Tum adimlari otomatik calistir:
+
+```
+Adim 0: FIGMA_SYNC  (opt-in) pipeline/scripts/sync-figma-source.sh
+                    -- figmaSource.path set ise upstream'den incremental pull
+Adim 1: DETECT      Timestamp karsilastir, stale hedefleri bul
+Adim 2: COPILOT     Claude Code -> Copilot CLI (instructions + 26 sub-command skills)
+Adim 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub)
+Adim 4: WEBSITE     Versiyon + faz/model sayilari -> {website-host} (i18n + projects.ts)
+Adim 5: REMOTE      Pipeline referanslari -> remote-control README
+Adim 6: Commit      Degisen tum repolari commit + push
+Adim 7: Report      Ozet: sync edilen hedefler, degisen dosyalar, deploy durumu
+```
+
+Hicbir sey stale degilse -> "Tum hedefler guncel" raporla ve dur.
+
+## Special inputs
+
+| Girdi | Davranis |
+|-------|----------|
+| (argumansiz) | Full ecosystem sync (varsayilan) |
+| `release` | Full sync + versiyon bump + tag + npm publish + website deploy |
+| `"degisiklik aciklamasi"` | Aciklamayi TUM hedeflere ayni anda uygula |
+
+
+## Sync rules
+
+1. **Once oku** — Degisiklik yapmadan once tum hedeflerin mevcut durumunu anla
+2. **Dosya yapisini koru** — Her hedefin kendi formati var:
+   - `multi-agent.md` + phases/: detayli pipeline spec (frontmatter, phases, routing)
+   - `copilot-instructions.md`: genel gelistirme talimatlari + pipeline ozet bolumu
+   - `multi-agent-pipeline/pipeline/`: generic acik kaynak versiyonu (kisisel veri YOK)
+3. **Shared section'lari sync et** (Claude <-> Copilot):
+   - Pipeline modlari tablosu (normal / autopilot / --dev / --dev autopilot)
+   - Proje tespiti (URL-based + cwd-based)
+   - Figma pipeline akisi
+   - Git conventions (author, branch, commit format)
+   - --dev mode model bilgisi (Opus)
+   - Keychain yonetimi (registry, naming convention, multi-agent pattern)
+4. **Duplike etme** — Copilot'ta ozet, Claude'da full spec. Bu ayrimi koru.
+5. **Rapor ver** — Sync sonrasi kisa diff ozeti goster
+
+## Pipeline Repo Sync Kurallari (KRITIK)
+
+1. **Kaynak**: `~/.claude/commands/multi-agent.md` + `~/.claude/commands/multi-agent/` + `~/.claude/agents/`
+2. **Hedef**: `~/multi-agent-pipeline/pipeline/`
+3. **Genericization** (hedefe yazmadan ONCE uygulanmali):
+   - Jira proje key'i (`prefs.global.defaultJiraKey`) -> `{JIRA_KEY}`, orneklerde `PROJ`
+   - Kisisel isimler/emailler -> generic placeholder
+   - Branch isimleri -> `develop`
+   - Proje isimleri -> `my-app`
+   - `{JIRA_HOST}`, `{BITBUCKET_HOST}`, `{CONFLUENCE_HOST}`, `{CORP_DOMAIN}` oldugu gibi kalir
+   - **Dogrula**: `grep` ile pipeline/ icinde kisisel/kurumsal veri taramasi -> 0 sonuc
+4. **Dosya esleme**:
+   ```
+   ~/.claude/commands/multi-agent.md      -> pipeline/commands/multi-agent.md
+   ~/.claude/commands/multi-agent/        -> pipeline/commands/multi-agent/
+   ~/.claude/commands/sim-test.md         -> pipeline/commands/sim-test.md
+   ~/.claude/agents/*.md                  -> pipeline/agents/
+   ```
+5. **Sync EDILMEYEN dosyalar** (local-only, kisisel veri icerebilir):
+   - `~/.claude/multi-agent-preferences.json`
+   - `~/.claude/CLAUDE.md`, `~/.claude/rules/`, `~/.claude/knowledge/`
+   - `~/.claude/scripts/` — `pre-commit-check.sh` ve `stack-swap.sh` HARIC (generic, sync edilir)
+   - `~/.claude/settings.json`
+
+
+## Website Sync (Adim 4)
+
+Pipeline versiyon, faz sayisi, model sayisi ve ozellik aciklamalarini website'a propagate et.
+
+```bash
+gh auth switch --user {owner}
+WEBSITE_DIR="$HOME/{website-host}"
+[ ! -d "$WEBSITE_DIR" ] && gh repo clone {owner}/website "$WEBSITE_DIR"
+cd "$WEBSITE_DIR" && git pull origin main
+```
+
+| Dosya | Sync edilecek |
+|-------|--------------|
+| `src/lib/i18n.tsx` | Faz sayisi, model sayisi, ozellik aciklamalari (EN + TR) |
+| `src/data/projects.ts` | Versiyon numarasi, tagline, aciklama, ozellik listesi |
+
+```bash
+cd "$WEBSITE_DIR"
+git add -A && git commit -m "chore: sync pipeline v{VERSION}"
+git push origin main  # Vercel auto-deploy
+```
+
+
+## Remote Control Sync (Adim 5)
+
+```bash
+REMOTE_DIR="$HOME/remote-control"
+[ ! -d "$REMOTE_DIR" ] && gh repo clone {owner}/remote-control "$REMOTE_DIR"
+cd "$REMOTE_DIR" && git pull origin main
+```
+
+| Dosya | Sync edilecek |
+|-------|--------------|
+| `README.md` | Pipeline ozellik aciklamasi |
+| `src/index.ts` | Help text / chip label'lari (varsa) |
+
+Sadece pipeline'in public-facing ozellikleri degistiyse guncelle.
+
+
+## Release Akisi
+
+`release` argumaniyla cagrildiginda:
+
+```
+1. REPO          Claude Code -> pipeline repo (genericized)
+2. VERIFY        Kisisel veri taramasi -> 0 sonuc
+3. LINT + TEST   ESLint + smoke tests
+4. VERSION       package.json version bump (patch/minor/major)
+5. Commit + TAG  git commit + git tag v{VERSION}
+6. PUSH          git push --tags -> release.yml auto-publish
+7. WEBSITE       Versiyon + ozellikler -> {website-host}
+8. REMOTE        remote-control referanslari guncelle
+9. COPILOT       Copilot CLI instructions + skills sync
+10. Report        Ozet: versiyon, dokunulan repolar, deploy durumu
+```
+
+
+## Sub-Command Sync (Claude Code <-> Copilot CLI Skills)
+
+| Claude Code | Copilot CLI |
+|-------------|-------------|
+| `~/.claude/commands/multi-agent/{cmd}.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
+
+**26 komut sync edilir** (v7.0.0+ canonical inventory — `cross-cli-contract.md` §1 ile eşleşmeli, drift = contract violation):
+
+```
+autopilot, channels, dev, dev-autopilot, dev-local, dev-local-autopilot,
+help, issue, jira, kill, local, local-autopilot, log, manual-test, purge,
+refactor, resume, review, scan, search, setup, stack, status, sync, test, update
+```
+
+**Sync EDILMEZ**: `refs/*` — Lazy-load referanslari, Claude Code'a ozel
+
+**Claude -> Copilot**: SKILL.md frontmatter ekle (`name`, `description`, `user-invocable: true`, `argument-hint`)
+**Copilot -> Claude**: Frontmatter'i basitlestir (`description` + `allowed-tools`), `$ARGUMENTS` ekle
+
+
+## Keychain Token Erisimi
+
+| Islem | Token Kaynagi |
+|-------|---------------|
+| `gh` CLI (personal) | `{owner}` gh auth (Keychain) |
+| `gh` CLI (work) | `${USER}_{work-gh-alias}` gh auth (Keychain) |
+| npm publish | `NODE_AUTH_TOKEN` — CI'da `GITHUB_TOKEN`, local'de Keychain PAT |
+
+```bash
+gh auth switch --user {owner}  # personal repolar icin
+```

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

@@ -0,0 +1,44 @@
+---
+name: multi-agent-test
+language: en
+description: "UI Bug Hunter — iOS Simulator (simctl) + Android Emulator (adb). Auto-detects platform. Screenshot + tap + analyze on the booted device. The Phase 5 Manual Test flow lives at multi-agent-manual-test."
+user-invocable: true
+argument-hint: '[scenario] — e.g. "dark mode" | "accessibility" | "dynamic type" | "screenshot tr" | "store-ready" | (empty = full sweep)'
+---
+
+# multi-agent-test — UI Bug Hunter
+
+Mobile UI test runner. Boots a simulator / emulator, drives it via MCP tools, and audits the running app for visual / accessibility / platform issues. Auto-detects iOS vs Android from cwd.
+
+**Input**: $ARGUMENTS (optional — test scenario tag).
+
+## Dispatcher
+
+This skill delegates to the full UI Bug Hunter flow. Read and follow:
+
+```
+$HOME/.copilot/multi-agent/sim-test.md
+```
+
+(Equivalent on Claude Code: `$HOME/.claude/commands/sim-test.md`.)
+
+Pass `$ARGUMENTS` through verbatim — the target doc picks the right test matrix based on the argument.
+
+## 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 |
+
+## 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__*`)
+
+For the Phase 5 manual test mode (branch checkout + Xcode hint), use `multi-agent-manual-test` instead.

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

@@ -0,0 +1,34 @@
+---
+name: multi-agent-update
+language: tr
+description: "Update the pipeline to the latest version: git pull, install, migrate."
+user-invocable: true
+argument-hint: ""
+---
+
+# multi-agent-update — Pipeline Güncelleme
+
+Tek komutla pipeline'ı güncelle. Preferences korunur, sadece skill/script/schema dosyaları yenilenir.
+
+## Steps
+
+1. Pipeline repo'yu bul (`~/multi-agent-pipeline` veya `~/dev/multi-agent-pipeline`)
+2. Mevcut versiyonu kaydet
+3. `git pull origin main`
+4. `node install.js --all` (Claude + Copilot)
+5. `node migrate-prefs.mjs` (schema upgrade varsa)
+6. Yeni versiyonu göster + changelog
+7. Smoke test (schema + cross-cli)
+
+## Usage
+
+```
+/multi-agent-update
+```
+
+Çıktı:
+```
+v3.6.0 → v3.7.0 güncellendi
+  5 commit, 25 dosya değişti
+  schema-validation: 27/27 pass
+```