@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-4d-preview.md

@@ -1,8 +1,8 @@
-# PHASE 4D — Preview (LTR + RTL)
+# PHASE 4D  -  Preview (LTR + RTL)
 
-Write two preview structs — `{ComponentName}Preview` (LTR) and `{ComponentName}RTLPreview` (RTL with Arabic text) — and their `#Preview` entry points at the bottom of `{ComponentName}.swift`.
+Write two preview structs  -  `{ComponentName}Preview` (LTR) and `{ComponentName}RTLPreview` (RTL with Arabic text)  -  and their `#Preview` entry points at the bottom of `{ComponentName}.swift`.
 
-required — always execute this phase.
+required  -  always execute this phase.
 SEQUENTIAL: Runs AFTER Phase 4A (Configuration) and Phase 4B (View) complete.
 
 ---
@@ -10,10 +10,10 @@ SEQUENTIAL: Runs AFTER Phase 4A (Configuration) and Phase 4B (View) complete.
 ## CONTEXT VARIABLES
 
 These are provided by the orchestrator in the dispatch prompt:
-- `componentName` — e.g., "LabelBadge"
-- `componentLocation` — e.g., "Sources/UIComponents/.../LabelBadge/"
-- `artifactPath` — path to implementation artifacts
-- `complexity` — SIMPLE or COMPLEX
+- `componentName`  -  e.g., "LabelBadge"
+- `componentLocation`  -  e.g., "Sources/UIComponents/.../LabelBadge/"
+- `artifactPath`  -  path to implementation artifacts
+- `complexity`  -  SIMPLE or COMPLEX
 
 ---
 
@@ -47,11 +47,11 @@ USER_ACTION_REQUIRED: Run Phase 4B first.
 
 ## WHY A SEPARATE PREVIEW STRUCT
 
-`#Preview` is a freestanding macro. `@GenerateViewConfiguration` is a member macro that generates `configured()` and forwarding modifiers. When the component is placed directly inside `#Preview { ... }`, the freestanding macro expansion may not resolve members generated by the member macro — the compiler reports "no accessible initializers." This is a known Apple bug.
+`#Preview` is a freestanding macro. `@GenerateViewConfiguration` is a member macro that generates `configured()` and forwarding modifiers. When the component is placed directly inside `#Preview { ... }`, the freestanding macro expansion may not resolve members generated by the member macro  -  the compiler reports "no accessible initializers." This is a known Apple bug.
 
 The workaround:
-1. Create `{ComponentName}Preview: View` — a plain struct with NO macros, auto-synthesized `init()`
-2. `#Preview` instantiates `{ComponentName}Preview()` — it only needs to see the plain `init()`, which has no macro dependency
+1. Create `{ComponentName}Preview: View`  -  a plain struct with NO macros, auto-synthesized `init()`
+2. `#Preview` instantiates `{ComponentName}Preview()`  -  it only needs to see the plain `init()`, which has no macro dependency
 3. Inside `{ComponentName}Preview.body`, the custom init and chain modifiers ARE visible because `body` is evaluated during normal type-checking, not during freestanding macro expansion
 
 ---
@@ -125,13 +125,13 @@ Append to the bottom of `{componentLocation}/{ComponentName}.swift`:
 **Preferred style:** Use the custom init with required props + chain modifiers for optional props.
 
 For components with required props + closure dependencies:
-- `{ComponentName}(title: "Book Now") { /* action */ }` — required props + trailing closure in init
-- `.style(.primary).size(.xlarge)` — optional config via chain modifiers
+- `{ComponentName}(title: "Book Now") { /* action */ }`  -  required props + trailing closure in init
+- `.style(.primary).size(.xlarge)`  -  optional config via chain modifiers
 
 For components with paired modifiers:
-- `{ComponentName}(title: "OK") { primaryAction() }` — required in init
-- `.secondaryButton("Cancel") { cancel() }` — paired modifier
-- `.state(.scroll)` — optional config via chain modifier
+- `{ComponentName}(title: "OK") { primaryAction() }`  -  required in init
+- `.secondaryButton("Cancel") { cancel() }`  -  paired modifier
+- `.state(.scroll)`  -  optional config via chain modifier
 
 ```swift
 // MARK: - Preview
@@ -182,7 +182,7 @@ struct {ComponentName}RTLPreview: View {
     var body: some View {
         ScrollView {
             VStack(alignment: .leading, spacing: .Spacing.spacing16) {
-                Text("{ComponentName} — RTL")
+                Text("{ComponentName}  -  RTL")
                     .typographyStyle(.bodyBold)
                     .foregroundStyle(Color.Text.textPrimary)
                     .frame(maxWidth: .infinity, alignment: .leading)
@@ -268,7 +268,7 @@ struct {ComponentName}RTLPreview: View {
     var body: some View {
         ScrollView {
             VStack(alignment: .leading, spacing: .Spacing.spacing16) {
-                Text("{ComponentName} — RTL")
+                Text("{ComponentName}  -  RTL")
                     .typographyStyle(.bodyBold)
                     .foregroundStyle(Color.Text.textPrimary)
                     .frame(maxWidth: .infinity, alignment: .leading)
@@ -322,7 +322,7 @@ Verify ALL variants from `pass3/04_patterns.md` → Variant Examples are rendere
 - ALL explanatory texts (titles, labels) must be **leading aligned** (`.frame(maxWidth: .infinity, alignment: .leading)`)
 - Sections separated by `Divider()`
 - RTL preview has `.environment(\.layoutDirection, .rightToLeft)` and `.environment(\.locale, Locale(identifier: "ar"))` on the outermost container
-- RTL preview title includes `" — RTL"` suffix for visual identification
+- RTL preview title includes `"  -  RTL"` suffix for visual identification
 
 ### Width handling
 
@@ -348,7 +348,7 @@ Without this, white components are invisible on the white Xcode canvas.
 ```
 [ ] {ComponentName}Preview struct appended to {ComponentName}.swift (not a separate file)
 [ ] {ComponentName}RTLPreview struct appended to {ComponentName}.swift (not a separate file)
