@mmerterden/multi-agent-pipeline 11.1.0 → 11.3.0

package/pipeline/skills/figma-common/README.md

@@ -1,64 +0,0 @@
-# figma-common  -  Platform-agnostic figma-to-component skills
-
-Shared skills that both `pipeline/skills/figma-ios/` (SwiftUI) and `pipeline/skills/figma-android/` (Jetpack Compose) dispatch. Moved here by WS-7b of the v5.0.0 rebuild so the platform trees stay lean and there's no duplication.
-
-## What lives here (31 skills)
-
-**Workflow orchestration:**
-
-- `figma-component-start`  -  Issue → branches, check out worktree
-- `figma-component-confluence-sync`  -  Phase 7b: wiki markdown → Confluence XHTML
-- `figma-component-status-update`  -  Refresh Confluence dashboard
-- `figma-commit`  -  14-item review + PR creation
-- `figma-iteration-commit`  -  Commit to iteration/develop + PR
-
-**Batch + iterate:**
-
-- `figma-iterate`  -  Auto loop: pick → implement → commit
-- `figma-cli-iterate`  -  Full CLI iterate (all phases)
-- `figma-cli-lean-iterate`  -  Iterate skipping test + wiki
-- `figma-cli-iterate-mend`  -  Re-implement discarded components
-- `figma-cli-skip`  -  Mark component as skipped
-- `figma-skip`  -  Skip + update Confluence dashboard
-
-**Issue + review:**
-
-- `figma-issue`  -  Create GitHub issue + optional Jira (feeds WS-6 triad)
-- `figma-review`  -  Interactive review gate (approve / bug / skip)
-- `figma-validate`  -  Pre-implementation validation
-- `figma-fix`  -  Targeted bug fix from review findings
-- `figma-mend`  -  Re-implement component from scratch
-- `figma-evolve-component`  -  Reconcile drift + additively extend an existing component (human-gated)
-
-**Setup + utility:**
-
-- `figma-setup`  -  Environment setup wizard (MCP, tokens, Code Connect CLI)
-- `figma-remote-mcp-auth`  -  Figma MCP OAuth flow
-- `figma-utility`  -  Figma data fetch (screenshots, metadata)
-- `figma-ui-patterns`  -  UI pattern library index
-- `figma-form-integration`  -  Form protocol adapter (shared UX)
-- `figma-price-integration`  -  Price protocol adapter (shared UX)
-
-**Cross-cutting interaction adapters (dual-platform: iOS SwiftUI + Android Jetpack Compose; native-first; project system via `figma-config` `ui.*`):**
-
-- `figma-navigation`  -  Navigation pattern: headless Output vs self-route; native `NavigationStack` or `ui.navigationSystem`
-- `figma-overlays`  -  Overlay pattern: toast/HUD/alert/data-modal; native `.alert`/`.sheet(item:)` or `ui.overlaySystem`
-- `figma-bottom-sheets`  -  Bottom-sheet/detent pattern: native `.presentationDetents` or `ui.sheetSystem`
-
-**Performance batch:**
-
-- `performance-start`, `performance-swiftui`, `performance-tour`, `performance-review-next`, `performance-iteration-commit-all`
-
-## What does NOT live here
-
-Platform-specific skills stay under `figma-ios/` or `figma-android/`:
-
-- `figma-to-component`  -  orchestrator (platform-specific build command)
-- `figma-component-implement`  -  Swift / Kotlin code generator
-- `figma-component-test`  -  SwiftUI ViewInspector / Compose Testing
-- `figma-component-code-connect`  -  Swift / Kotlin Code Connect
-- `figma-component-wiki`  -  same 4-adapter contract, but platform-aware rendering
-
-## Invocation
-
-Both platforms' orchestrators call the same common skill paths  -  no CLI or platform routing needed. The cross-CLI contract (`refs/cross-cli-contract.md` section 1.1) enforces the inventory.

package/pipeline/skills/figma-common/figma-bottom-sheets/SKILL.md

