@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.1

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

@@ -1,120 +0,0 @@
----
-name: figma-component-test
-description: Generate Compose Testing + Paparazzi/Roborazzi snapshot + unit tests for a Jetpack Compose component. Android peer to pipeline/skills/figma-ios/figma-component-test.
-user-invocable: true
-argument-hint: <component-name>
-allowed-tools: Read, Write, Edit, Glob, Grep, Bash
-status: wip-v5
-sourced-from: derived-from/figma-ios/figma-component-test
-platform: android
----
-
-# figma-component-test  -  Compose Test Suite
-
-> **WS-7 v5.0.0**  -  Subphase 3.5 for Android. Three-layer test strategy mirroring the iOS peer (ViewInspector → Compose Testing, Snapshot → Paparazzi/Roborazzi, Unit → JUnit).
-
-## Three-layer strategy (Android)
-
-| Layer | Tool | What it verifies |
-|---|---|---|
-| **Structural** | Compose Testing (`createComposeRule()`) | Semantic tree, node existence, applied modifiers, click + input actions |
-| **Visual** | Paparazzi (JVM) or Roborazzi | Pixel-accurate render: light/dark, LTR/RTL, multi-density, multi-fontScale |
-| **Behavioural** | JUnit + Turbine | State changes, callback invocation, configuration copy semantics |
-
-The orchestrator picks Paparazzi by default (JVM-side, fast). Override by setting `figmaConfig.build.snapshotEngine = "roborazzi"` when the project already wires Robolectric.
-
-## Generated files
-
-### 1. `{Name}ComposeTest.kt` (structural)
-
-```kotlin
-class ButtonPrimaryComposeTest {
-    @get:Rule val composeRule = createComposeRule()
-
-    @Test
-    fun default_config_renders_title_and_is_clickable() {
-        var clicked = false
-        composeRule.setContent {
-            AppTheme {
-                ButtonPrimary(
-                    ButtonPrimaryConfiguration()
-                        .title("Save")
-                        .onClick { clicked = true }
-                )
-            }
-        }
-
-        composeRule.onNodeWithText("Save")
-            .assertIsDisplayed()
-            .assertHasClickAction()
-            .performClick()
-
-        assertThat(clicked).isTrue()
-    }
-
-    @Test
-    fun disabled_state_is_not_clickable() {
-        // ... covers isEnabled=false path
-    }
-}
-```
-
-Rules:
-- Prefer `onNodeWithTag(TestingIdentifiers.buttonPrimary)` over `onNodeWithText` when the text is localised.
-- Every interactive state (enabled, disabled, loading) gets a test.
-- No `Thread.sleep`  -  use `composeRule.waitUntil { ... }` or `runTest` for coroutine flows.
-
-### 2. `{Name}SnapshotTest.kt` (visual)
-
-Paparazzi variant:
-
-```kotlin
-class ButtonPrimarySnapshotTest {
-    @get:Rule val paparazzi = Paparazzi(
-        deviceConfig = DeviceConfig.PIXEL_6,
-        theme = "AppTheme",
-        renderingMode = SessionParams.RenderingMode.SHRINK
-    )
-
-    @Test fun primary_light()     { paparazzi.snapshot { variant(ButtonStyle.Primary, dark = false) } }
-    @Test fun primary_dark()      { paparazzi.snapshot { variant(ButtonStyle.Primary, dark = true)  } }
-    @Test fun secondary_rtl()     { paparazzi.snapshot { variant(ButtonStyle.Secondary, rtl = true) } }
-    @Test fun fontScale_large()   { paparazzi.snapshot { variant(ButtonStyle.Primary, fontScale = 1.5f) } }
-}
-```
-
-Minimum matrix: primary × (light, dark) × (LTR, RTL) × (default, large fontScale) = 8 snapshots per component. `--dev` elides fontScale row.
-
-### 3. `{Name}ConfigurationTest.kt` (unit)
-
-```kotlin
-class ButtonPrimaryConfigurationTest {
-    @Test fun copy_preserves_unchanged_fields() {
-        val base = ButtonPrimaryConfiguration().title("A").style(ButtonStyle.Primary)
-        val changed = base.title("B")
-        assertThat(changed.title).isEqualTo("B")
-        assertThat(changed.style).isEqualTo(base.style)
-    }
-}
-```
-
-Covers: fluent modifier semantics, default values, enum exhaustiveness.
-
-## Build + run
-
-```bash
-# JVM side (Paparazzi + Configuration unit tests)
-./gradlew :${module}:testDebugUnitTest --console=plain
-
-# Instrumented side (Compose Testing)
-./gradlew :${module}:connectedDebugAndroidTest --console=plain
-
-# Paparazzi record (only when snapshots are intentionally updated)
-./gradlew :${module}:recordPaparazziDebug
-```
-
-On failure  -  up to 3 auto-fix cycles, then halt.
-
-## Cross-CLI parity
-
-Both CLIs emit identical progress lines, generate the same 3-file set (compose + snapshot + configuration), and honour `figmaConfig.build.snapshotEngine`. `smoke-figma-android-parity.sh` asserts the inventory match with the iOS peer.

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