-[ ] Both preview structs have NO macros — plain structs
+[ ] Both preview structs have NO macros  -  plain structs
 [ ] #Preview instantiates {ComponentName}Preview() (unnamed = LTR default)
 [ ] #Preview("RTL") instantiates {ComponentName}RTLPreview()
 [ ] Inside Preview body, COMPLEX uses custom init + chain modifiers: {ComponentName}(requiredProp: val) { action }.prop1(val)

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-4e-modifiers.md

@@ -1,23 +1,23 @@
-# PHASE 4E — View Modifiers Extension (+Modifiers)
+# PHASE 4E  -  View Modifiers Extension (+Modifiers)
 
-Generate `{ComponentName}+Modifiers.swift` — a thin extension on the View that forwards each Configuration property as a discoverable chain modifier method.
+Generate `{ComponentName}+Modifiers.swift`  -  a thin extension on the View that forwards each Configuration property as a discoverable chain modifier method.
 
 CONDITIONAL: Only for COMPLEX components with `@GenerateViewConfiguration` + Configuration pattern.
 SEQUENTIAL: Runs AFTER Phase 4A (Configuration) and Phase 4B (View) complete.
 
-**NOTE:** `@GenerateViewConfiguration` generates ONLY the `configured()` method. It CANNOT generate View-level forwarding modifiers because Swift macros cannot introspect types other than the one they're attached to — the Configuration struct's properties are invisible to a macro on the View. This phase (AI-written +Modifiers) is ALWAYS required for COMPLEX components.
+**NOTE:** `@GenerateViewConfiguration` generates ONLY the `configured()` method. It CANNOT generate View-level forwarding modifiers because Swift macros cannot introspect types other than the one they're attached to  -  the Configuration struct's properties are invisible to a macro on the View. This phase (AI-written +Modifiers) is ALWAYS required for COMPLEX components.
 
 ---
 
 ## CONTEXT VARIABLES
 
 Provided by the orchestrator:
-- `componentName` — e.g., "TurkishButton"
-- `componentLocation` — e.g., "{repos.components.path}/Sources/UIComponents/Components/DesignSystemCore/Button/TurkishButton"
-- `artifactPath` — path to implementation artifacts
-- `complexity` — must be COMPLEX (skip if SIMPLE)
-- `gitUser` — git user name for file header
-- `date` — DD.MM.YYYY format
+- `componentName`  -  e.g., "TurkishButton"
+- `componentLocation`  -  e.g., "{repos.components.path}/Sources/UIComponents/Components/DesignSystemCore/Button/TurkishButton"
+- `artifactPath`  -  path to implementation artifacts
+- `complexity`  -  must be COMPLEX (skip if SIMPLE)
+- `gitUser`  -  git user name for file header
+- `date`  -  DD.MM.YYYY format
 
 ---
 
@@ -27,8 +27,8 @@ Provided by the orchestrator:
 
 2. **Verify files exist**:
    ```
-   {componentLocation}/{ComponentName}.swift              — View (Phase 4B)
-   {componentLocation}/{ComponentName}Configuration.swift — Configuration (Phase 4A)
+   {componentLocation}/{ComponentName}.swift               -  View (Phase 4B)
+   {componentLocation}/{ComponentName}Configuration.swift  -  Configuration (Phase 4A)
    ```
    Both must exist. Missing → HALT.
 
@@ -47,11 +47,11 @@ REASON: {ComponentName}Configuration.swift not found. Phase 4A must complete fir
 
 ---
 
-## ARCHITECTURAL RULE — Configuration Purity
+## ARCHITECTURAL RULE  -  Configuration Purity
 
 **Configuration structs hold ONLY declarative, value-type properties.**
 
-The following MUST NOT be in Configuration — they are direct View dependencies:
+The following MUST NOT be in Configuration  -  they are direct View dependencies:
 
 | Excluded Type | Reason | Where It Lives |
 |---------------|--------|----------------|
@@ -62,7 +62,7 @@ The following MUST NOT be in Configuration — they are direct View dependencies
 
 **Consequence for +Modifiers:** Only Configuration properties get forwarding methods. View dependencies (closures, bindings) are set at init time or via paired modifiers (Phase 4B). Paired modifiers (data+closure combined) live in the View file, not in +Modifiers.
 
-**CRITICAL — Skip rules for forwarding modifiers:**
+**CRITICAL  -  Skip rules for forwarding modifiers:**
 1. **Coexistent/paired properties (PAIRED_ACTION_SUBCOMPONENT):** Do NOT generate forwarding modifiers for config properties that are the data half of a paired modifier (e.g., `secondaryButtonTitle`). Setting title without action creates a nonsensical state. These are ONLY set via paired modifiers in the View file (e.g., `.secondaryButton(title) { action }`).
 2. **Init-param properties:** Do NOT generate forwarding modifiers for config properties that are required init parameters (e.g., `primaryButtonTitle`). These are set once at construction and should not be modified after init.
 
@@ -155,7 +155,7 @@ Do NOT generate a modifier for properties marked with `@IgnoreChainModifier` in
 
 ## GATE 3: UPDATE_PREVIEW
 
-After generating the +Modifiers file, check if the Preview structs in `{ComponentName}.swift` can benefit from the new API. Do NOT change Preview — it should continue using the `{ config in ... }` pattern for clarity. The +Modifiers API is for call-site usage, not previews.
+After generating the +Modifiers file, check if the Preview structs in `{ComponentName}.swift` can benefit from the new API. Do NOT change Preview  -  it should continue using the `{ config in ... }` pattern for clarity. The +Modifiers API is for call-site usage, not previews.
 
 ---
 

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-5-orchestrator.md

@@ -1,4 +1,4 @@
-# PHASE 5 — Testing Orchestrator
+# PHASE 5  -  Testing Orchestrator
 
 Orchestrates Phase 5 sub-phases: dispatches sub-agents to write test files, collects results.
 PREV: Phase 4 (Implementation)
@@ -54,7 +54,7 @@ USER_ACTION_REQUIRED: Run Phase 4 first.
 ## GATE 1: CREATE_TEST_INDEX
 
 Create a single index file that maps to all artifact paths used by test sub-phases.
-This is the ONLY file that knows where artifacts live — sub-phases read this index.
+This is the ONLY file that knows where artifacts live  -  sub-phases read this index.
 
 ### 1.1 Write `{artifactPath}/pass5/_test_index.md`
 