@@ -1,152 +0,0 @@
----
-name: figma-bottom-sheets
-description: "Bottom-sheet / detent pattern integration for Figma-to-UI components (iOS SwiftUI + Android Jetpack Compose) — half-sheets, drawers, pinned bottom CTAs, resizable pull-up panels, content-sized sheets, and multi-step in-sheet flows. Native by default (SwiftUI .sheet+presentationDetents; Compose ModalBottomSheet + rememberModalBottomSheetState); an optional project-supplied detent-sheet system when figma-config declares one. Reach for this when a design shows a bottom sheet, half-sheet, bottom drawer, snap points, a sticky footer button, or a wizard-in-a-sheet."
-user-invocable: true
-allowed-tools: Read, Glob, Grep
-status: wip-v5
-sourced-from: upstream/figma-bottom-sheets
----
-
-# /figma-bottom-sheets  -  Bottom-Sheet / Detent Pattern Integration
-
-## Purpose
-
-Consumed by the figma-to-swiftui pipeline (Phase 3D detection, Phase 4B view) and available ad-hoc, this skill defines how **bottom-anchored, detent-based surfaces** are presented. Sibling of `/figma-overlays` (transient/blocking overlays) and `/figma-navigation` (routing): native-SwiftUI default + a config-driven hook for projects that ship a custom detent-sheet engine.
-
-**Generic by design.** Default is stock SwiftUI `.sheet` + `.presentationDetents`. If `figma-config.json` declares `ui.sheetSystem`, route through that engine by name  -  same rules, project vocabulary. (Some apps replace system sheets because iOS 26 forces a Liquid-Glass floating inset on partial detents with no removal API; that replacement is the custom-system case, not the default.)
-
----
-
-## Strict Rules (non-negotiable)
-
-1. **The sheet surface is a caller concern; the component is the content.** A reusable component authored from Figma is the sheet's **content**, not the presenter. The caller owns the `isPresented`/`item` binding and the detents. A component that presents itself can't be reused elsewhere.
-2. **No magic numbers.** Detents, corner radius, grabber size, insets come from tokens / figma-config token patterns, never hard-coded literals.
-3. **Detents ascend, max 3.** Pass `[detent]` lowest→highest; the sheet opens at the lowest. Prefer semantic detents (`.medium`, `.large`, `.fraction`, content-height) over pixel heights where possible.
-4. **A bottom sheet is not a modal card and not a navigation push.** Data alert/modal card → `/figma-overlays`; screen routing → `/figma-navigation` (a routed modal may still *render* as a sheet, but navigation owns the routing).
-5. **Native SwiftUI is the default; a custom sheet engine is opt-in via config.** Only use a project detent-sheet system when `ui.sheetSystem.mode == "custom"`.
-
----
-
-## When to Invoke This Skill
-
-1. **Phase 3D  -  sheet affordance/pattern:** the design is (or contains) a bottom sheet / half-sheet / drawer, a **pinned bottom CTA** bar, a resizable pull-up panel, a **content-sized** sheet, or a **multi-step** in-sheet flow (in-sheet back/next that resizes per step).
-2. **Phase 4B  -  View:** the view is authored as sheet content, or presents a child as a sheet.
-3. **Ad-hoc:** "half sheet", "bottom drawer", "pull-up panel", "snap points", "sticky footer button", "multi-step sheet", "sheet sized to its content".
-
-**Not a bottom sheet (guards):**
-- Toast / HUD / alert / data modal card → `/figma-overlays`.
-- Full screen navigation / tab / deep link → `/figma-navigation`.
-- An inline expandable section within the page flow (not an anchored surface) → plain component content.
-
----
-
-## Native-first architecture (default)
-
-```
-Caller
-    |  owns isPresented / item + detents; presents the component as content
-    v
-.sheet(item:/isPresented:) {
-    ComponentContent()                    // the Figma-authored component
-      .presentationDetents([.medium, .large])
-      .presentationDragIndicator(.visible)
-      .presentationBackgroundInteraction(.enabled(upThrough: .medium))  // passthrough-ish
-      .presentationCornerRadius(<token>)
-}
-```
-
-- **Half / expandable:** `.presentationDetents([.medium, .large])` or `[.fraction(0.25), .fraction(0.6), .large]`.
-- **Content-sized:** `.presentationDetents([.height(measuredHeight)])` using a height read via a preference key (a `sizeThatFits`/`GeometryReader` measured content height), then scroll past the cap.
-- **Pinned bottom CTA (part of the screen, not a modal):** `.safeAreaInset(edge: .bottom) { CTA() }`  -  reserves space, screen stays interactive. This is NOT a presented sheet.
-- **Backdrop behavior:** dim+block is the `.sheet` default; passthrough/interactive-behind uses `.presentationBackgroundInteraction(.enabled(...))`.
-- **Multi-step in-sheet flow:** drive a `NavigationStack(path:)` *inside* the sheet content for push/pop, resizing detents per step; each step is a headless view emitting `Output` (see `/figma-navigation`). If the target project's custom engine forbids a nested `NavigationStack`, use its engine (config hook).
-- **Overlays over a sheet:** mount the toast/HUD host on the sheet content (`/figma-overlays`), not the root.
-
-Tokens per `reference/ui` + figma-config token patterns.
-
-## Config hook  -  project-supplied detent-sheet engine
-
-When `figma-config.json` declares:
-```jsonc
-"ui": { "sheetSystem": {
-  "mode": "custom",
-  "brandedModifier": "bottomSheet",       // .bottomSheet(isPresented:title:) branded entry
-  "headlessModifiers": ["modalSheet", "dockedSheet", "expandableSheet", "detentNavigationSheet"],
-  "detentType": "SheetDetentType",         // detent enum
-  "backdropType": "Backdrop",              // backdrop enum
-  "cornerRadiusToken": ".CornerRadius.radius12"   // example: your branded top-corner radius token
-}}
-```
-apply the SAME rules via the project's engine (names from config, do NOT hardcode):
-- Use `.{brandedModifier}` for product sheets needing brand chrome; the headless modifiers for unbranded surfaces / CTAs / resizable panels / multi-step flows.
-- Detents/backdrops use `{detentType}`/`{backdropType}` values; corner radius from `{cornerRadiusToken}`.
-- Multi-step flows use the engine's navigation sheet (e.g. `detentNavigationSheet` with a `Navigator<Route>`) rather than a raw nested `NavigationStack`.
-- One container-owned grabber (pass custom headers grabberless if the engine draws the grabber).
-- Present only from the surface's own host  -  never walk the scene/window hierarchy for a "top" controller.
-
-If `mode` is absent or `native`, use the native-first section.
-
-## Android (Jetpack Compose)
-
-Same rules, Compose vocabulary. Default is Material3; a project sheet engine is used only when `ui.sheetSystem.mode == "custom"`.
-
-- **Half / expandable / drawer:** `ModalBottomSheet(onDismissRequest = { showSheet = false }, sheetState = rememberModalBottomSheetState(skipPartiallyExpanded = false)) { Content() }`. The caller owns `var showSheet by remember` and the `SheetState`; the Figma-authored composable is the **content**.
-- **Detents / snap points:** Material3 exposes partial + expanded (`skipPartiallyExpanded`, `SheetValue`); for finer snap points use an `AnchoredDraggable`-based sheet. Don't hard-code pixel heights  -  derive from content / fractions.
-- **Content-sized:** let the content wrap-height; the sheet grows to content then scrolls (inner `Column`/`LazyColumn` with `verticalScroll`).
-- **Pinned bottom CTA (part of the screen, not a sheet):** `Scaffold(bottomBar = { CTA() })`  -  reserves space, screen stays interactive. Not a `ModalBottomSheet`.
-- **Multi-step in-sheet flow:** host a nested `NavHost` (or step state) inside the sheet content, resizing per step; each step is a headless composable emitting events (see `/figma-navigation`).
-- **Overlays over the sheet:** show `Snackbar`/`AlertDialog` scoped to the sheet content (`/figma-overlays`), not the root.
-
-**Config hook:** `ui.sheetSystem.mode == "custom"` → use the project's `{brandedModifier}` / headless composables + `{detentType}` / `{backdropType}` and radius from `{cornerRadiusToken}`, resolved from config.
-
-Corner radius / grabber / insets from tokens (`MaterialTheme.shapes` / figma-config), not literals.
-
----
-
-## Integration with Phase 3D
-
-Record in `04b_component_architecture.md`:
-
-```markdown
-## Bottom Sheet
-| Signal | Surface | Detents | Owner |
-|---|---|---|---|
-| Half-sheet picker | presented sheet | [.medium, .large] | caller owns isPresented |
-| Sticky "Devam Et" bar | pinned bottom CTA | n/a (safeAreaInset) | part of screen |
-| 3-step add flow | multi-step in-sheet | per-step (content height) | caller drives path |
-```
-
-Property classification addition:
-
-| Classification | When | Swift Pattern |
-|---|---|---|
-| Sheet content | Component is authored to live inside a sheet | plain component; caller adds `.presentationDetents(...)` |
-| Present-child-as-sheet | Component reveals a child surface | caller-owned `isPresented`/`item` + `.sheet` (component emits the trigger intent) |
-| Pinned CTA | Sticky bottom action bar | `.safeAreaInset(edge:.bottom)` at the screen, not a modal |
-
-## Integration with Phase 4B
-- Author the component as sheet **content**; let the caller own presentation + detents.
-- Prefer semantic detents; content-sized sheets measure height via a preference key.
-- Pinned CTA = `.safeAreaInset(edge:.bottom)`, not a presented sheet.
-- Multi-step flow = `NavigationStack` inside the sheet (native) or the engine's nav sheet (custom).
-- If `ui.sheetSystem.mode == custom`, use `{brandedModifier}`/headless modifiers + `{detentType}`/`{backdropType}` per config.
-- Verify on the simulator across detents, backdrop, and drag/dismiss on the project's min + current iOS.
-
----
-
-## When NOT to Use Bottom-Sheet Integration
-- Toast/HUD/alert/data modal card → `/figma-overlays`.
-- Screen routing/tabs/deep links → `/figma-navigation`.
-- An inline expandable/disclosure within page flow → plain component content.
-
-## Checklist  -  Before Leaving the Skill
-```
-[ ] Component is sheet CONTENT; caller owns isPresented/item + detents
-[ ] Detents ascend, max 3; semantic detents preferred; no magic-number heights
-[ ] Pinned CTA uses safeAreaInset(edge:.bottom), not a presented sheet
-[ ] Content-sized sheet measures height via preference key, then scrolls
-[ ] Multi-step flow uses NavigationStack-in-sheet (native) or engine nav sheet (custom)
-[ ] Corner radius / grabber / insets from tokens, not literals
-[ ] Default native SwiftUI; custom engine only when figma-config ui.sheetSystem.mode == custom
-[ ] Overlays over the sheet mount on the sheet content surface
-```