@@ -1,35 +0,0 @@
----
-name: figma-component-wiki
-description: Component wiki generation for Android. Dispatches to the same 4-mode adapter set as the iOS peer (submodule / in-repo / github-wiki / separate-repo). Body rendering reads the Kotlin composable + sibling README.md instead of Swift + FIGMA.md.
-user-invocable: true
-argument-hint: <figma-url> | <component-name>
-allowed-tools: Read, Write, Glob, Grep, Bash
-status: wip-v5
-sourced-from: derived-from/figma-ios/figma-component-wiki
-platform: android
----
-
-# figma-component-wiki  -  Component Wiki (Android)
-
-> **WS-7 v5.0.0**  -  Android peer to `pipeline/skills/figma-ios/figma-component-wiki`. Identical dispatch contract (Phase 7 Report Step 2 → `{componentName, componentPath, figmaConfig, agentState}` → `{writtenPaths[], committedSha?, pushedRemote?}`). Identical 4-adapter matrix (submodule / in-repo / github-wiki / separate-repo). Only the markdown rendering differs: reads Kotlin composable signature + sibling `README.md` rather than SwiftUI `+Modifiers.swift` + `FIGMA.md`.
-
-See `pipeline/skills/figma-ios/figma-component-wiki/SKILL.md` for the full adapter table and dispatch contract  -  shared verbatim.
-
-## Android-specific rendering notes
-
-- Parameter table reads the Composable signature AND the Configuration data class:
-  ```kotlin
-  @Composable fun ButtonPrimary(configuration: ButtonPrimaryConfiguration, modifier: Modifier = Modifier)
-  ```
-  Yields: `configuration: ButtonPrimaryConfiguration`, `modifier: Modifier`. Nested Configuration properties are rendered as a second table (one row per knob).
-- Code examples quote `@Preview` bodies rather than SwiftUI `#Preview` bodies.
-- Design tokens section reads `MaterialTheme.colorScheme.*` + `MaterialTheme.typography.*` references grepped from the composable.
-- Accessibility notes read `.semantics { ... }` blocks instead of `.accessibility*` modifiers.
-
-## Python helpers
-
-Shared with the iOS peer  -  same `pipeline/scripts/wiki/sidebar-generator.py` and `pipeline/scripts/wiki/status-page.py` land in WS-5b. The helpers are platform-agnostic (they read component markdown files, not Swift or Kotlin sources).
-
-## Cross-CLI parity
-
-Byte-identical progress lines, identical adapter dispatch, identical return schema. Wiki layout convergence across iOS and Android is an explicit goal  -  the same `/components/{Category}/{Name}.md` path structure on every project regardless of platform.

package/pipeline/skills/figma-android/figma-to-component/SKILL.md

