@mmerterden/multi-agent-pipeline 8.6.2 → 10.2.0

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-0-init.md

@@ -1,4 +1,4 @@
-# PHASE 0 — Component Initialization
+# PHASE 0  -  Component Initialization
 
 Setup component context and create artifact directory before implementation.
 NEXT: Phase 1 (Data Gathering)
@@ -75,7 +75,7 @@ QUESTION: No node ID found in user input.
 OPTIONS:
   1) Provide Figma URL (format: https://figma.com/design/KEY/Name?node-id=X-Y)
   2) Provide node ID directly (format: X:Y)
-SUGGESTED: Option 1 — paste the full Figma URL
+SUGGESTED: Option 1  -  paste the full Figma URL
 COMPLETED_GATES: [PRE_CHECK_SETUP]
 CONTEXT: A Figma URL or node ID is required to start implementation.
 ```
@@ -118,7 +118,7 @@ OPTIONS:
   1) Update registry first (run registry update command)
   2) Provide component name and location manually
   3) Check if node ID is correct
-SUGGESTED: Option 1 — registry may be outdated
+SUGGESTED: Option 1  -  registry may be outdated
 COMPLETED_GATES: [PRE_CHECK_SETUP, EXTRACT_NODE_ID]
 CONTEXT: The FigmaRegistryUtility lookup returned no results for node ID <NODE_ID>.
 ```
@@ -133,9 +133,9 @@ Resolve `componentName`, `componentLocation`, and `artifactPath` using this prio
 
 | Field | Priority 1 (highest) | Priority 2 | Priority 3 (lowest) |
 |-------|---------------------|------------|---------------------|
-| `componentName` | User-provided in prompt | Suggested by registry | HALT — ask user |
-| `componentLocation` | User-provided in prompt | `suggestedComponentLocation` from registry | HALT — ask user |
-| `artifactPath` | Derived from final `componentName` if name changed | `suggestedArtifactPath` from registry | HALT — ask user |
+| `componentName` | User-provided in prompt | Suggested by registry | HALT  -  ask user |
+| `componentLocation` | User-provided in prompt | `suggestedComponentLocation` from registry | HALT  -  ask user |
+| `artifactPath` | Derived from final `componentName` if name changed | `suggestedArtifactPath` from registry | HALT  -  ask user |
 
 **How to detect user overrides:** Scan the user's original prompt for explicit name or location mentions:
 - `"implement as PackageBadge"` → override componentName
@@ -143,14 +143,14 @@ Resolve `componentName`, `componentLocation`, and `artifactPath` using this prio
 - `"put it in Sources/UIComponents/Booking/"` → override componentLocation
 - Any PascalCase word the user associates with the component → override componentName
 
-If user provided an override in their prompt, use it directly — do NOT ask for confirmation.
-If user did NOT provide an override, use the registry suggestion — but check for vague names first.
+If user provided an override in their prompt, use it directly  -  do NOT ask for confirmation.
+If user did NOT provide an override, use the registry suggestion  -  but check for vague names first.
 
 ### 3.2 Vague name detection
 
 Registry names derived from Figma layer hierarchy can be too generic. Check if `suggestedComponentName` is vague:
 
-**Vague indicators** — single common word that doesn't describe the component's purpose:
+**Vague indicators**  -  single common word that doesn't describe the component's purpose:
 - Generic containers: `Package`, `Card`, `Item`, `Cell`, `Row`, `View`, `Container`, `Component`, `Element`, `Block`, `Section`, `Group`, `Box`, `Wrapper`
 - Generic actions: `Button`, `Label`, `Icon`, `Badge`, `Tag`, `Chip`, `Indicator`
 - Generic layout: `Header`, `Footer`, `Content`, `Body`, `Stack`, `List`