@@ -111,7 +111,7 @@ Generated: {DD.MM.YYYY}
 |-----------|------|---------|----------|
 | 5A | `phase-5a-viewinspector.md` | ViewInspector structure + accessibility tests | **ALWAYS** |
 | 5B | `phase-5b-snapshot.md` | Snapshot tests for ALL Figma variants | **ALWAYS** |
-| 5C | `phase-5c-unit.md` | Unit tests for ViewModel/model logic | **CONDITIONAL** — only if testable logic exists |
+| 5C | `phase-5c-unit.md` | Unit tests for ViewModel/model logic | **CONDITIONAL**  -  only if testable logic exists |
 
 ### Execution Flow
 
@@ -119,15 +119,15 @@ Generated: {DD.MM.YYYY}
 GATE 1: CREATE_TEST_INDEX
     ↓
 Wave 1 (parallel):
-    5A — ViewInspector structure tests
-    5B — Snapshot visual tests
+    5A  -  ViewInspector structure tests
+    5B  -  Snapshot visual tests
     ↓
 Wave 2 (conditional):
-    5C — Unit tests (ONLY if component has ViewModel/model logic)
+    5C  -  Unit tests (ONLY if component has ViewModel/model logic)
     ↓
 GATE 2: UPDATE_TEST_INDEX
     ↓
-GATE 3: TEST_EXECUTION (xcodebuild test — builds + runs, zero warnings, all tests pass)
+GATE 3: TEST_EXECUTION (xcodebuild test  -  builds + runs, zero warnings, all tests pass)
     ↓
 GATE 4: TEST_FILE_VALIDATION
     ↓
@@ -139,7 +139,7 @@ PHASE OUTPUT
 ### Sub-Phase Inputs
 
 All sub-phases read from `{artifactPath}/pass5/_test_index.md` for paths.
-They then read the actual artifact files listed in the index — no data duplication.
+They then read the actual artifact files listed in the index  -  no data duplication.
 
 | Sub-Phase | Reads From (via index) |
 |-----------|----------------------|
@@ -159,7 +159,7 @@ After all sub-phases complete, update `pass5/_test_index.md`:
 
 ## GATE 3: TEST_EXECUTION
 
-Build and run tests using the `run-uicomponents-tests.sh` script. The script uses `xcodebuild test` which builds before testing — no separate build gate is needed. This gate requires **zero build warnings** and **all tests passing**.
+Build and run tests using the `run-uicomponents-tests.sh` script. The script uses `xcodebuild test` which builds before testing  -  no separate build gate is needed. This gate requires **zero build warnings** and **all tests passing**.
 
 ### How it works
 
@@ -195,21 +195,21 @@ bash "${REPO_ROOT}/.instructions/figma/figma-to-swiftui/scripts/run-uicomponents
 
 After all tests pass, uncomment the original `.package(url: ...)` line and remove the `.package(path: ...)` line in `Package.swift`.
 
-**Important:** Do NOT run multiple test filters in parallel — they share the same DerivedData build database and will fail with a database lock error. Run them sequentially.
+**Important:** Do NOT run multiple test filters in parallel  -  they share the same DerivedData build database and will fail with a database lock error. Run them sequentially.
 
-**Note on first-run snapshots:** When snapshot tests run for the first time, `record: .missing` mode will **record** reference images (not fail). The test passes but creates new `__Snapshots__/` directories with `.png` files. These reference images are **gitignored** and must NOT be committed — they are re-recorded automatically on each machine. The wiki/Confluence skill copies them from disk for documentation before they are discarded.
+**Note on first-run snapshots:** When snapshot tests run for the first time, `record: .missing` mode will **record** reference images (not fail). The test passes but creates new `__Snapshots__/` directories with `.png` files. These reference images are **gitignored** and must NOT be committed  -  they are re-recorded automatically on each machine. The wiki/Confluence skill copies them from disk for documentation before they are discarded.
 
-### required GATE — SNAPSHOT_DESIGN_FIDELITY
+### required GATE  -  SNAPSHOT_DESIGN_FIDELITY
 
-Snapshot tests passing does NOT mean the rendered component matches the Figma design. It only means "the pixels we recorded match the pixels we recorded". A broken test scaffold (missing image prefetch per `phase-5b-snapshot.md § GATE 3.0.1`, wrong hosting frame, clipped layout, misapplied modifier) records a broken render as "ground truth" and every subsequent run compares broken-vs-broken and reports PASS. The test infrastructure CANNOT catch this class of failure by itself.
+Snapshot tests passing does NOT mean the rendered component matches the Figma design. It only means "the pixels we recorded match the pixels we recorded". A broken test scaffold (missing image prefetch per `phase-5b-snapshot.md section GATE 3.0.1`, wrong hosting frame, clipped layout, misapplied modifier) records a broken render as "ground truth" and every subsequent run compares broken-vs-broken and reports PASS. The test infrastructure CANNOT catch this class of failure by itself.
 
-This gate runs automatically after `TEST_EXECUTION` succeeds, every time Phase 5B recorded or re-recorded snapshots (first run or after a test-file change). It is performed by the orchestrator itself — no user involvement, no pause for confirmation.
+This gate runs automatically after `TEST_EXECUTION` succeeds, every time Phase 5B recorded or re-recorded snapshots (first run or after a test-file change). It is performed by the orchestrator itself  -  no user involvement, no pause for confirmation.
 
 **Procedure** (automated fix-and-retry loop, up to 4 attempts):
 
-1. Read `{artifactPath}/pass1/screenshot.png` — the Figma reference captured in Phase 1. (Claude is multimodal and sees images via the Read tool.)
+1. Read `{artifactPath}/pass1/screenshot.png`  -  the Figma reference captured in Phase 1. (Claude is multimodal and sees images via the Read tool.)
 2. Read the LTR light variant from `__Snapshots__/{componentName}SnapshotTests/test_snapshot_light_default.light_default.png` (or the equivalent default-variant filename).
-3. Compare them directly in the orchestrator's own visual judgement — layout, proportions, hierarchy, typography, colors, gradients, background content, text legibility.
+3. Compare them directly in the orchestrator's own visual judgement  -  layout, proportions, hierarchy, typography, colors, gradients, background content, text legibility.
 4. **If match** (all match criteria hold): proceed to Phase 6.
 5. **If mismatch** (any non-match criterion triggers): do NOT halt on the first failure. Instead enter the fix-and-retry loop:
 