@@ -1,124 +0,0 @@
----
-name: figma-to-component
-description: Figma-to-Compose component implementation workflow for Android. Takes a Figma URL and produces a production-ready Jetpack Compose component through the same 8-phase pipeline shape as the iOS peer  -  data gathering, analysis, code generation, testing, Code Connect, documentation.
-user-invocable: true
-argument-hint: <figma-url> | phase-<N> | status
-allowed-tools: Task, Read, Glob, Grep, Bash, Write, Edit, AskUserQuestion
-status: wip-v5
-sourced-from: derived-from/figma-ios/figma-to-component
-platform: android
----
-
-# figma-to-component  -  Android Orchestrator
-
-> **WS-7 v5.0.0**  -  Platform peer to `pipeline/skills/figma-ios/figma-to-component`. Same 8-phase shape; platform-specific phases (3-Token Mapping, 4-Code Gen, 5-Tests, 6-Code Connect) target Kotlin / Jetpack Compose / Paparazzi / Code Connect for Compose. Common phases (0-Init, 1-Gather, 2A-2D utilities, 7-Wiki, 8-Cleanup) share logic with the iOS peer  -  implementations stay in this skill for now; a `figma-common/` refactor lands in WS-7b.
-
-## Dispatch entry
-
-Called from multi-agent Phase 3 when `state.taskType === "component"` AND `figmaConfig.project.platform === "android"`. See `pipeline/commands/multi-agent/refs/component-dispatch.md` for the full dispatch contract shared with the iOS peer (same input/output schema, subphase state shape).
-
-## Parameters
-
-| Parameter | Required | Description |
-|-----------|----------|-------------|
-| Figma URL | Yes | `https://www.figma.com/design/{fileKey}/...?node-id={nodeId}` |
-| `phase-<N>` | No | Resume a specific subphase instead of running the full chain |
-| `status` | No | Print subphase progress from `state.phases["3"].subphases[]` and exit |
-
-```
-/figma-to-component https://www.figma.com/design/abc/?node-id=123-456
-/figma-to-component phase-4a   # resume at Kotlin Configuration generation
-/figma-to-component status
-```
-
-## Phase order (Android-flavoured)
-
-| # | Phase | Platform-specific? | Notes |
-|---|---|---|---|
-| 3.0 | Init | no | Node-id parse, registry lookup, worktree confirm |
-| 3.1 | Gather | no | Figma API/MCP fetch, design tokens, properties |
-| 3.2a | Testing identifiers | no | Platform-agnostic semantic IDs (shared with iOS) |
-| 3.2b | Localization | no | Shared strings  -  lands in `{repos.common}` |
-| 3.2c | Accessibility | partial | `contentDescription` / `Role` / `semantics {}` vs SwiftUI's `.accessibility*`  -  the generator knows both |
-| 3.2d | Analytics | no | Shared analytics keys |
-| 3.3 | Token Mapping | **yes** | Maps Figma tokens → MaterialTheme dimensions / colorScheme / typography; outputs a per-project `DesignTokens.kt` if missing |
-| 3.4a | Configuration | **yes** | `{Name}Configuration.kt`  -  data class with all properties, marked `@Immutable`/`@Stable` for Compose skippability |
-| 3.4b | View | **yes** | `{Name}Screen.kt` or `{Name}.kt`  -  `@Composable fun {Name}(configuration: {Name}Configuration, modifier: Modifier = Modifier)` |
-| 3.4c | Docs | no | `README.md` next to the composable |
-| 3.4d | Preview | **yes** | `@Preview` functions covering variants (device, darkMode, RTL, fontScale) |
-| 3.4e | Modifiers | **yes** | Kotlin extension functions on `Modifier` or on the Configuration type  -  the fluent API the iOS peer expresses as `+Modifiers.swift` |
-| 3.5a | Structural tests | **yes** | `createComposeRule()` + semantic matchers (`onNodeWithText`, `onNodeWithTag`, `onNodeWithContentDescription`) |
-| 3.5b | Snapshot | **yes** | Paparazzi or Roborazzi snapshot tests covering light/dark, LTR/RTL, Dynamic Font Scale |
-| 3.5c | Unit | yes (opt) | Logic-only unit tests; `--dev` may elide |
-| 3.6 | Code Connect | **yes** | Code Connect for Compose  -  `{Name}.figma.kt` with `@FigmaConnect` variant mappings |
-| 3.7 | Wiki | no | Delegates to `figma-component-wiki`  -  same 4-mode adapter as iOS |
-| 3.8 | Cleanup | no | Artifact pruning, state finalize |
-
-## Delegation graph
-
-```
-figma-to-component (this skill)
-├─ phase 3.4 (code gen)     → figma-component-implement  (Android peer)
-├─ phase 3.5 (tests)        → figma-component-test        (Android peer)
-├─ phase 3.6 (code connect) → figma-component-code-connect (Android peer)
-└─ phase 3.7 (wiki)         → figma-component-wiki        (Android peer  -  mode-aware adapter)
-```
-
-The platform-agnostic subphases (3.0-3.3, 3.2a-d, 3.8) use the same logic as the iOS orchestrator  -  they read `figmaConfig` + Figma API results and write registry entries that don't care about language target. WS-7b extracts those to `pipeline/skills/figma-common/` so both platforms import rather than duplicate.
-
-## Build target resolution
-
-Reads from `figmaConfig.build`:
-
-```json
-{
-  "gradleModule": ":components:button",
-  "variant": "debug",
-  "buildType": "release"
-}
-```
-
-Invokes build via:
-
-```bash
-./gradlew :${build.gradleModule//:/}:assembleDebug
-./gradlew :${build.gradleModule//:/}:testDebugUnitTest
-```
-
-If `build.gradleModule` is missing, halt with a clear "configure `figmaConfig.build.gradleModule` for Android" message. Do not guess.
-
-## Component output locations
-
-Default layout  -  override per project via `figmaConfig.repos` and `figmaConfig.artifactBasePath`:
-
-| Artifact | Path |
-|---|---|
-| Composable + Configuration | `{repos.components.path}/src/main/java/.../components/{Category}/{Name}/{Name}.kt` |
-| Modifiers extensions | Same directory as the composable |
-| Unit tests | `{repos.components.path}/src/test/java/.../components/{Category}/{Name}Test.kt` |
-| Instrumented/Compose tests | `{repos.components.path}/src/androidTest/java/.../components/{Category}/{Name}ComposeTest.kt` |
-| Snapshot tests | Beside Compose tests, using Paparazzi's `@get:Rule val paparazzi = Paparazzi(...)` |
-| Code Connect | `{repos.components.path}/src/main/java/.../components/{Category}/{Name}/{Name}.figma.kt` |
-| Component artifacts | `{artifactBasePath}/{Category}/{Name}/` (screenshots, specs  -  platform-agnostic) |
-
-## Design token conventions
-
-Tokens for Compose land in `MaterialTheme`:
-
-- Spacing → `CustomSpacing` extension on `MaterialTheme` (or vanilla `dp` constants if the project has no theme wrapper)
-- Color → `MaterialTheme.colorScheme.{name}` or project's `CustomColorScheme`
-- Typography → `MaterialTheme.typography.{name}`
-- Radius → `CustomShapes` extension
-
-The generator reads `figmaConfig.tokens.*Path` to locate the theme file and resolves symbolic tokens (e.g. `Spacing.spacing16`) in the same way the iOS peer resolves `.Spacing.spacing16`. No magic numbers land in the composable.
-
-## Cross-CLI parity
-
-Claude Code and Copilot CLI implementations MUST:
-
-- Accept identical arguments (`<figma-url>`, `phase-<N>`, `status`).
-- Emit byte-identical progress lines via the WS-11 contract.
-- Write the same `state.phases["3"].subphases[]` schema so multi-agent's phase-tracker renders identically.
-- Resolve `figmaConfig.build.gradleModule` the same way.
-
-`smoke-figma-android-parity.sh` asserts the platform-specific skill inventory matches the iOS peer (same skill names exist on both sides).

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

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

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

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