@@ -277,8 +277,8 @@ ls {artifactPath}/pass0/specs.md 2>/dev/null
 ```
 
 **If specs exist:** read the file and store as `implementationSpecs`. These specs will be passed to subsequent phases as additional context:
-- Phase 3 (Analysis) — informs pattern decisions
-- Phase 4 (Implementation) — constrains the init signature, defaults, and behavior
+- Phase 3 (Analysis)  -  informs pattern decisions
+- Phase 4 (Implementation)  -  constrains the init signature, defaults, and behavior
 
 Append to IMPLEMENTATION_HISTORY.md:
 ```markdown
@@ -287,7 +287,7 @@ Append to IMPLEMENTATION_HISTORY.md:
 - Loaded: <DATE>
 ```
 
-**If no specs file:** continue without. No error — specs are optional.
+**If no specs file:** continue without. No error  -  specs are optional.
 
 ---
 

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-1-gathering.md

@@ -1,4 +1,4 @@
-# Phase 1 — Data Gathering
+# Phase 1  -  Data Gathering
 
 ## Overview
 
@@ -28,7 +28,7 @@ Phase 1 is done. All artifacts are in `pass1/`. Proceed to Phase 2.
 
 ### If `status` = `COMPLETE_WITH_DEFERRED`
 
-The script completed all data gathering **except** `get_design_context`, which was deferred because the component has too many sublayers (>20). Report status to orchestrator — it will dispatch a Phase 1 subagent for deferred resolution.
+The script completed all data gathering **except** `get_design_context`, which was deferred because the component has too many sublayers (>20). Report status to orchestrator  -  it will dispatch a Phase 1 subagent for deferred resolution.
 
 ---
 
@@ -52,9 +52,9 @@ Classify each variant axis:
 
 | Category | Examples | Action |
 |----------|----------|--------|
-| **Interaction** | `State` (Default/Hover/Pressed/Disabled), focus/hover variants | Fix to `Default` (only color/opacity changes — no structural difference) |
+| **Interaction** | `State` (Default/Hover/Pressed/Disabled), focus/hover variants | Fix to `Default` (only color/opacity changes  -  no structural difference) |
 | **Theme** | `Color`, `Theme`, `Mode` | Fix to first value (e.g., `Brand`) |
-| **Structural** | `Size`, `Style`, `IconDirection`, `Type`, `Layout`, everything else | **Vary** — these change layout/structure |
+| **Structural** | `Size`, `Style`, `IconDirection`, `Type`, `Layout`, everything else | **Vary**  -  these change layout/structure |
 
 Calculate structural combinations:
 - If <= 20: fetch all structural combinations (with interaction + theme fixed).
@@ -66,7 +66,7 @@ Each sublayer in Figma is a variant named like `Color=Brand, Size=Default, Style
 
 The `sublayerIds` list in `design_context_deferred.json` corresponds to the children of the component set. To map selected variant combinations to node IDs:
 
-1. Read `{artifactPath}/pass1/screenshots/variants.md` — it has a table of `Variant | Node ID | File`.
+1. Read `{artifactPath}/pass1/screenshots/variants.md`  -  it has a table of `Variant | Node ID | File`.
 2. Match your selected combinations against the variant names.
 3. Collect the node IDs for matched variants.
 

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-1.5-existing-discovery.md

@@ -1,9 +1,9 @@
-# PHASE 1.5 — Existing Component Discovery
+# PHASE 1.5  -  Existing Component Discovery
 
 Detects whether the target component is already implemented in the codebase OR already mapped via Code Connect, BEFORE Phase 2 starts greenfield generation. Without this gate, the pipeline can silently overwrite existing implementations and re-publish duplicate Code Connect mappings.
 
 PREV: Phase 1 (Data Gathering)
-NEXT: Phase 2 (Utility Integration) — only when status is `GREENFIELD_OK`
+NEXT: Phase 2 (Utility Integration)  -  only when status is `GREENFIELD_OK`
 REF: `phase-6-code-connect.md` (publish gate honors discovery output)
 
 ---
