@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.1

package/pipeline/skills/figma-ios/figma-component-implement/SKILL.md

@@ -1,184 +0,0 @@
----
-name: figma-component-implement
-description: "Figma → SwiftUI implementation for a single component. Runs Phases 0-4 of the figma-to-swiftui pipeline (init, data gathering, analysis, code generation) and produces a production-ready SwiftUI view. Excludes testing, Code Connect, and wiki  -  those are separate standalone skills. iOS platform peer  -  Android equivalent lives under figma-android/."
-user-invocable: true
-argument-hint: "<figma-url>"
-language: en
-platform: ios
-status: wip-v5
-sourced-from: upstream/figma-to-swift-ui-implement
-local-overlay: true
----
-
-# figma-component-implement  -  Standalone Implementation (Phases 0-4)
-
-## Purpose
-
-Implements a Figma component as a production-ready SwiftUI view. Runs Phases 0-4 of the figma-to-swiftui pipeline: init, data gathering, analysis, and code generation. Does NOT include testing, Code Connect, or Confluence  -  those are separate standalone skills.
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| Figma URL | Yes | `https://www.figma.com/design/{fileKey}/...?node-id={nodeId}` |
-| `phase-N` | No | Resume from a specific phase |
-| `status` | No | Show implementation status |
-
-```
-/figma-to-swift-ui-implement https://www.figma.com/design/9ipBvrtsq9HlQ175B9k0wx/?node-id=2073-17454
-/figma-to-swift-ui-implement phase-3
-/figma-to-swift-ui-implement status
-```
-
----
-
-## Parse Arguments
-
-Same as `/figma-to-swiftui`:
-
-| Input | Mode | Action |
-|-------|------|--------|
-| `https://www.figma.com/design/...` | **Start** | Extract fileKey + nodeId, begin Phase 0 |
-| `phase-0` through `phase-4` | **Resume** | Read IMPLEMENTATION_HISTORY.md, dispatch that phase |
-| `phase-2a` through `phase-2d` | **Resume** | Dispatch specific Phase 2 sub-phase |
-| `status` | **Status** | Read and display IMPLEMENTATION_HISTORY.md |
-
-### URL Parsing
-
-```
-https://www.figma.com/design/{fileKey}/{fileName}?node-id={nodeId}
-```
-Convert `-` to `:` in node-id.
-
----
-
-## Phase Execution Order
-
-```
-0 (Init) → 1 (Gather) → 2A → 2B → 2C → 2D → 3 (Analysis) → 4A → 4B → 4C → 4D → 4E
-```
-
-This skill stops after Phase 4. To continue:
-- `/figma-to-swift-ui-test` → Phase 5 (testing)
-- `/figma-to-swift-ui-code-connect` → Phase 6 (Code Connect)
-- `/figma-to-swift-ui-confluence` → Phase 7 (documentation)
-
----
-
-## Dispatch Table
-
-All instruction files are in `.instructions/figma/figma-to-swiftui/`  -  shared with `/figma-to-swiftui`.
-
-| Phase | Instruction (shared) | Model | Max Turns | Tool Restrictions |
-|-------|---------------------|-------|-----------|-------------------|
-| 0 | `phases/phase-0-init.md` | opus | 30 | No Edit |
-| 1 | `scripts/phase1-gather.py` | N/A (script) | N/A | Bash only |
-| 2A | `phases/phase-2a-testing-identifiers.md` | opus | 25 | No Edit |
-| 2B | `phases/phase-2b-localization.md` | sonnet | 25 | No Edit |
-| 2C | `phases/phase-2c-accessibility.md` | opus | 25 | No Edit |
-| 2D | `phases/phase-2d-analytics.md` | sonnet | 20 | No Edit, No Bash |
-| 3A | `phases/phase-3a-location.md` | sonnet | 20 | No Edit |
-| 3C | `phases/phase-3c-nested.md` | sonnet | 20 | No Edit |
-| 3H | `phases/phase-3h-variant-config.md` | opus | 25 | No Edit |
-| 3D | `phases/phase-3d-patterns.md` | opus | 30 | No Edit |
-| 4A | `phases/phase-4a-configuration.md` | opus | 30 | ALL allowed |
-| 4B | `phases/phase-4b-view.md` | opus | 40 | ALL allowed |
-| 4C | `phases/phase-4c-documentation.md` | sonnet | 20 | ALL allowed |
-| 4D | `phases/phase-4d-preview.md` | sonnet | 20 | ALL allowed |
-| 4E | `phases/phase-4e-modifiers.md` | sonnet | 20 | ALL allowed |
-
----
-
-## Phase Routing
-
-All routing logic is identical to `/figma-to-swiftui` SKILL.md:
-
-- **Phase 0**: Dispatch table
-- **Phase 1**: Run script, handle COMPLETE_WITH_DEFERRED
-- **Phase 2**: Inline routing (PRE-CHECK → NORMALIZE → REGISTRY_LOOKUP → Wave 1 parallel 2A+2B+2C → Wave 2 2D → FINALIZE script)
-- **Phase 3**: Inline routing (PRE-CHECK → NORMALIZE → Wave 1 scripts+3A+3C+3H → missing token resolution → Wave 2 3D → Wave 3 3G → COLLECT → SPEC → INDEX)
-- **Phase 4**: Inline routing (PRE-CHECK → LOAD_SPEC → PREPARE_DIRECTORY → Wave 1 4A+4B+4C → Wave 2 4D+4E → COLLECT → VALIDATE → BUILD → UPDATE_REGISTRY)
-
-Refer to `.instructions/figma/figma-to-swiftui/SKILL.md` for the full routing logic  -  it is the authoritative source. This skill uses the exact same dispatch procedures, read-order tables, and return parsing.
-
-### Phase 4 registry finalize
-
-After BUILD passes, run `phase4-finalize.py` to mark `status.ios.implemented` green with a content-hashed version bump. See `phases/phase-4-orchestrator.md` GATE 4 for details.
-
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/phase4-finalize.py \
-    --node-id "{nodeId}" \
-    --component-name "{ComponentName}" \
-    --source-file "{componentLocation}/{ComponentName}.swift" \
-    --platform ios
-```
-
-The actual GitHub issue sync (labels, body progress table, Projects V2 fields, assignee) runs later when you call `/figma-iteration-commit`  -  it reads this registry state and invokes `update-issue-from-registry.py` once per node.
-
----
-
-## Reference Files
-
-Same as `/figma-to-swiftui`:
-
-| File | Used By Phases |
-|------|----------------|
-| `reference/tools.md` | 0, 1 |
-| `reference/registry.md` | 0, 3 |
-| `reference/missing-tokens.md` | 3, 4 |
-| `reference/macros.md` | 4 |
-| `reference/figma-to-swiftui-effects.md` | 4 |
-| `reference/accessibility.md` | 2C |
-| `reference/localization-naming.md` | 2B |
-| `reference/testing-identifiers-naming.md` | 2A |
-| `reference/analytics-events.md` | 2D |
-
----
-
-## Artifact Path Resolution
-
-Same as `/figma-to-swiftui`:
-
-```bash
-CONFIG_PATH="{repos.common.path}"
-cd "$CONFIG_PATH" && .build/debug/FigmaRegistryUtility lookup --node-id '{nodeId}'
-```
-
----
-
-## Resume Mode
-
-Same as `/figma-to-swiftui`:
-
-1. Find IMPLEMENTATION_HISTORY.md
-2. Read context variables
-3. Verify prerequisite artifacts
-4. Dispatch requested phase
-
----
-
-## Completion
-
-After Phase 4 completes successfully, output:
-
-```
-Implementation complete: {ComponentName}
-- Location: {componentLocation}
-- Files: {ComponentName}.swift, FIGMA.md [, {ComponentName}Configuration.swift, {ComponentName}+Modifiers.swift]
-- Build: PASSED
-
-Next steps:
-- /figma-to-swift-ui-test {figmaUrl} → generate and run tests
-- /figma-to-swift-ui-code-connect {figmaUrl} → publish Code Connect
-- /figma-to-swift-ui-confluence {figmaUrl} → upload Confluence docs
-```
-
----
-
-## Notes
-
-- This skill runs Phases 0-4 only  -  the implementation core
-- All phase files, scripts, and references are shared with `/figma-to-swiftui`
-- The routing logic is identical  -  only the scope differs (stops at Phase 4 vs going to Phase 8)
-- Resume mode works the same  -  `phase-3` resumes Phase 3 from existing artifacts
-- Can be followed by any combination of the standalone skills in any order

package/pipeline/skills/figma-ios/figma-component-test/SKILL.md

@@ -1,219 +0,0 @@
----
-name: figma-component-test
-description: "Test generator + runner for implemented SwiftUI Figma components. Produces ViewInspector structural tests, snapshot tests, and XCTest unit tests for a component already built via Phase 4 codegen. Runs standalone (reads source files) or as a Phase 3.5 continuation. iOS platform peer  -  Android equivalent (Paparazzi/Roborazzi) lives under figma-android/."
-user-invocable: true
-argument-hint: "<figma-url> | --component <name>"
-language: en
-platform: ios
-status: wip-v5
-sourced-from: upstream/figma-to-swift-ui-test
-local-overlay: true
----
-
-# figma-component-test  -  Standalone Test Generation & Execution
-
-## Purpose
-
-Generates and runs ViewInspector, snapshot, and unit tests for an implemented Figma component. Works independently from `/figma-to-swiftui`  -  reads source files directly. Can also run as a continuation after Phase 4 when full artifacts exist.
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| Figma URL | Yes | `https://www.figma.com/design/{fileKey}/...?node-id={nodeId}` |
-
-```
-/figma-to-swift-ui-test https://www.figma.com/design/9ipBvrtsq9HlQ175B9k0wx/?node-id=2073-17454
-```
-
----
-
-## Parse Arguments
-
-Extract from Figma URL:
-```
-https://www.figma.com/design/{fileKey}/{fileName}?node-id={nodeId}
-```
-Convert `-` to `:` in node-id.
-
----
-
-## Gate 0: Preliminary Check
-
-### 1. Resolve Component
-
-```bash
-cd {repos.common.path}
-.build/debug/FigmaRegistryUtility lookup --node-id '{nodeId}'
-```
-
-Extract: `componentName`, `suggestedComponentLocation`, `suggestedArtifactPath`.
-
-### 2. Verify Prerequisites
-
-| Check | Required | Source |
-|-------|----------|--------|
-| `{componentLocation}/{ComponentName}.swift` | Yes | Component must be implemented |
-| `{componentLocation}/FIGMA.md` | Yes | Variant mapping for snapshot matrix |
-| Component registry JSON (`{nodeId}.json`) | Yes | Testing identifiers |
-
-If Swift file missing → HALT. Component not implemented.
-
-### 3. Check Existing Tests
-
-| Condition | Action |
-|-----------|--------|
-| ViewInspector + Snapshot tests exist | **UPDATE** mode  -  regenerate and re-record |
-| Tests missing | **CREATE** mode |
-
-### 4. Detect Path: HOT or COLD
-
-| Condition | Path |
-|-----------|------|
-| `{artifactPath}/pass5/_test_index.md` exists | **HOT**  -  skip Gate 1, go to Gate 2 |
-| Missing | **COLD**  -  run Gate 1 |
-
----
-
-## Gate 1: Test Data Accumulation (COLD path only)
-
-AI subagent (sonnet, 20 turns) reads source files and produces the test index + supporting artifacts that Phase 5 subphases expect.
-
-### Sources
-
-| Source | Derives |
-|--------|---------|
-| `{ComponentName}.swift` (init signature, enums, types) | Variant axes, complexity (SIMPLE/COMPLEX), optional properties |
-| FIGMA.md (variant mapping table) | Snapshot matrix  -  which property combinations to test |
-| FIGMA.md (parameters table) | Parameter types, defaults |
-| Component registry JSON (testingIdentifiers) | Accessibility identifier test cases |
-| `{ComponentName}Configuration.swift` (if COMPLEX) | Configuration properties, chain modifiers |
-
-### Outputs
-
-The subagent writes:
-
-```
-{artifactPath}/pass5/_test_index.md
-{artifactPath}/pass3/04b_component_architecture.md  (if missing)
-{artifactPath}/pass3/04_patterns.md                  (if missing)
-{artifactPath}/pass3/05_complexity.md                (if missing)
-{artifactPath}/pass2/utility_identifiers.json        (if missing  -  from registry)
-```
-
-The `_test_index.md` contains:
-- componentName, sourceModule, componentPath
-- Paths to all referenced artifacts
-- Variant axes summary
-- Testing identifier list
-
-After this step, Phase 5A/5B/5C subphases can't distinguish HOT from COLD.
-
----
-
-## Gate 2: Test Generation
-
-### Dependency Switch
-
-Before running tests, switch to local common dependency:
-
-In `{repos.components.path}/Package.swift`:
-- Comment out `.package(url: "...{project.slug}-common...", ...)`
-- Add `.package(path: "../{project.slug}-common")`
-
-### Wave 1 (parallel): 5A + 5B
-
-Dispatch subagents:
-
-| Phase | Instruction (shared) | Model | Max Turns |
-|-------|---------------------|-------|-----------|
-| 5A | `phases/phase-5a-viewinspector.md` | sonnet | 40 |
-| 5B | `phases/phase-5b-snapshot.md` | sonnet | 40 |
-
-### Wave 2 (conditional): 5C
-
-| Condition | Action |
-|-----------|--------|
-| Component has ViewModel/model logic | Dispatch `phases/phase-5c-unit.md` (sonnet, 30 turns) |
-| Pure View + Configuration | Skip  -  N/A |
-
----
-
-## Gate 3: Test Execution
-
-Run tests sequentially (shared DerivedData lock):
-
-```bash
-REPO_ROOT=$(git rev-parse --show-toplevel)
-bash "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/run-uicomponents-tests.sh" \
-    --filter "{ComponentName}ViewInspectorTests"
-bash "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/run-uicomponents-tests.sh" \
-    --filter "{ComponentName}SnapshotTests"
-```
-
-Both must exit 0. Fix any failures, re-run.
-
-### Dependency Revert
-
-After tests pass, revert Package.swift:
-- Uncomment `.package(url: ...)`
-- Remove `.package(path: ...)`
-
----
-
-## Gate 4: Update Registry
-
-Mark `status.ios.tested` green via the Phase 5 finalize script:
-
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/phase5-finalize.py \
-    --node-id "{nodeId}" \
-    --platform ios
-```
-
-The script records `against = status.ios.implemented.version`, so the flag will automatically drop to yellow next time Phase 4 bumps `implemented.version`.
-
-| Result | Action |
-|--------|--------|
-| Exit 0, `"action": "updated"` / `"already_current"` / `"created"` | Proceed |
-| Exit 1 | HALT  -  verify node-id matches registry |
-
-GitHub issue sync (labels, Progress table, Projects V2 fields) runs later when `/figma-iteration-commit` invokes `update-issue-from-registry.py`.
-
----
-
-## Dispatch Table
-
-| Gate | Instruction | Model | Max Turns |
-|------|-------------|-------|-----------|
-| 0 | Inline (this file) |  -  |  -  |
-| 1 | AI subagent | sonnet | 20 |
-| 2 (5A) | `phases/phase-5a-viewinspector.md` (shared) | sonnet | 40 |
-| 2 (5B) | `phases/phase-5b-snapshot.md` (shared) | sonnet | 40 |
-| 2 (5C) | `phases/phase-5c-unit.md` (shared) | sonnet | 30 |
-| 3 | Script (`run-uicomponents-tests.sh`) |  -  |  -  |
-| 4 | Script (`phase5-finalize.py`) |  -  |  -  |
-
----
-
-## Shared Resources
-
-| Resource | Used By |
-|----------|---------|
-| `phases/phase-5a-viewinspector.md` | Gate 2 |
-| `phases/phase-5b-snapshot.md` | Gate 2 |
-| `phases/phase-5c-unit.md` | Gate 2 |
-| `reference/viewinspector.md` | Gate 2 (5A) |
-| `reference/snapshot-testing.md` | Gate 2 (5B) |
-| `scripts/run-uicomponents-tests.sh` | Gate 3 |
-
----
-
-## Notes
-
-- Standalone entry point  -  does NOT require `/figma-to-swiftui` to have run
-- When called after Phase 4, detects existing artifacts (HOT path) and skips data accumulation
-- Phase 5A/5B/5C instruction files don't know which skill invoked them  -  fully modular
-- Always switches to local common dependency for test execution, reverts after
-- Snapshot tests run twice: first to record, second to verify
-- If component already has tests (UPDATE mode), deletes old snapshots before re-recording

package/pipeline/skills/figma-ios/figma-component-wiki/SKILL.md

@@ -1,274 +0,0 @@
----
-name: figma-component-wiki
-description: Generate component wiki documentation with a pluggable adapter. Reads component source + FIGMA.md, renders markdown, then delegates publication to the adapter selected by figmaConfig.wiki.mode (submodule | in-repo | github-wiki | separate-repo).
-user-invocable: true
-argument-hint: <figma-url> | <component-name>
-allowed-tools: Read, Write, Glob, Grep, Bash
-status: wip-v5
-sourced-from: upstream/figma-to-swift-ui-wiki
-local-overlay: true
----
-
-# figma-component-wiki  -  Component Wiki Documentation
-
-> **WS-5 v5.0.0  -  locally overlaid.** `local-overlay: true` in frontmatter tells `sync-figma-source.sh` + `import-figma-skills.sh` to skip this file so this v5-specific contract (4-adapter dispatch) isn't flattened on every sync.
-
-## Dispatch contract (Phase 7 Report Step 2)
-
-Phase 7 calls this skill with:
-
-```
-{
-  componentName: string,
-  componentPath: string,
-  figmaConfig:    object,
-  agentState:     object,
-  dryRun?:        boolean
-}
-```
-
-Returns `{ writtenPaths, committedSha?, pushedRemote?, confluencePageId? }`.
-
-Emit progress line `→ writing wiki {componentName} (mode: {mode})` as the first action. On failure, emit `→ wiki write failed (mode: {mode}): {reason}` and bubble the error; Phase 7 treats wiki as non-blocking.
-
-## Adapter selection
-
-| mode | when to pick | path layout | push semantics |
-|---|---|---|---|
-| `submodule` | Team versions the wiki as a git submodule (source project's native layout). | `{repos.wiki.path}/FigmaComponents/{Category}/{Name}/{Name}.md` + `assets/` | Commit into submodule's `{repos.wiki.branch}`, push. Updates parent repo's submodule pointer. |
-| `in-repo` | Simple projects without a separate wiki repo (default). | `{repos.components.path}/.wiki/components/{Category}/{Name}.md` | No push  -  commits with the component change in Phase 6. |
-| `github-wiki` | Team uses GitHub's built-in wiki (`{org}/{repo}.wiki.git`). | `{repo}.wiki.git/{Category}/{Name}.md` | Clone `.wiki.git`, add/commit, push. Idempotent over re-renders. |
-| `separate-repo` | Wiki in a separate GitHub repo (not submodule, not `.wiki`). | Remote repo's configured branch; same file layout as submodule. | Clone on demand to `~/.cache/multi-agent/wiki/{slug}/`, commit, push. |
-
-Every adapter:
-
-1. Receives identical rendered markdown (content identical across layouts).
-2. Generates `_Sidebar.md` via `pipeline/scripts/wiki/sidebar-generator.py` (ships in a follow-up).
-3. Updates `ComponentImplementationStatus.md` via `pipeline/scripts/wiki/status-page.py` (ships in a follow-up).
-4. Is idempotent  -  re-running on unchanged component produces no diff.
-
-## Failure contracts
-
-- `submodule`  -  submodule path missing → return error, no partial commit.
-- `in-repo`  -  target dir not writable → return error; Phase 6 commit picks up the `.wiki/` change on its next run if paths eventually exist.
-- `github-wiki`  -  wiki repo not enabled on GitHub → suggest enabling and skip (return success with `writtenPaths: []`).
-- `separate-repo`  -  remote unreachable → cache the markdown under `~/.cache/multi-agent/wiki/{slug}/pending/` and return a warning; next run retries.
-
-## Markdown rendering (mode-agnostic)
-
-Reads `componentPath` + sibling `FIGMA.md` (variant matrix, usage examples). Writes:
-
-- `{Name}.md`  -  component page (overview, parameters, variants, code examples, tokens, accessibility notes).
-- `{Name}/assets/`  -  design screenshots.
-- `_Sidebar.md`  -  navigation (regenerated by the sidebar script).
-- `ComponentImplementationStatus.md`  -  status dashboard (regenerated).
-
----
-
-## Legacy content (upstream  -  submodule-mode reference)
-
-Everything below is the original `/figma-to-swift-ui-wiki` skill content, preserved as the reference implementation for the `submodule` adapter.
-
----
-
-# /figma-to-swift-ui-wiki  -  Standalone Wiki Documentation
-
-## Purpose
-
-Generates GitHub Wiki documentation for an implemented Figma component. Works independently from `/figma-to-swiftui`  -  reads source files and artifacts directly. Can also run as a continuation after Phase 6 when full artifacts exist.
-
-The wiki is the **source of truth** for component documentation. Confluence pages are synced from the wiki via `/figma-to-swift-ui-confluence-sync`.
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| Figma URL | Yes | `https://www.figma.com/design/{fileKey}/...?node-id={nodeId}` |
-
-```
-/figma-to-swift-ui-wiki https://www.figma.com/design/ps4xrJzhn7WNbfkZs895Bi/?node-id=9511-10868
-```
-
----
-
-## Parse Arguments
-
-Extract from Figma URL:
-```
-https://www.figma.com/design/{fileKey}/{fileName}?node-id={nodeId}
-```
-Convert `-` to `:` in node-id.
-
----
-
-## Gate 0: Preliminary Check
-
-1. Registry lookup:
-```bash
-cd {repos.common.path}
-.build/debug/FigmaRegistryUtility lookup --node-id '{nodeId}'
-```
-
-Extract: `suggestedComponentName`, `suggestedComponentLocation`, `suggestedArtifactPath`.
-
-2. Verify the component is implemented:
-```bash
-# Swift view file must exist
-ls {componentLocation}/{ComponentName}.swift
-# FIGMA.md must exist
-ls {componentLocation}/FIGMA.md
-```
-
-If either is missing → HALT: "Component not implemented. Run /figma-to-swiftui or /figma-to-swift-ui-implement first."
-
-3. Derive paths:
-- `wikiRoot` = `{repos.wiki.path}`
-- `wikiCategory` = derive from `artifactPath` (e.g., `DesignSystemCore/BoardingPass`, `MobileAppComponents/FlowBasedComponents/Explore`)
-- `wikiComponentPath` = `{wikiRoot}/{wikiCategory}/{ComponentName}`
-
----
-
-## Gate 1: Generate Wiki Documentation
-
-Dispatch Phase 7A as a subagent:
-
-```
-Agent(
-  subagent_type: "general-purpose",
-  model: sonnet,
-  max_turns: 30,
-  prompt: "You are executing Phase 7A (Wiki Documentation) of the Figma-to-SwiftUI workflow.
-
-  ## Context
-  - Component: {ComponentName}
-  - File Key: {fileKey}
-  - Node ID: {nodeId}
-  - Artifact Path: {artifactPath}
-  - Component Location: {componentLocation}
-  - Wiki Path: {wikiRoot}
-
-  ## Tool Restrictions
-  Do NOT use the Edit tool.
-
-  ## Your Instructions
-  Read and STRICTLY FOLLOW your phase instructions gate-by-gate from this file:
-    .instructions/figma/figma-to-swiftui/phases/phase-7a-wiki-generate.md
-
-  Execute every gate sequentially. Do not skip gates.
-
-  Read the return protocol from:
-    .instructions/figma/figma-to-swiftui/reference/halt-return-protocol.md
-
-  ## Previous Phase Artifacts (read in this order)
-  - {componentLocation}/FIGMA.md
-  - {componentLocation}/{ComponentName}.swift
-  - {artifactPath}/IMPLEMENTATION_HISTORY.md
-  - {artifactPath}/pass3/07_implementation_spec.md
-  - {artifactPath}/pass3/08_utility_integration.md
-  - {artifactPath}/pass3/03_nested_components.md
-  - {artifactPath}/pass2/utility_analytics.md (if exists)
-  - {artifactPath}/pass1/component_summary.json"
-)
-```
-
-On COMPLETE → proceed to Gate 1.5.
-On HALT → show user the halt reason, ask to resolve.
-
----
-
-## Gate 1.5: Verify Sidebar Updated
-
-The Phase 7A subagent is responsible for updating `_Sidebar.md` (GATE 4) via `sidebar-generator.py`. Verify it actually happened before committing:
-
-```bash
-cd ${wikiRoot}
-grep -q "\[\[${ComponentName}\]\]" _Sidebar.md
-```
-
-If the component is **missing** from `_Sidebar.md`, re-run the sidebar generator as a safety net:
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/sidebar-generator.py --wiki-root ${wikiRoot}
-```
-
-This regenerates the entire sidebar from the wiki directory structure. If the component's wiki folder exists, it will appear in the output. If it still doesn't appear after regeneration, the wiki folder structure is incorrect  -  HALT and ask the user to verify the component's wiki directory path.
-
----
-
-## Gate 2: Commit & Push Wiki
-
-```bash
-cd ${wikiRoot}
-git add -A
-git commit -m "docs: add ${ComponentName} wiki documentation"
-git push origin master
-```
-
-If push fails → HALT: "Wiki push failed. Check wiki submodule state."
-
----
-
-## Gate 3: Update Status Page
-
-Run the status page generator:
-
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/confluence-component-status.py
-```
-
-Then commit and push the updated status page:
-
-```bash
-cd ${wikiRoot}
-git add ComponentImplementationStatus.md
-git commit -m "docs: update Component Implementation Status"
-git push origin master
-```
-
----
-
-## Gate 4: Update Registry
-
-Mark `status.ios.wiki` green via the Phase 7 finalize script:
-
-```bash
-python3 .instructions/figma/figma-to-swiftui/scripts/phase7-finalize.py \
-    --node-id "{nodeId}" \
-    --platform ios
-```
-
-The script records `against = status.ios.implemented.version`, so the flag drops to yellow automatically on the next Phase 4 version bump until the wiki is regenerated.
-
-| Result | Action |
-|--------|--------|
-| Exit 0, `"action": "updated"` / `"already_current"` / `"created"` | Proceed |
-| Exit 1 | HALT  -  verify node-id matches registry |
-
-GitHub issue sync runs later via `/figma-iteration-commit` → `update-issue-from-registry.py`.
-
----
-
-## Summary
-
-Print:
-
-```
-Wiki documentation complete:
-
-| Field | Value |
-|-------|-------|
-| Component | {ComponentName} |
-| Wiki Page | {wikiComponentPath}/{ComponentName}.md |
-| Assets | {COUNT} screenshots |
-| Status Page | Updated |
-| Wiki URL | https://github.com/{github.componentsRepo}/wiki/{ComponentName} |
-```
-
----
-
-## Error Handling
-
-- **Component not implemented**: HALT  -  run implementation first.
-- **FigmaRegistryUtility not built**: Run `swift build --product FigmaRegistryUtility`.
-- **Wiki submodule not initialized**: Run `git submodule update --init` on the wiki path.
-- **Push fails**: Check if wiki submodule is on `master` and remote is accessible.
-- **Phase 7A HALT**: Show reason, ask user to resolve.