Stepper - Dash sits above multi-step flows to tell the user where they are — KYC wizards, onboarding carousels, checkout funnels. The dashed format reads as "position in a sequence" rather than "percent done".

• Total step count encoded as 10 boolean props instead of an integer. Ships prop1Stepper…prop10Steppers — ten toggles used as visibility flags for "how many dashes to render". To spec a 4-dash stepper a consumer flips four toggles on and six off; to change to 5 dashes they flip one more. Should be a single total: Int (or total: 2 | 3 | … | 10 enum). C2 · Variant & Property Naming
• highlighted is ordinal, not numeric. highlighted = 1st | 2nd | … | 10th reads as a label, not a position. Native APIs and product code want an integer they can feed a current / total calculation — rename to current and switch to a numeric range. C2 · Variant & Property Naming
• Duplicate 6th layer name across positions 7–10. In the highlighted=1st variant, dash layers are labelled 1st, 2nd, 3rd, 4th, 5th, 6th, 6th, 6th, 6th, 6th. Looks like a copy-paste oversight when the component was extended from 6 to 10 slots. Rename to 7th…10th. C1 · Layer Structure & Naming
• No native primitive matches. Neither SwiftUI nor Material 3 ships a "segmented dash" progress indicator. Implementation is a custom HStack/Row of rounded rectangles — manageable, but the DS must own the composable and its theming. C4 · Native Mappability
• No completed, error, or interactive state modeled. Only the default two-tone (brand / track) rendering exists. Add variants for completed-successfully (green), error-at-step-N (red), and optionally pressed/focused if steps are tappable. C5 · Interaction State Coverage
• Code Connect mappings not registered. Blocked until the ordinal enum and boolean visibility props collapse into current and total. Mapping today's schema would codify the anti-pattern. C7 · Code Connect Linkability

• Replace the 10 propNStepper booleans with a single total property. Today a designer builds "4-dash stepper" by toggling prop1Stepper=true, prop2=true, prop3=true, prop4=true, prop5..10=false. Replace with total: 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10. Variant math drops from (10 ordinal × 2^10 boolean combos, nominally) to 9 × 10 = 90, and more importantly the schema becomes legible — "4 dashes, step 2 active" instead of "highlighted=2nd + 4 booleans on, 6 booleans off". Property
• Rename highlighted = 1st…10th to current: 1…10. The property name reads as a Boolean ("is highlighted?") and the values read as rank labels. Both are wrong — the value is a numeric index. Rename to current and switch values from ordinal strings to integers so consumers can do current / total math. Rename
• Fix duplicated 6th layer names on slots 7–10. Rename the last four inner dash layers to 7th, 8th, 9th, 10th so the inspector and dev handoff read cleanly. Low-effort cleanup. Rename
• Add status states for completed, error, and loading. Introduce an optional component-level state: default | success | error that repaints the whole row (green when the flow finishes, red when the current step errors). Indeterminate / loading is optional — a subtle pulsing animation on the current dash while an async step resolves. Tokens: main/stepper/color/bg-positive, main/stepper/color/bg-negative. State
• Unify Stepper - Dash, Stepper - Bullet, and Stepper - Circular into one EBStepper API. All three render the same underlying data (current, total) and differ only in the visual treatment of each slot. On the native side, ship one EBStepper(current:total:style:) with style: .dash | .bullet | .circular instead of three separate components — the state, accessibility, and layout logic are identical across styles. Figma can keep three sibling records for the sticker sheet, but the API is one surface. Family
• Document a canonical "dash height × total" sizing chart. The single frame is 268 px wide with 4-px dash height and 4-px gap. As total grows the individual dash width shrinks — at total=10 each dash is ~22 px. Document the minimum sensible per-dash width and the component's fill behavior inside narrower parents. Docs
• Announce "Step X of Y" to screen readers. Dashes are purely decorative — assistive tech sees nothing today. Wrap in a container with accessibilityLabel = "Step \(current) of \(total)" on iOS and Modifier.semantics { contentDescription = … } on Android. A11y
• Spec a vertical orientation for long flows. With 10 dashes in a narrow column, individual dashes get uncomfortably short. Add orientation: horizontal | vertical so flows can stack top-to-bottom when horizontal width is constrained. Property