@@ -12,12 +12,12 @@ REF: `phase-6-code-connect.md` (publish gate honors discovery output)
 
 | Condition | Action |
 |---|---|
-| `pass1/code_connect_map_response.json` missing | HALT — Phase 1 didn't complete cleanly |
+| `pass1/code_connect_map_response.json` missing | HALT  -  Phase 1 didn't complete cleanly |
 | All other cases | EXECUTE |
 
 ---
 
-## STEP 1 — Inspect Code Connect map for self-reference
+## STEP 1  -  Inspect Code Connect map for self-reference
 
 INPUT: `{artifactPath}/pass1/code_connect_map_response.json`
 
@@ -26,7 +26,7 @@ The map is a `{ nodeId: { codeConnectSrc, codeConnectName } }` lookup. The curre
 ```python
 # Pseudocode
 target_node_id = state.issue.nodeId    # e.g. "7528:23317"
-target_name    = state.issue.componentName  # PascalCase, e.g. "MilesSmilesAccountSettingsAirlineProgramMembershipLayout"
+target_name    = state.issue.componentName  # PascalCase, e.g. "MyComponentSettingsLayout"
 
 cc_map = json.load(open(f"{artifactPath}/pass1/code_connect_map_response.json"))
 
@@ -42,7 +42,7 @@ If `ALREADY_MAPPED`: the target Figma node is already wired to a code component.
 
 ---
 
-## STEP 2 — Search the codebase for an existing source file
+## STEP 2  -  Search the codebase for an existing source file
 
 If Step 1 returned no match, look for a file that matches the target component name. Use the project's component root (resolved from `figma-config.json` → `componentRoot` if set, else `Sources/UIComponents/Components/`).
 
@@ -54,9 +54,9 @@ Three outcomes:
 
 | Files found | Status |
 |---|---|
-| 0 | `GREENFIELD_OK` — proceed to Phase 2 normally |
-| 1 | `EXISTING_SOURCE_NO_CC` — file exists but Code Connect mapping is missing |
-| 2+ | `AMBIGUOUS_SOURCE` — multiple files match; needs user disambiguation |
+| 0 | `GREENFIELD_OK`  -  proceed to Phase 2 normally |
+| 1 | `EXISTING_SOURCE_NO_CC`  -  file exists but Code Connect mapping is missing |
+| 2+ | `AMBIGUOUS_SOURCE`  -  multiple files match; needs user disambiguation |
 
 For `EXISTING_SOURCE_NO_CC`, also check whether a sibling `.figma.swift` exists:
 
@@ -70,7 +70,7 @@ If `.figma.swift` is absent → the source exists but is fully unconnected.
 
 ---
 
-## STEP 3 — User decision (only on non-greenfield)
+## STEP 3  -  User decision (only on non-greenfield)
 
 When the orchestrator sees status `ALREADY_MAPPED`, `EXISTING_SOURCE_NO_CC`, or `AMBIGUOUS_SOURCE`, emit a `STATUS: NEEDS_INPUT` block to the parent multi-agent pipeline.
 
@@ -83,9 +83,9 @@ GATE: ALREADY_MAPPED
 DETECTED: {sourcePath} (already mapped to Figma node {nodeId})
 QUESTION: This Figma node is already wired to a code component. What should the pipeline do?
 OPTIONS:
-  1. Run gap analysis only (FIGMA.md / tests / wiki — fill what's missing, do NOT touch the component source)
-  2. Force regenerate (DANGER — overwrites the existing source file; only choose this if the design has materially changed)
-  3. Cancel — abort this run, no edits
+  1. Run gap analysis only (FIGMA.md / tests / wiki  -  fill what's missing, do NOT touch the component source)
+  2. Force regenerate (DANGER  -  overwrites the existing source file; only choose this if the design has materially changed)
+  3. Cancel  -  abort this run, no edits
 DEFAULT: 1
 ```
 