package/pipeline/skills/figma-common/figma-cli-iterate/SKILL.md

@@ -1,282 +0,0 @@
----
-name: figma-cli-iterate
-description: Runs the complete Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-7) → commit. Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
----
-
-# /figma-cli-iterate  -  Full Pipeline Orchestrator for CLI
-
-## Purpose
-
-Runs the complete Figma-to-SwiftUI pipeline for one or more issues: pick → start → implement (phases 0-7) → commit. Returns a structured `ORCHESTRATOR_RESULT` block that the CLI orchestrator can parse.
-
-This skill IS the orchestrator. It dispatches **only leaf-phase subagents**  -  individual phase instruction files that read one doc, execute gates, and return. It never delegates to multi-phase meta-skills.
-
-## Forbidden Dispatches
-
-**NEVER dispatch these as subagents  -  they are orchestrators that would try to dispatch further:**
-
-- `/figma-to-swift-ui-implement` (Phases 0-4)
-- `/figma-to-swift-ui-test` (Phase 5)
-- `/figma-to-swift-ui-code-connect` (Phase 6)
-- `/figma-to-swift-ui-wiki` (Phase 7)
-- `/figma-iteration-commit`
-- `/figma-to-swiftui` (entire pipeline)
-
-Instead, dispatch the **leaf phase instruction files** directly via Agent tool.
-
-## Parameters
-
-```
-/figma-cli-iterate #230           ← implement specific issue
-/figma-cli-iterate                ← auto-pick next available
-```
-
----
-
-## Constants
-
-```
-GH_REPO         = {github.componentsRepo}
-REPO_ROOT       = git repo root (auto-detect)
-COMMON          = ${REPO_ROOT}/{repos.common.path}
-UICOMPONENTS    = ${REPO_ROOT}/{repos.components.path}
-WIKI            = ${REPO_ROOT}/{repos.wiki.path}
-PHASE_DIR       = .instructions/figma/figma-to-swiftui/phases
-REF_DIR         = .instructions/figma/figma-to-swiftui/reference
-SCRIPT_DIR      = .instructions/figma/figma-to-swiftui/scripts
-```
-
----
-
-## STEP 0  -  Pick Issue
-
-Same logic as `/figma-iterate` STEP 0. Read `.instructions/figma/figma-iterate/SKILL.md` STEP 0 for details.
-
-Extract from issue body: `componentName`, `figmaUrl`, `nodeId`, `jiraKey`, `registryName`, `figmaPage`, `acceptanceCriteria`.
-
----
-
-## STEP 1  -  Start
-
-Run inline (not as a skill). Read `.instructions/figma/figma-to-swift-ui-start/SKILL.md` for the full procedure:
-
-1. Parse issue → extract metadata
-2. Fetch latest → checkout `develop` (main stays on develop, NO feature branch), `iteration/develop` (submodules)
-3. Create feature branches on **submodules only** (common, uicomponents)
-4. Registry lookup → `componentLocation`, `artifactPath`
-5. Save specs artifact if acceptance criteria exist
-6. Assign (GitHub + Jira)
-7. **Move GitHub issue to "In Develop" on the Projects V2 board**  -  required. Read STEP 5 of the start skill. Run both GraphQL mutations: set Status option `bc6c45f7` (In Develop) and Phase option `0577dcda` (Implementation). Do NOT skip this  -  new issues are created with Status=Todo, so this transition is how the board reflects "someone is working on it".
-
----
-
-## required PRE-READ
-
-Before dispatching any phase subagent, read:
-  ${REF_DIR}/orchestrator-discipline.md
-
-These 6 rules govern orchestrator behavior. Violations have caused repeated failures. Follow them strictly.
-
----
-
-## STEP 2  -  Implement (Phases 0-7)
-
-This is the core orchestration. Run each phase by dispatching leaf subagents and scripts.
-
-### Spec Injection (Option A)
-
-Before dispatching any Phase 4+ subagent, check if `{artifactPath}/pass0/specs.md` exists. If it does:
-1. Read the specs
-2. Extract concrete requirements
-3. Inject them as **CRITICAL SPEC GATES** in the subagent dispatch prompt  -  NOT as a sidecar "also read this file" instruction
-
-This ensures spec requirements become indistinguishable from standard gates.
-
-### Phase Dispatch Table
-
-All instruction files relative to `${PHASE_DIR}/`.
-
-| Phase | Instruction | Model | Subagent? |
-|-------|-------------|-------|-----------|
-| 0 | `phase-0-init.md` | opus | Yes (leaf) |
-| 1 | `${SCRIPT_DIR}/phase1-gather.py` | N/A | No (script) |
-| 2A | `phase-2a-testing-identifiers.md` | opus | Yes (leaf) |
-| 2B | `phase-2b-localization.md` | sonnet | Yes (leaf) |
-| 2C | `phase-2c-accessibility.md` | opus | Yes (leaf) |
-| 2D | `phase-2d-analytics.md` | sonnet | Yes (leaf) |
-| 3A | `phase-3a-location.md` | sonnet | Yes (leaf) |
-| 3C | `phase-3c-nested.md` | sonnet | Yes (leaf) |
-| 3H | `phase-3h-variant-config.md` | opus | Yes (leaf) |
-| 3D | `phase-3d-patterns.md` | opus | Yes (leaf) |
-| 4A | `phase-4a-configuration.md` | opus | Yes (leaf, COMPLEX only) |
-| 4B | `phase-4b-view.md` | opus | Yes (leaf) |
-| 4C | `phase-4c-documentation.md` | sonnet | Yes (leaf) |
-| 4D | `phase-4d-preview.md` | sonnet | Yes (leaf) |
-| 4E | `phase-4e-modifiers.md` | sonnet | Yes (leaf, COMPLEX only) |
-| 5A | `phase-5a-viewinspector.md` | sonnet | Yes (leaf) |
-| 5B | `phase-5b-snapshot.md` | sonnet | Yes (leaf) |
-| 5C | `phase-5c-unit.md` | sonnet | Yes (leaf, if applicable) |
-| 6 | `phase-6-code-connect.md` | opus | Yes (leaf) |
-| 7 | `phase-7a-wiki-generate.md` | sonnet | Yes (leaf) |
-
-### Dispatch Prompt Template
-
-For each leaf subagent:
-
-```
-You are executing {Phase Name} of the Figma-to-SwiftUI workflow.
-
-## Context
-- Component: {componentName}
-- File Key: {fileKey}
-- Node ID: {nodeId}
-- Artifact Path: {artifactPath}
-- Component Location: {componentLocation}
-- GitHub Issue: {issueNumber} (omit if not available)
-
-## CRITICAL SPEC GATES (only if specs exist)
-{Concrete requirements extracted from specs  -  phrased as mandatory instructions, not a file reference}
-
-## Tool Restrictions
-{from dispatch table}
-
-## Your Instructions
-Read and STRICTLY FOLLOW your phase instructions gate-by-gate from this file:
-  {PHASE_DIR}/{instruction file}
-
-Read the return protocol from:
-  {REF_DIR}/halt-return-protocol.md
-
-## Reference Files
-{relevant reference files from the read-order table in figma-to-swiftui/SKILL.md}
-
-## Previous Phase Artifacts
-{artifact paths in read order  -  compact first}
-```
-
-### Phase Execution Flow
-
-**Phase 0**: Dispatch subagent → verify `IMPLEMENTATION_HISTORY.md` created.
-
-**Phase 1**: Run script:
-```bash
-python3 ${SCRIPT_DIR}/phase1-gather.py \
-  --file-key "{fileKey}" --node-id "{nodeId}" \
-  --artifact-path "{artifactPath}" --component-name "{componentName}"
-```
-If `COMPLETE_WITH_DEFERRED` → dispatch Phase 1 deferred resolution subagent.
-
-**Phase 2**:
-1. Pre-check: verify `pass1/_index.md`
-2. Normalize: check sublayers in `design_context_response.json`
-3. Registry lookup: `FigmaRegistryUtility utility-lookup --node-id '{nodeId}'`
-4. Wave 1 (parallel): dispatch 2A + 2B + 2C subagents simultaneously
-5. Wave 2: dispatch 2D subagent
-6. Finalize: `python3 ${SCRIPT_DIR}/phase2-finalize.py ...`
-
-**Phase 3**:
-1. Wave 1 (parallel): `python3 ${SCRIPT_DIR}/phase3-scripts.py wave1 ...` + dispatch 3A + 3C + 3H subagents
-2. Missing token resolution: check `pass3/02_token_mapping.md` for "⚠️ not found". If any → dispatch resolution subagent
-3. Wave 2: dispatch 3D subagent
-4. Wave 3: `python3 ${SCRIPT_DIR}/phase3-scripts.py 3g ...`
-5. Spec: `python3 ${SCRIPT_DIR}/phase3-scripts.py spec ...`
-6. Write `pass3/_index.md`
-
-**Phase 4**:
-1. Read `pass3/05_complexity.md` → SIMPLE or COMPLEX
-2. Prepare directory: `mkdir -p {componentLocation}`
-3. Wave 1 (parallel): dispatch 4B + 4C (+ 4A if COMPLEX)
-4. Wave 2 (parallel): dispatch 4D (+ 4E if COMPLEX)
-5. Validate: `bash ${SCRIPT_DIR}/validate-phase4.sh ...`
-6. Build: `xcodebuild build ...`  -  fix errors if any
-
-**Phase 5**:
-1. Switch to local common: comment out remote URL in Package.swift, add local path
-2. Wave 1 (parallel): dispatch 5A + 5B subagents
-3. Wave 2 (conditional): dispatch 5C if component has model logic
-4. Run tests sequentially via `${SCRIPT_DIR}/run-uicomponents-tests.sh`
-5. Revert Package.swift to remote
-
-**Phase 6**: Dispatch subagent → run `${SCRIPT_DIR}/phase6-finalize.py` as safety net.
-
-**Phase 7**: Dispatch subagent.
-
----
-
-## STEP 3  -  Commit
-
-Run inline. Read `.instructions/figma/figma-iteration-commit/SKILL.md` for the full procedure:
-
-1. Rebase submodules to `iteration/develop` if on feature branch
-2. Build validation
-3. Commit to `iteration/develop` (common → uicomponents → wiki)
-4. Push with rebase-retry loop
-5. Clean up feature branches
-6. Issue housekeeping (comment, phase update, wiki link)
-7. Auto-unblock dependents
-
----
-
-## STEP 4  -  Loop
-
-Same logic as `/figma-iterate` STEP 4. If specific issue → exit after one. If `--count` → decrement. Otherwise → pick next.
-
----
-
-## STEP 5  -  Output Result
-
-Output EXACTLY this block as your FINAL message. Nothing else after it.
-
-### On success (per component):
-
-```
-ORCHESTRATOR_RESULT:
-  status: COMPLETE
-  issueNumber: <N>
-  componentName: <name>
-  figmaUrl: <url>
-  nodeId: <nodeId>
-  jiraKey: <key>
-  commits:
-    common: <SHA>
-    uicomponents: <SHA>
-    wiki: <SHA>
-  phases: [0, 1, 2, 3, 4, 5, 6, 7]
-  testsRun: <count>
-  summary: <one-line>
-```
-
-### On failure:
-
-```
-ORCHESTRATOR_RESULT:
-  status: FAILED
-  issueNumber: <N>
-  componentName: <name>
-  failedPhase: <phase>
-  reason: <exact reason>
-  suggestion: <what to fix>
-```
-
-### On full iteration completion:
-
-```
-ORCHESTRATOR_RESULT:
-  status: ITERATION_COMPLETE
-  completed:
-    - { issue: <N>, component: <name>, commits: { common: <SHA>, uicomponents: <SHA>, wiki: <SHA> } }
-  failed:
-    - { issue: <N>, component: <name>, phase: <phase>, reason: <reason> }
-  remaining: <count>
-```
-
----
-
-## Error Handling
-
-- **No available issues**: Output ORCHESTRATOR_RESULT with status ITERATION_COMPLETE, empty completed/failed.
-- **Blocked issue**: Output FAILED.
-- **Phase HALT**: Show reason, ask user. If resolved → retry phase. If skipped → FAILED for this component, move to next.
-- **Build failure**: Attempt auto-fix. If unfixable → FAILED.
-- **3 consecutive failures**: Stop iteration.
-- **Subagents can't dispatch subagents**: This is why we dispatch only leaf phases. If a phase instruction file references dispatching subagents, ignore that  -  run its gates directly in the subagent.