@@ -242,7 +242,7 @@ This gate runs automatically after `TEST_EXECUTION` succeeds, every time Phase 5
     USER_ACTION_REQUIRED: The mismatch is beyond automated repair. Review pass5/fidelity_attempt_*.md to see what was tried, then inspect the component manually.
     ```
 
-7. **Counter tracking**: the attempt counter lives in the orchestrator's own task state — do NOT rely on grepping files. Increment after every mismatch-driven fix. Reset only on successful match.
+7. **Counter tracking**: the attempt counter lives in the orchestrator's own task state  -  do NOT rely on grepping files. Increment after every mismatch-driven fix. Reset only on successful match.
 
 **Match criteria** (all must hold):
 - Overall layout, proportions, and hierarchy match Figma
@@ -259,16 +259,16 @@ This gate runs automatically after `TEST_EXECUTION` succeeds, every time Phase 5
 - Colors that look "close enough" but don't match Figma tokens
 - Any case where the recorded snapshot is visibly different from `pass1/screenshot.png` beyond expected aspect-ratio or sample-data differences
 
-**Never ask the user to confirm the match**. The orchestrator is multimodal and has direct visual access to both images. Surfacing the images to the user and asking for confirmation is forbidden — it wastes a round-trip and makes the gate advisory instead of blocking. The orchestrator makes the judgement itself, enters the fix loop on mismatch, and only HALTs after the 4-attempt budget is exhausted.
+**Never ask the user to confirm the match**. The orchestrator is multimodal and has direct visual access to both images. Surfacing the images to the user and asking for confirmation is forbidden  -  it wastes a round-trip and makes the gate advisory instead of blocking. The orchestrator makes the judgement itself, enters the fix loop on mismatch, and only HALTs after the 4-attempt budget is exhausted.
 
-**Never explain away a mismatch**. If the visual comparison shows a clear difference, enter the fix loop — do not rationalise that the snapshot is "close enough" or that the difference is "just the sample image". Ambiguous cases also enter the fix loop and surface the specific concern in the `fidelity_attempt_{N}.md` diagnosis.
+**Never explain away a mismatch**. If the visual comparison shows a clear difference, enter the fix loop  -  do not rationalise that the snapshot is "close enough" or that the difference is "just the sample image". Ambiguous cases also enter the fix loop and surface the specific concern in the `fidelity_attempt_{N}.md` diagnosis.
 
 ### Pass criteria
 
 Both conditions must be met:
 
-1. **All tests pass** — exit code 0, no test failures
-2. **Zero build warnings** — review xcodebuild output for warnings in the component's test files. Fix any warnings before proceeding.
+1. **All tests pass**  -  exit code 0, no test failures
+2. **Zero build warnings**  -  review xcodebuild output for warnings in the component's test files. Fix any warnings before proceeding.
 
 ### Exit codes
 
@@ -294,7 +294,7 @@ After tests pass (exit 0), review the output for any warnings in the component's
 
 | Warning | Fix |
 |---------|-----|
-| `'Inspectable' is deprecated` | Remove the `extension {ComponentName}: Inspectable {}` line — no longer required by ViewInspector |
+| `'Inspectable' is deprecated` | Remove the `extension {ComponentName}: Inspectable {}` line  -  no longer required by ViewInspector |
 | `main actor-isolated property` | Add `@MainActor` to the test class |
 | Unused variable | Remove or use the variable |
 
@@ -318,7 +318,7 @@ USER_ACTION_REQUIRED: Fix the failing tests and re-run.
 
 Validate that all generated test files follow the required patterns and that no tests are skipped.
 
-### 5.1 Structural validation — ViewInspector test file
+### 5.1 Structural validation  -  ViewInspector test file
 
 Check the ViewInspector test file at `Tests/{sourceModule}Tests/ViewInspector/{componentPath}/{componentName}ViewInspectorTests.swift`:
 
@@ -334,11 +334,11 @@ Check the ViewInspector test file at `Tests/{sourceModule}Tests/ViewInspector/{c
 [ ] Has `test_containsExpectedSubviews()` test
 [ ] Has variant rendering tests (e.g., `test_allStatesRender`)
 [ ] Has accessibility identifier tests for each testing ID
-[ ] No `XCTSkip` — all tests must execute
-[ ] No `throw XCTSkip` — no conditional skipping
+[ ] No `XCTSkip`  -  all tests must execute
+[ ] No `throw XCTSkip`  -  no conditional skipping
 ```
 
-### 5.2 Structural validation — Snapshot test file
+### 5.2 Structural validation  -  Snapshot test file
 
 Check the Snapshot test file at `Tests/{sourceModule}Tests/Snapshot/{componentPath}/{componentName}SnapshotTests.swift`:
 
@@ -356,7 +356,7 @@ Check the Snapshot test file at `Tests/{sourceModule}Tests/Snapshot/{componentPa
 [ ] Each helper uses `.image(precision: 0.99, perceptualPrecision: 0.98)`
 [ ] RTL helpers set `.semanticContentAttribute = .forceRightToLeft`
 [ ] Dark helpers set `.overrideUserInterfaceStyle = .dark`
-[ ] No `XCTSkip` — all tests must execute
+[ ] No `XCTSkip`  -  all tests must execute
 ```
 
 ### 5.3 Test naming convention
@@ -411,10 +411,10 @@ python3 .instructions/figma/figma-to-swiftui/scripts/phase5-finalize.py \
 
 | Result | Action |
 |--------|--------|
-| Exit 0, `"action": "updated"` | `status.ios.tested` set green, `against = implemented.version` — proceed |
-| Exit 0, `"action": "already_current"` | Already marked against current implemented.version — proceed |
-| Exit 0, `"action": "created"` | New registry file created — proceed |
-| Exit 1 | HALT — registry update failed |
+| Exit 0, `"action": "updated"` | `status.ios.tested` set green, `against = implemented.version`  -  proceed |
+| Exit 0, `"action": "already_current"` | Already marked against current implemented.version  -  proceed |
+| Exit 0, `"action": "created"` | New registry file created  -  proceed |
+| Exit 1 | HALT  -  registry update failed |
 
 **Why this matters:** This is the single source of truth for `status.ios.tested`. The script records `against = status.ios.implemented.version` so when the next Phase 4 bumps `implemented.version`, this flag automatically drops to yellow until tests are re-run. `figma-iteration-commit` reads this and syncs the GitHub issue via `update-issue-from-registry.py`.
 
@@ -439,10 +439,10 @@ GATES_PASSED: [PRE_CHECK, CREATE_TEST_INDEX, ROUTING, UPDATE_TEST_INDEX, TEST_EX
 ARTIFACTS_CREATED:
   - {artifactPath}/pass5/_test_index.md
 SUB_PHASES:
-  - 5A ViewInspector: {COUNT} tests — {testFilePath}
-  - 5B Snapshot: {COUNT} tests ({LIGHT} light + {DARK} dark + {RTL} RTL) — {testFilePath}
-  - 5C Unit: {COUNT} tests or N/A — {testFilePath or N/A}
-TESTS: ✅ PASS (xcodebuild test — zero warnings, all tests green)
+  - 5A ViewInspector: {COUNT} tests  -  {testFilePath}
+  - 5B Snapshot: {COUNT} tests ({LIGHT} light + {DARK} dark + {RTL} RTL)  -  {testFilePath}
+  - 5C Unit: {COUNT} tests or N/A  -  {testFilePath or N/A}
+TESTS: ✅ PASS (xcodebuild test  -  zero warnings, all tests green)
 VALIDATION: ✅ PASS (structure + naming + variant coverage)
 SUMMARY: Phase 5 testing complete. {TOTAL} tests across {FILE_COUNT} test files. Zero warnings. All tests passing.
 ```
@@ -453,19 +453,19 @@ SUMMARY: Phase 5 testing complete. {TOTAL} tests across {FILE_COUNT} test files.
 
 ```
 [ ] pass5/_test_index.md created with all artifact paths
-[ ] 5A ViewInspector test file created — structure, accessibility, variant rendering tests
-[ ] 5B Snapshot test file created — light/dark/RTL variants, snapshot helpers
+[ ] 5A ViewInspector test file created  -  structure, accessibility, variant rendering tests
+[ ] 5B Snapshot test file created  -  light/dark/RTL variants, snapshot helpers
 [ ] 5C Unit tests created OR marked N/A (no testable logic)
 [ ] Test index updated with final status
 [ ] All test files follow existing project patterns (XCTest, makeSUT, closure init)
 [ ] xcodebuild test passed (exit 0, all tests green)
 [ ] Zero build warnings in component test files
-[ ] No XCTSkip in any test file — all tests must execute
+[ ] No XCTSkip in any test file  -  all tests must execute
 [ ] Snapshot test naming follows test_snapshot_{mode}_{variant} convention
 [ ] ViewInspector tests cover all accessibility identifiers
 [ ] Snapshot tests cover ALL Figma variant dimensions (light + dark minimum)
 [ ] RTL snapshot tests present for components with text/localized content
-[ ] Snapshot reference images generated locally (NOT committed — gitignored)
+[ ] Snapshot reference images generated locally (NOT committed  -  gitignored)
 [ ] phase5-finalize.py passed (status.ios.tested updated)
 ```
 

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-5a-viewinspector.md

@@ -1,15 +1,15 @@
-# PHASE 5A — ViewInspector Structure Tests
+# PHASE 5A  -  ViewInspector Structure Tests
 
 ViewInspector-based tests verifying view hierarchy, text content, and accessibility identifiers.
 
 PARENT: `phase-5-orchestrator.md`
-required — always execute this sub-phase.
+required  -  always execute this sub-phase.
 
-**FRAMEWORK**: XCTest (NOT Swift Testing — ViewInspector has issues with `@Test`, see GitHub #319)
+**FRAMEWORK**: XCTest (NOT Swift Testing  -  ViewInspector has issues with `@Test`, see GitHub #319)
 
 ### Naming Convention
 
-REF: [Kodeco — iOS Test-Driven Development by Tutorials](https://www.kodeco.com/books/ios-test-driven-development-by-tutorials/v2.0/chapters/3-tdd-app-setup)
+REF: [Kodeco  -  iOS Test-Driven Development by Tutorials](https://www.kodeco.com/books/ios-test-driven-development-by-tutorials/v2.0/chapters/3-tdd-app-setup)
 
 Pattern: `test_{systemUnderTest}_{whenCondition}_{expectedResult}`
 
@@ -49,7 +49,7 @@ Test File:   {componentName}ViewInspectorTests.swift
 
 | Check | Pass | Fail |
 |-------|------|------|
-| `{sourceModule}Tests` target exists | Proceed | HALT — add test target first |
+| `{sourceModule}Tests` target exists | Proceed | HALT  -  add test target first |
 | Dependencies include ExternalViewInspector, ExternalSnapshotTesting | Proceed | HALT |
 
 ---
@@ -73,7 +73,7 @@ import ViewInspector
 import XCTest
 @testable import {sourceModule}
 
-// NOTE: Do NOT add `extension {componentName}: Inspectable {}` — deprecated since ViewInspector 0.10+
+// NOTE: Do NOT add `extension {componentName}: Inspectable {}`  -  deprecated since ViewInspector 0.10+
 
 @MainActor
 final class {componentName}ViewInspectorTests: XCTestCase {
@@ -270,5 +270,5 @@ PHASE: phase-5a
 GATES_PASSED: [PRE_CHECK, DETERMINE_TEST_LOCATION, CREATE_TEST_FILE, IMPLEMENT_STRUCTURE_TESTS, IMPLEMENT_ACCESSIBILITY_TESTS, RUN_TESTS]
 ARTIFACTS_CREATED:
   - Tests/{sourceModule}Tests/ViewInspector/{componentPath}/{componentName}ViewInspectorTests.swift
-SUMMARY: {COUNT} ViewInspector tests — structure ({STRUCT_COUNT}), accessibility identifiers ({ID_COUNT}), variants ({VARIANT_COUNT}).
+SUMMARY: {COUNT} ViewInspector tests  -  structure ({STRUCT_COUNT}), accessibility identifiers ({ID_COUNT}), variants ({VARIANT_COUNT}).
 ```

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-5b-snapshot.md

@@ -1,9 +1,9 @@
-# PHASE 5B — Snapshot Tests
+# PHASE 5B  -  Snapshot Tests
 
 Snapshot visual regression tests for ALL Figma variants in light and dark mode.
 
 PARENT: `phase-5-orchestrator.md`
-required — always execute this sub-phase.
+required  -  always execute this sub-phase.
 PARALLEL WITH: Phase 5A (both read from pass5/_test_index.md independently)
 
 **FRAMEWORK**: XCTest with swift-snapshot-testing (via ExternalSnapshotTesting)
@@ -100,30 +100,30 @@ Without this, white components are invisible against the default white snapshot
 
 ### 3.0.1 Remote Image Initialization (required if the component uses `RemoteImage` / Kingfisher)
 
-**CRITICAL — this gate is easy to miss and produces silent false positives.**
+**CRITICAL  -  this gate is easy to miss and produces silent false positives.**
 
-If the component (or any nested component it composes) renders images via `CoreUI.RemoteImage` / Kingfisher / any async image loader, the snapshot test MUST include image-initialization scaffolding. Without it, the snapshot captures the KFImage **placeholder state** — the first and every subsequent run compare placeholder to placeholder, so the tests "pass" while the reference PNGs contain no real image pixels at all.
+If the component (or any nested component it composes) renders images via `CoreUI.RemoteImage` / Kingfisher / any async image loader, the snapshot test MUST include image-initialization scaffolding. Without it, the snapshot captures the KFImage **placeholder state**  -  the first and every subsequent run compare placeholder to placeholder, so the tests "pass" while the reference PNGs contain no real image pixels at all.
 
-**How to detect the need**: if `pass3/04b_component_architecture.md` / `pass3/04_patterns.md` / `pass3/06_assets.md` mentions `RemoteImage`, `Kingfisher`, `KFImage`, image URL, remote image, or the component consumes any protocol/config with an `imageURL: URL` field, you MUST apply this gate. Also check if any **nested** component uses remote images — the parent inherits the requirement transitively.
+**How to detect the need**: if `pass3/04b_component_architecture.md` / `pass3/04_patterns.md` / `pass3/06_assets.md` mentions `RemoteImage`, `Kingfisher`, `KFImage`, image URL, remote image, or the component consumes any protocol/config with an `imageURL: URL` field, you MUST apply this gate. Also check if any **nested** component uses remote images  -  the parent inherits the requirement transitively.
 
-**NEVER use `usleep` on the main thread in either the prefetch or the image wait.** Kingfisher dispatches its `retrieveImage` completion handlers and KFImage's view-delivery updates back to the **main queue**. `usleep` blocks the main runloop, so those callbacks never fire, the cache never warms, and the snapshot captures a placeholder. Use `RunLoop.main.run(until:)` to spin the runloop instead — that allows queued main-actor work to drain while you wait. See the sibling `Homepage3rdPartyCardSnapshotTests.swift` for the canonical 20 ms pattern, and `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift` for the composite-view 4 s pattern (same rule, longer deadline).
+**NEVER use `usleep` on the main thread in either the prefetch or the image wait.** Kingfisher dispatches its `retrieveImage` completion handlers and KFImage's view-delivery updates back to the **main queue**. `usleep` blocks the main runloop, so those callbacks never fire, the cache never warms, and the snapshot captures a placeholder. Use `RunLoop.main.run(until:)` to spin the runloop instead  -  that allows queued main-actor work to drain while you wait. See the sibling `Homepage3rdPartyCardSnapshotTests.swift` for the canonical 20 ms pattern, and `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift` for the composite-view 4 s pattern (same rule, longer deadline).
 
 **Required scaffolding** (both references together show the full pattern):
 
-1. **Module imports** — `@testable import CoreUI` + `import Kingfisher` in addition to the usual `SnapshotTesting` / `SwiftUI` / `XCTest`.
-2. **Deterministic seeded URLs** — file-scope `let`s like `URL(string: "https://picsum.photos/seed/{slug}/{W}/{H}")!`. Seeds return the same image bytes for identical URLs → stable snapshots. Do NOT use unseeded picsum, placehold.it, or any URL that returns different bytes per request.
-3. **`@MainActor private func prefetchVariantImages(timeout:)`** — kicks `KingfisherManager.shared.retrieveImage(with:)` for every URL and **spins `RunLoop.main.run(until:)`** until every completion callback has fired (not `usleep`, not `isCached` polling). Use a `@MainActor final class` counter (`MainActor.assumeIsolated { counter.remaining -= 1 }` inside the completion) to satisfy Swift 6 concurrency rules — a captured `var Int` inside the closure will not compile. 20 s timeout is safe; the runloop exits early once the counter hits zero.
-4. **`override class func setUp()`** — after `TestDependencies.registerAll()`, set `RemoteImageConfiguration.shared.fadeDuration = 0`. This disables KFImage's crossfade animation so cached pixels appear on the first layout pass instead of fading in mid-snapshot.
-5. **`override func setUp()`** — call `prefetchVariantImages()` before every test, so each test sees warm cache.
-6. **`waitForImages()` helper** — **`RunLoop.main.run(until: Date().addingTimeInterval({seconds}))`**, NOT `usleep`. Call it in every assert helper AFTER `vc.view.layoutIfNeeded()` and BEFORE `SnapshotTesting.assertSnapshot(...)`. Duration depends on how many `RemoteImage` instances the view composes **simultaneously**:
+1. **Module imports**  -  `@testable import CoreUI` + `import Kingfisher` in addition to the usual `SnapshotTesting` / `SwiftUI` / `XCTest`.
+2. **Deterministic seeded URLs**  -  file-scope `let`s like `URL(string: "https://picsum.photos/seed/{slug}/{W}/{H}")!`. Seeds return the same image bytes for identical URLs → stable snapshots. Do NOT use unseeded picsum, placehold.it, or any URL that returns different bytes per request.
+3. **`@MainActor private func prefetchVariantImages(timeout:)`**  -  kicks `KingfisherManager.shared.retrieveImage(with:)` for every URL and **spins `RunLoop.main.run(until:)`** until every completion callback has fired (not `usleep`, not `isCached` polling). Use a `@MainActor final class` counter (`MainActor.assumeIsolated { counter.remaining -= 1 }` inside the completion) to satisfy Swift 6 concurrency rules  -  a captured `var Int` inside the closure will not compile. 20 s timeout is safe; the runloop exits early once the counter hits zero.
+4. **`override class func setUp()`**  -  after `TestDependencies.registerAll()`, set `RemoteImageConfiguration.shared.fadeDuration = 0`. This disables KFImage's crossfade animation so cached pixels appear on the first layout pass instead of fading in mid-snapshot.
+5. **`override func setUp()`**  -  call `prefetchVariantImages()` before every test, so each test sees warm cache.
+6. **`waitForImages()` helper**  -  **`RunLoop.main.run(until: Date().addingTimeInterval({seconds}))`**, NOT `usleep`. Call it in every assert helper AFTER `vc.view.layoutIfNeeded()` and BEFORE `SnapshotTesting.assertSnapshot(...)`. Duration depends on how many `RemoteImage` instances the view composes **simultaneously**:
 
    | Simultaneous async-image views | `waitForImages` duration | Canonical reference |
    |---|---|---|
    | 1 (single card, single banner, etc.) | 20 ms (`usleep(20_000)` is OK for single-view, but `RunLoop.main.run` is still safer) | `Homepage3rdPartyCardSnapshotTests.swift` |
-   | 2–4 (group / row / carousel composing multiple cards) | 2–4 s via `RunLoop.main.run(until:)` | `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift` |
-   | 5+ (lists, grids, large composites) | 4–6 s via `RunLoop.main.run(until:)`; consider also capping list length to 3–5 in `makeSUT` |
+   | 2-4 (group / row / carousel composing multiple cards) | 2-4 s via `RunLoop.main.run(until:)` | `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift` |
+   | 5+ (lists, grids, large composites) | 4-6 s via `RunLoop.main.run(until:)`; consider also capping list length to 3-5 in `makeSUT` |
 
-7. **Frame width sanity** — if the SUT renders a section title or horizontal carousel, make sure the snapshot frame width is wide enough to include the title and at least one full card. Clipped titles are a visible smoke signal that the frame is too narrow.
+7. **Frame width sanity**  -  if the SUT renders a section title or horizontal carousel, make sure the snapshot frame width is wide enough to include the title and at least one full card. Clipped titles are a visible smoke signal that the frame is too narrow.
 
 **Skeleton** (adapt to single-view OR composite-view shape per the table above):
 
@@ -147,7 +147,7 @@ private final class PrefetchCounter {
 
 /// Warms Kingfisher's memory cache for all variant URLs and spins the main
 /// runloop until every completion callback fires (or the deadline expires).
-/// Spinning the runloop is required — usleep on main would starve the
+/// Spinning the runloop is required  -  usleep on main would starve the
 /// Kingfisher callbacks and the cache would never warm.
 @MainActor
 private func prefetchVariantImages(timeout: TimeInterval = 20.0) {
@@ -178,10 +178,10 @@ final class {ComponentName}SnapshotTests: XCTestCase {
         prefetchVariantImages()                             // required
     }
 
-    /// required — uses RunLoop.main.run(until:), never usleep.
+    /// required  -  uses RunLoop.main.run(until:), never usleep.
     /// Duration scales with # of simultaneous RemoteImage views (see table
-    /// in phase-5b § 3.0.1). 20 ms is enough for a single-card SUT;
-    /// 2–4 s is required for composite views that render multiple cards
+    /// in phase-5b section 3.0.1). 20 ms is enough for a single-card SUT;
+    /// 2-4 s is required for composite views that render multiple cards
     /// at once.
     private func waitForImages() {
         RunLoop.main.run(until: Date().addingTimeInterval(/* single: 0.02 | composite: 4.0 */))
@@ -202,25 +202,25 @@ final class {ComponentName}SnapshotTests: XCTestCase {
 1. Delete any pre-existing PNGs under `__Snapshots__/{ComponentName}SnapshotTests/`.
 2. Run the suite once. Expect failures on first run (`.missing` mode auto-records).
 3. Open at least one recorded PNG visually and confirm every card/image slot shows **real photographic content**, not a Kingfisher placeholder (light gradient + activity spinner) and not an all-blank background.
-4. Check file sizes: real photographic snapshots are typically 100 KB – 2 MB. A composite PNG at <50 KB is a strong signal of placeholder capture.
-5. Run the suite a second time — it MUST pass on the regression run. If not, increase `waitForImages` duration.
+4. Check file sizes: real photographic snapshots are typically 100 KB - 2 MB. A composite PNG at <50 KB is a strong signal of placeholder capture.
+5. Run the suite a second time  -  it MUST pass on the regression run. If not, increase `waitForImages` duration.
 6. Only commit PNGs (if tracked) and the test file together, never separately.
 
-**Root-cause note (why this gate exists):** the template in § 3.1 below references `ExploreCityDetailAboutCitySnapshotTests.swift`, which does NOT use remote images. A subagent that copies only the § 3.1 template will silently omit the scaffolding above and produce tests that lock in placeholder reference PNGs. This has happened in real runs:
+**Root-cause note (why this gate exists):** the template in section 3.1 below references `ExploreCityDetailAboutCitySnapshotTests.swift`, which does NOT use remote images. A subagent that copies only the section 3.1 template will silently omit the scaffolding above and produce tests that lock in placeholder reference PNGs. This has happened in real runs:
 
-- `HomepageAdditionalServices3rdPartyGroupSnapshotTests` ({jira.projectKey}-132403): first fix copied the sibling's `usleep(20_000)` wait verbatim — the composite renders **three** `Homepage3rdPartyCard` instances simultaneously, and 20 ms wasn't enough for all three to drain. Second fix replaced both the prefetch poll AND the image wait with `RunLoop.main.run(until:)` and extended the wait to 4 s. Reference PNGs went from 65 KB (placeholder) to 750 KB – 1.76 MB (real photos).
+- `HomepageAdditionalServices3rdPartyGroupSnapshotTests` ({jira.projectKey}-132403): first fix copied the sibling's `usleep(20_000)` wait verbatim  -  the composite renders **three** `Homepage3rdPartyCard` instances simultaneously, and 20 ms wasn't enough for all three to drain. Second fix replaced both the prefetch poll AND the image wait with `RunLoop.main.run(until:)` and extended the wait to 4 s. Reference PNGs went from 65 KB (placeholder) to 750 KB - 1.76 MB (real photos).
 
-**If the component renders a single `RemoteImage`, the canonical reference is `Homepage3rdPartyCardSnapshotTests.swift`. If the component composes multiple `RemoteImage` instances simultaneously, the canonical reference is `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift`.** Neither the Explore reference nor the generic § 3.1 template is appropriate for remote-image components.
+**If the component renders a single `RemoteImage`, the canonical reference is `Homepage3rdPartyCardSnapshotTests.swift`. If the component composes multiple `RemoteImage` instances simultaneously, the canonical reference is `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift`.** Neither the Explore reference nor the generic section 3.1 template is appropriate for remote-image components.
 
 ### 3.1 Template
 
 Pick the canonical reference based on what the component renders:
 
-| Component shape | Canonical reference | § 3.0.1 scaffolding |
+| Component shape | Canonical reference | section 3.0.1 scaffolding |
 |---|---|---|
 | Pure SwiftUI, no remote images | `ExploreCityDetailAboutCitySnapshotTests.swift` | Not required |
 | Single `RemoteImage` / Kingfisher instance | `Homepage3rdPartyCardSnapshotTests.swift` | **Required** (single-view variant) |
-| Composite view with 2+ `RemoteImage` instances rendered simultaneously | `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift` | **Required** (composite variant, 2–4 s `RunLoop.main.run` wait) |
+| Composite view with 2+ `RemoteImage` instances rendered simultaneously | `HomepageAdditionalServices3rdPartyGroupSnapshotTests.swift` | **Required** (composite variant, 2-4 s `RunLoop.main.run` wait) |
 
 Then follow the established project pattern from the chosen reference:
 
@@ -564,7 +564,7 @@ func test_snapshot_en_dark_{caseName}() {
 
 ## GATE 6: RUN_AND_RECORD
 
-### 6.1 First Run — Record Reference Snapshots
+### 6.1 First Run  -  Record Reference Snapshots
 
 **IMPORTANT:** Use `xcodebuild`, NOT `swift test`. The project uses Xcode-specific features (`ColorResource`, `ImageResource`, asset catalogs) that are unavailable in SPM's `swift build`/`swift test`.
 
@@ -590,7 +590,7 @@ Tests/{sourceModule}Tests/__Snapshots__/{componentName}SnapshotTests/
 |----------|--------|--------|
 | {EXPECTED_COUNT} total | {ACTUAL_COUNT} recorded | pass/fail |
 
-### 6.3 Second Run — Verify Regression
+### 6.3 Second Run  -  Verify Regression
 
 ```bash
 cd {repos.components.path} && \
@@ -632,5 +632,5 @@ GATES_PASSED: [PRE_CHECK, DETERMINE_VARIANT_MATRIX, DETERMINE_TEST_LOCATION, CRE
 ARTIFACTS_CREATED:
   - Tests/{sourceModule}Tests/Snapshot/{componentPath}/{componentName}SnapshotTests.swift
   - Tests/{sourceModule}Tests/__Snapshots__/{componentName}SnapshotTests/*.png
-SUMMARY: {COUNT} snapshot tests — {ENUM_COUNT} enum variants × 2 themes + {OPTIONAL_COUNT} optional variants × 2 themes + {RTL_COUNT} RTL variants × 2 themes + {LOCALE_COUNT} locale variants (TR/EN) × 2 themes = {TOTAL} snapshots.
+SUMMARY: {COUNT} snapshot tests  -  {ENUM_COUNT} enum variants × 2 themes + {OPTIONAL_COUNT} optional variants × 2 themes + {RTL_COUNT} RTL variants × 2 themes + {LOCALE_COUNT} locale variants (TR/EN) × 2 themes = {TOTAL} snapshots.
 ```

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-5c-unit.md

@@ -1,9 +1,9 @@
-# PHASE 5C — Unit Tests
+# PHASE 5C  -  Unit Tests
 
 Unit tests for component logic: ViewModel, model computed properties, data transformations.
 
 PARENT: `phase-5-orchestrator.md`
-CONDITIONAL — only execute if component has testable logic.
+CONDITIONAL  -  only execute if component has testable logic.
 
 **FRAMEWORK**: Swift Testing (`@Test`, `#expect`, `@Suite`)
 
@@ -15,15 +15,15 @@ Read the component source file. Determine if testable logic exists.
 
 | Component Has | Action |
 |---------------|--------|
-| ViewModel class (`ObservableObject`) | Execute — test state mutations |
-| Model with computed properties | Execute — test computations |
-| Data transformation functions | Execute — test transformations |
-| Action handlers with branching logic | Execute — test branches |
-| Pure View only (configuration + body) | **N/A — skip this sub-phase** |
+| ViewModel class (`ObservableObject`) | Execute  -  test state mutations |
+| Model with computed properties | Execute  -  test computations |
+| Data transformation functions | Execute  -  test transformations |
+| Action handlers with branching logic | Execute  -  test branches |
+| Pure View only (configuration + body) | **N/A  -  skip this sub-phase** |
 
 Most Figma-generated components are pure Views with a Configuration struct and a body.
 Configuration structs with only stored properties have no testable logic.
-`@GenerateChainModifiers` and `@GenerateConfiguredInit` are macro-generated — tested by UIMacrosTests, not here.
+`@GenerateChainModifiers` and `@GenerateConfiguredInit` are macro-generated  -  tested by UIMacrosTests, not here.
 
 N/A →
 ```
@@ -138,5 +138,5 @@ PHASE: phase-5c
 GATES_PASSED: [LOGIC_CHECK, PRE_CHECK, DETERMINE_TEST_LOCATION, IDENTIFY_TESTABLE_UNITS, CREATE_TEST_FILE, RUN_TESTS]
 ARTIFACTS_CREATED:
   - Tests/{sourceModule}Tests/Unit/{componentPath}/{componentName}Tests.swift
-SUMMARY: {COUNT} unit tests — ViewModel ({VM_COUNT}), Model ({MODEL_COUNT}).
+SUMMARY: {COUNT} unit tests  -  ViewModel ({VM_COUNT}), Model ({MODEL_COUNT}).
 ```