@@ -101,9 +101,9 @@ DETECTED: {sourcePath} exists in the codebase but is not connected to the Figma
 SIBLING_FIGMA_SWIFT: {present | absent}
 QUESTION: Found an existing source file matching {target_name}. What should the pipeline do?
 OPTIONS:
-  1. Add Code Connect only — write {target_name}.figma.swift next to the source, publish it (recommended when sibling absent)
-  2. Publish-only — sibling .figma.swift already exists; just run `figma connect publish` (recommended when sibling present)
-  3. Force regenerate — overwrite the source file with a fresh greenfield generation
+  1. Add Code Connect only  -  write {target_name}.figma.swift next to the source, publish it (recommended when sibling absent)
+  2. Publish-only  -  sibling .figma.swift already exists; just run `figma connect publish` (recommended when sibling present)
+  3. Force regenerate  -  overwrite the source file with a fresh greenfield generation
   4. Cancel
 DEFAULT: 2 if sibling present, else 1
 ```
@@ -119,13 +119,13 @@ CANDIDATES: <bulleted list of paths>
 QUESTION: Pick the canonical source for this Figma node, or cancel.
 OPTIONS:
   <one option per candidate>
-  N+1. None of the above — treat as greenfield
+  N+1. None of the above  -  treat as greenfield
   N+2. Cancel
 ```
 
 ---
 
-## STEP 4 — Gap analysis (only on ALREADY_MAPPED + user picked option 1)
+## STEP 4  -  Gap analysis (only on ALREADY_MAPPED + user picked option 1)
 
 When the existing component is reused, the orchestrator still checks what's missing:
 
@@ -136,7 +136,7 @@ SRC_DIR=$(dirname "$sourcePath")
 # Snapshot tests, ViewInspector tests, wiki MD, ...
 ```
 
-The gap list goes into `state.discovery.gaps[]`. Phases 2/3 are SKIPPED. Phase 4–7 run only the steps that target gaps:
+The gap list goes into `state.discovery.gaps[]`. Phases 2/3 are SKIPPED. Phase 4-7 run only the steps that target gaps:
 
 | Gap | Phase that fills it |
 |---|---|

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

@@ -1,4 +1,4 @@
-# PHASE 2 — Utility Integration Orchestrator
+# PHASE 2  -  Utility Integration Orchestrator
 
 Orchestrates Phase 2 sub-phases: dispatches sub-agents, collects results, writes pass2/_index.md.
 PREV: Phase 1.5 (Existing Component Discovery)
@@ -6,18 +6,18 @@ NEXT: Phase 3 (Data Analysis)
 
 ---
 
-## ENTRY GATE — discovery status
+## ENTRY GATE  -  discovery status
 
 Phase 2 reads `agent-state.discovery.status` written by Phase 1.5:
 
 | `discovery.status` | Phase 2 action |
 |---|---|
-| `GREENFIELD_OK` (or absent for backward compat) | EXECUTE — run all sub-phases below |
-| `GAP_ANALYSIS` | SKIP — Phase 2 outputs are not needed; jump to Phase 4 (only run Documentation / Code Connect / tests / wiki sub-phases that target the gap list) |
-| `ALREADY_MAPPED` (no user override) | SKIP — same as `GAP_ANALYSIS` |
-| `EXISTING_SOURCE_NO_CC` (publish-only path picked) | SKIP — jump to Phase 6 |
+| `GREENFIELD_OK` (or absent for backward compat) | EXECUTE  -  run all sub-phases below |
+| `GAP_ANALYSIS` | SKIP  -  Phase 2 outputs are not needed; jump to Phase 4 (only run Documentation / Code Connect / tests / wiki sub-phases that target the gap list) |
+| `ALREADY_MAPPED` (no user override) | SKIP  -  same as `GAP_ANALYSIS` |
+| `EXISTING_SOURCE_NO_CC` (publish-only path picked) | SKIP  -  jump to Phase 6 |
 | `CANCELLED` | HALT |
-| Any other value | HALT — unknown discovery state, refuse to proceed |
+| Any other value | HALT  -  unknown discovery state, refuse to proceed |
 
 If `discovery` field is absent on `agent-state.json`, log a one-line warning ("phase-1.5 not run; assuming GREENFIELD_OK") and proceed. This preserves backward compatibility with runs started before the discovery gate existed.
 
@@ -35,7 +35,7 @@ import UIComponentUtilities
 |----------|-----------|-------|
 | Testing | `View.accessibilityIdentifier(_ key: UITestingIdentifierKey)` | `.accessibilityIdentifier(.ComponentName.element)` |
 | Localization | `Text(_ key: LocalizationStringKey)` | `Text(.ComponentName.title)` |
-| Accessibility | `View.accessibilityLabel(_ key: LocalizedAccessibilityStringKey)` | Only when SwiftUI can't read visible text — many components need NO accessibility modifiers |
+| Accessibility | `View.accessibilityLabel(_ key: LocalizedAccessibilityStringKey)` | Only when SwiftUI can't read visible text  -  many components need NO accessibility modifiers |
 | Analytics | `View.analyticsButton(id:label:type:)` | `.analyticsButton(id: "id", label: "Submit", type: .primary)` |
 
 SOURCE: `Sources/UIComponentUtilities/`
@@ -91,7 +91,7 @@ Check the JSON structure:
 
 | Format | Detection | Action |
 |--------|-----------|--------|
-| Normal | `sublayers` is `false` or absent | No action needed — `response` field exists |
+| Normal | `sublayers` is `false` or absent | No action needed  -  `response` field exists |
 | Sublayer | `sublayers` is `true` | Concatenate all `responses` values (see below) |
 
 ### Sublayer normalization
@@ -104,7 +104,7 @@ If `sublayers: true`:
 4. Keep the original `sublayers`, `sublayerNodeIds`, and `responses` fields intact (for traceability)
 5. Write the updated JSON back to `{artifactPath}/pass1/design_context_response.json`
 
-After normalization, all sub-phases read the `response` field as usual — no sublayer awareness needed.
+After normalization, all sub-phases read the `response` field as usual  -  no sublayer awareness needed.
 
 ```json
 {
@@ -162,14 +162,14 @@ REGISTRY_LOOKUP
 ┌───────────────────────────────────┐
 │  PARALLEL DISPATCH (sub-agents)   │
 │                                   │
-│   2A — Testing Identifiers        │  ← required
-│   2B — Localization Keys          │  ← if visible text
-│   2C — Accessibility Keys         │  ← required
+│   2A  -  Testing Identifiers        │  ← required
+│   2B  -  Localization Keys          │  ← if visible text
+│   2C  -  Accessibility Keys         │  ← required
 │                                   │
 └───────────────────────────────────┘
     ↓ wait for all to complete
     ↓
-    2D — Analytics Events              ← if interactive elements (depends on 2A output)
+    2D  -  Analytics Events              ← if interactive elements (depends on 2A output)
     ↓
 COLLECT RESULTS
     ↓
@@ -216,13 +216,13 @@ After all sub-phases complete, verify each produced its artifacts (both JSON sid
 
 ```
 [ ] pass2/utility_identifiers.md exists (Phase 2A)
-[ ] pass2/utility_identifiers.json exists (Phase 2A — JSON sidecar)
-[ ] pass2/utility_localization.md exists (Phase 2B — or skipped placeholder)
-[ ] pass2/utility_localization.json exists (Phase 2B — JSON sidecar)
+[ ] pass2/utility_identifiers.json exists (Phase 2A  -  JSON sidecar)
+[ ] pass2/utility_localization.md exists (Phase 2B  -  or skipped placeholder)
+[ ] pass2/utility_localization.json exists (Phase 2B  -  JSON sidecar)
 [ ] pass2/utility_accessibility.md exists (Phase 2C)
-[ ] pass2/utility_accessibility.json exists (Phase 2C — JSON sidecar)
-[ ] pass2/utility_analytics.md exists (Phase 2D — or skipped placeholder)
-[ ] pass2/utility_analytics.json exists (Phase 2D — JSON sidecar)
+[ ] pass2/utility_accessibility.json exists (Phase 2C  -  JSON sidecar)
+[ ] pass2/utility_analytics.md exists (Phase 2D  -  or skipped placeholder)
+[ ] pass2/utility_analytics.json exists (Phase 2D  -  JSON sidecar)
 ```
 
 ANY markdown missing →
@@ -235,7 +235,7 @@ MISSING: [list missing files]
 USER_ACTION_REQUIRED: Re-run the failed sub-phase.
 ```
 
-If a JSON sidecar is missing but the markdown exists, the finalize script will log a warning and use empty arrays — this is non-blocking.
+If a JSON sidecar is missing but the markdown exists, the finalize script will log a warning and use empty arrays  -  this is non-blocking.
 
 ---
 
@@ -293,10 +293,10 @@ Using the counts from the finalize script output, append to `{artifactPath}/IMPL
 [ ] design_context_response.json normalized (sublayer → flat response field)
 [ ] Registry lookup performed (utility-lookup)
 [ ] Pre-existing keys passed to sub-phases (if registry data found)
-[ ] Phase 2A completed — utility_identifiers.md + .json exists (required)
-[ ] Phase 2B completed — utility_localization.md + .json exists (or skipped with placeholder)
-[ ] Phase 2C completed — utility_accessibility.md + .json exists (required)
-[ ] Phase 2D completed — utility_analytics.md + .json exists (or skipped with placeholder)
+[ ] Phase 2A completed  -  utility_identifiers.md + .json exists (required)
+[ ] Phase 2B completed  -  utility_localization.md + .json exists (or skipped with placeholder)
+[ ] Phase 2C completed  -  utility_accessibility.md + .json exists (required)
+[ ] Phase 2D completed  -  utility_analytics.md + .json exists (or skipped with placeholder)
 [ ] phase2-finalize.py ran successfully (builds component-utilities.json, registers, writes _index.md)
 [ ] IMPLEMENTATION_HISTORY.md updated with Phase 2 summary (using script output counts)
 ```

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-2a-testing-identifiers.md

@@ -1,9 +1,9 @@
-# PHASE 2A — Testing Identifiers
+# PHASE 2A  -  Testing Identifiers
 
 UI testing identifier integration.
 REF: `reference/testing-identifiers-naming.md`
 
-required — always execute this phase.
+required  -  always execute this phase.
 PARALLEL WITH: Phase 2B, Phase 2C (all read from pass1/_index.md independently)
 NEXT: Phase 2D (depends on this phase's output)
 
@@ -68,7 +68,7 @@ USER_ACTION_REQUIRED: Run Phase 1 first to gather Figma data.
 
 ## CONTEXT-AWARE IDENTIFIERS
 
-Components are reusable — the same `TurkishButton` appears in many screens.
+Components are reusable  -  the same `TurkishButton` appears in many screens.
 Testing identifiers cascade via `UIIdentifierContext` (SwiftUI EnvironmentKey).
 
 ### How It Works
@@ -76,7 +76,7 @@ Testing identifiers cascade via `UIIdentifierContext` (SwiftUI EnvironmentKey).
 Parent views set context using `UITestingIdentifierKey` or raw strings:
 
 ```swift
-// Type-safe (recommended) — uses key's identifier string as segment
+// Type-safe (recommended)  -  uses key's identifier string as segment
 PassengerListView()
     .identifierContext(.PassengerList.screen)
 
@@ -85,7 +85,7 @@ SearchSection()
     .identifierContext("search")
 ```
 
-Child components use standard `.accessibilityIdentifier(.Component.element)` —
+Child components use standard `.accessibilityIdentifier(.Component.element)`  - 
 the context is prepended automatically:
 
 ```
@@ -97,7 +97,7 @@ context = ["passenger_list", "search"]
 ### What Phase 2A Generates
 
 Phase 2A generates **component-level** identifiers only (e.g., `TurkishButton.button`).
-Context prefixes are NOT baked into component identifiers — they come from the
+Context prefixes are NOT baked into component identifiers  -  they come from the
 parent view hierarchy at runtime via `.identifierContext()`.
 
 ### Artifact Guidance
@@ -282,7 +282,7 @@ Write `{artifactPath}/pass2/utility_identifiers.json`:
 }
 ```
 
-This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON — never the markdown.
+This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON  -  never the markdown.
 
 ### Markdown Artifact (human-readable)
 

package/pipeline/skills/figma-ios/figma-to-component/phases/phase-2b-localization.md

@@ -1,4 +1,4 @@
-# PHASE 2B — Localization Keys
+# PHASE 2B  -  Localization Keys
 
 Localization key integration for 8 languages (ar, de, en, es, fr, it, ru, tr).
 REF: `reference/localization-naming.md`
@@ -118,7 +118,7 @@ REF: `reference/localization-naming.md`
 |------|-------|
 | Key format | PascalCase.Dot.Notation |
 | No unnecessary suffix | No `.Label`, `.Text`, `.Title` unless disambiguation needed |
-| Complete text | No runtime concatenation — display-ready strings |
+| Complete text | No runtime concatenation  -  display-ready strings |
 | Unique per pattern | One key per unique text pattern |
 | Shared texts | Single key for identical text across contexts |
 | Max 5 levels | Key hierarchy depth ≤ 5 |
@@ -175,7 +175,7 @@ or
 | Result | Action |
 |--------|--------|
 | `✅ Key exists` + `Missing: 0` | Mark status: "Existing" |
-| `✅ Key exists` + `Missing: N` | Mark status: "Incomplete" — needs missing language translations |
+| `✅ Key exists` + `Missing: N` | Mark status: "Incomplete"  -  needs missing language translations |
 | `❌ Key not found` | Mark status: "To Add" |
 
 FAIL (tool error) →
@@ -196,7 +196,7 @@ USER_ACTION_REQUIRED: Options:
 
 ## GATE 5: ADD_MISSING_KEYS
 
-**CRITICAL: Always use `TranslationManagerTool add` to add keys — NEVER edit localization JSON files directly. The tool writes to BOTH suggested and merged files atomically. Manual edits cause suggested/merged drift.**
+**CRITICAL: Always use `TranslationManagerTool add` to add keys  -  NEVER edit localization JSON files directly. The tool writes to BOTH suggested and merged files atomically. Manual edits cause suggested/merged drift.**
 
 For each key with status "To Add" or "Incomplete":
 
@@ -313,7 +313,7 @@ Write `{artifactPath}/pass2/utility_localization.json`:
 
 If no localization keys needed, write `{ "localizationKeys": [] }`.
 
-This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON — never the markdown.
+This JSON is consumed by `phase2-finalize.py` to build `component-utilities.json`. The orchestrator reads ONLY this JSON  -  never the markdown.
 
 ### Markdown Artifact (human-readable)
 
@@ -368,7 +368,7 @@ Before marking complete, verify:
 [ ] Key format: PascalCase.Dot.Notation
 [ ] No unnecessary suffixes (.Label, .Text unless needed)
 [ ] All 8 language translations provided (ar, de, en, es, fr, it, ru, tr)
-[ ] No runtime concatenation — display-ready strings only
+[ ] No runtime concatenation  -  display-ready strings only
 [ ] One key per unique text pattern
 [ ] TranslationManagerTool check passes for all keys
 [ ] TranslationMetadataGenerator completed