@getrheo/rheo-skill 1.0.0

package/rheo/rheo-flow-import/references/carousel-import.md

@@ -0,0 +1,64 @@
+# Carousel import rules
+
+Use when the source flow has an **in-screen pager** (`infoSteps`, `currentInfoStep`, horizontal `FlatList` / `PagerView`, dot indicators).
+
+## Rheo carousel behavior (swipe-only)
+
+- Users move between slides by **swiping** (horizontal scroll with snap).
+- Optional **`pageControl`** adds dot indicators — not buttons.
+- There is **no** Next / Continue button on the carousel layer in the manifest or at runtime.
+- On the **last slide** (when `loop` is false and there are 2+ slides), swiping to that slide emits a carousel completion so `screen.next` can run.
+- **Single-slide** carousels do not auto-complete; add a `regions.footer` **Continue** (or other) button to advance the flow.
+- **`loop: true`** carousels never auto-complete; pair with a separate screen-level CTA when the flow should move on.
+
+## Manifest shape
+
+- One `kind: "carousel"` in `regions.body` (or inside a body stack).
+- Each page → child **`stack`** in `carousel.slides[]`.
+- `pageControl: { "position": "bottom" }` when source had dot indicators.
+
+## Do not duplicate paging UI
+
+| Source | Import |
+|--------|--------|
+| Pager pages | `carousel.slides[]` |
+| Dot indicators | `pageControl` only |
+| Swipe between pages | Default — no extra buttons |
+| Footer that only increments pager index | **Omit** — not `regions.footer` |
+| Footer / CTA that exits to **next route** | `regions.footer` with `continue` / `go_to_step`, or rely on last-slide swipe completion + `screen.next` |
+
+## Example (swipe + dots)
+
+```json
+{
+  "regions": {
+    "body": {
+      "kind": "stack",
+      "direction": "vertical",
+      "children": [
+        {
+          "kind": "carousel",
+          "slides": [
+            {
+              "kind": "stack",
+              "direction": "vertical",
+              "align": "center",
+              "children": [
+                { "kind": "text", "text": { "default": "Slide 1" }, "style": { "color": "#111111" } }
+              ]
+            }
+          ],
+          "pageControl": { "position": "bottom" }
+        }
+      ]
+    }
+  },
+  "next": { "default": "scr_next" }
+}
+```
+
+## Completion gate
+
+- [ ] No `button` layers for in-pager next/continue.
+- [ ] `screen.next` targets the next **screen** in the flow, not “next slide”.
+- [ ] Single-slide carousel screens include a flow-level CTA if the flow must advance without swiping.

package/rheo/rheo-flow-import/references/flow-spec.md

@@ -0,0 +1,214 @@
+# Flow Spec (recommended authoring path)
+
+A **flow spec** is a compact, agent-authored description of a flow. Running
+`node scripts/scaffold-manifest.mjs <flow-spec.json>` expands it into a
+**schema-valid** Rheo `FlowManifest` skeleton: it generates `scr_*`/`lyr_*` ids,
+wraps label copy into `children`, builds `optionBindings` and `branching` for
+choices, maps button variants to the Rheo enum, and wires `next` edges. You then
+enrich theme/styles and validate.
+
+> The scaffold guarantees **schema validity only**. It does not invent colors,
+> fonts, or publish-gate styling — set `theme` and layer `style` from audit
+> evidence, then run `validate-manifest.mjs` + `audit-publish-manifest.mjs`.
+
+Why use it: the scaffold removes the mistakes that cause `invalid_union` import
+failures (missing `children`, UUID-as-layer-id, missing choice bindings, raw
+source `variant` names). Hand-authoring is allowed but you own every mechanical
+detail yourself.
+
+## Top-level shape
+
+```jsonc
+{
+  "flowId": "00000000-0000-0000-0000-000000000001", // optional placeholder; dashboard replaces it
+  "version": 1,
+  "defaultLocale": "en",
+  "locales": ["en"],
+  "entry": "scr_welcome",            // optional; defaults to the first screen's id
+  "theme": { /* @getrheo/contracts Theme */ },
+  "sdkAttributeKeys": ["sdk.plan"],  // non-reserved keys used by decisions
+  "screens": [ /* ScreenSpec[] — required */ ],
+  "decisions": [ /* @getrheo/contracts DecisionNode[] */ ],
+  "externalSurfaces": [ /* ExternalSurfaceSpec[] */ ]
+}
+```
+
+## Screens
+
+```jsonc
+{
+  "id": "scr_welcome",     // optional; generated from name when omitted
+  "name": "Welcome",
+  "containerStyle": { "backgroundFill": { "kind": "color", "color": "#0EA5E9" } },
+  "header": [ /* LayerIntent[] — back_button / progress chrome */ ],
+  "body":   [ /* LayerIntent[] — required main content */ ],
+  "footer": [ /* LayerIntent[] — sticky CTAs */ ],
+  "next": "scr_goal"       // jump target (scr_*/dec_*/surf_*) or null to end the flow
+}
+```
+
+`next` becomes the screen's `next.default`. Use `null` (or omit and rely on an
+`end_flow` button) for terminal screens.
+
+## Layer intents
+
+Every entry in `header`/`body`/`footer` is a **layer intent** — a friendly shape
+the scaffold expands into a real layer. `id` is always optional. `style` and
+`styleBreakpoints` are passed through verbatim (validated by the layer schema).
+
+### Text, image, icon, media
+
+```jsonc
+{ "kind": "text", "text": "Welcome to Rheo", "style": { "color": "#FFFFFF" } }
+{ "kind": "text", "text": { "default": "Hi", "translations": { "es": "Hola" } } }
+{ "kind": "image", "mediaAssetId": "00000000-0000-0000-0000-000000000101", "alt": "Hero" }
+{ "kind": "icon", "iconName": "sparkles-outline" }            // family defaults to ionicons
+{ "kind": "lottie", "mediaAssetId": "…", "loop": true, "autoPlay": true }
+{ "kind": "video", "mediaAssetId": "…", "autoPlay": false }    // needs a play_media button
+```
+
+Copy fields accept a plain string (becomes `{ default }`) or an explicit
+`{ default, translations }`.
+
+### Buttons, back buttons, links
+
+The convenience fields `label`/`icon`/`labelStyle` are expanded into nested
+`text`/`icon` children — you do not write `children` yourself unless you need
+custom content. `action` defaults to `continue`. Source `variant` names
+(`outline`, `text`, `link`, `default`, `filled`, `danger`) are mapped to the Rheo
+enum automatically.
+
+```jsonc
+{ "kind": "button", "label": "Continue", "action": "continue", "variant": "primary",
+  "labelStyle": { "color": "#FFFFFF" } }
+{ "kind": "button", "label": "Maybe later", "action": "skip", "variant": "ghost" }
+{ "kind": "button", "label": "Go to plan", "action": { "kind": "go_to_step", "screenId": "scr_plan" } }
+{ "kind": "back_button", "icon": "chevron-back-outline", "variant": "ghost" } // header chrome, no action
+{ "kind": "hyperlink", "href": "https://rheo.app/terms", "label": "Terms" }
+```
+
+Action shorthands: `"none"`, `"continue"`, `"skip"`, `"end_flow"`,
+`"go_back_one_screen"`, `"request_app_review"`. Object forms:
+`{ "kind": "go_to_step", "screenId": "scr_x" }`,
+`{ "kind": "request_os_permission", "permissionKey": "…", "outcomes": { "granted": "scr_a", "denied": "scr_b", "blocked": "scr_c" } }`,
+`{ "kind": "play_media", "targetLayerIds": ["lyr_video"] }`.
+
+### Stacks (layout)
+
+```jsonc
+{ "kind": "stack", "direction": "vertical", "align": "center", "gap": 12,
+  "style": { "padding": { "t": 24, "r": 16, "b": 24, "l": 16 } },
+  "children": [ { "kind": "text", "text": "Centered hero copy" } ] }
+```
+
+Card chrome (border/shadow/background/radius) goes on a wrapping stack's `style`.
+
+### Choices
+
+You provide `options`; the scaffold builds the option `stack` children,
+`optionBindings`, and `branching`. `optionId` defaults to a slug of the label.
+Map unselected chrome to `style` and selected chrome to `selectedStyle` per option.
+
+```jsonc
+{
+  "kind": "single_choice",
+  "fieldKey": "gender",
+  "direction": "vertical",
+  "gap": 12,
+  "options": [
+    { "optionId": "male",   "label": "Male",
+      "style": { "border": { "width": 1, "color": "#E5E7EB" }, "radius": 12, "padding": { "t": 16, "r": 16, "b": 16, "l": 16 } },
+      "selectedStyle": { "border": { "width": 1, "color": "#6D5DF6" }, "background": "#6D5DF610" },
+      "labelStyle": { "color": "#0A0A0A" } },
+    { "optionId": "female", "label": "Female", "labelStyle": { "color": "#0A0A0A" } }
+  ]
+}
+```
+
+`multiple_choice` adds optional `minSelections`/`maxSelections`. To branch per
+option, set `branching: { "enabled": true, "conditions": [{ "choiceId": "male", "goTo": "scr_x" }] }`.
+
+### Inputs
+
+```jsonc
+{ "kind": "text_input", "fieldKey": "first_name", "placeholder": "Your name",
+  "inputType": "plain", "required": true, "classification": "safe" }
+{ "kind": "scale_input", "fieldKey": "fitness_level", "min": 1, "max": 5, "step": 1,
+  "minLabel": "Beginner", "maxLabel": "Pro" }
+{ "kind": "checkbox", "fieldKey": "accept_terms", "blocking": true }
+```
+
+Use **at most one** input layer per screen, and add a `continue` button on
+screens with `text_input`, `multiple_choice`, or `scale_input`.
+
+### Auth
+
+```jsonc
+{ "kind": "oauth_login", "providers": [
+  { "type": "preset", "provider": "apple" },
+  { "type": "preset", "provider": "google" },
+  { "type": "custom", "label": "SSO", "iconName": "key-outline", "buttonVariant": "secondary" }
+] }
+{ "kind": "email_password_auth", "fieldKey": "auth", "mode": "sign_up",
+  "submitLabel": "Create account", "minPasswordLength": 8 }
+```
+
+Keep OAuth, email/password, and questionnaire inputs on **separate screens**.
+
+### Carousel (swipe-only onboarding pager)
+
+```jsonc
+{
+  "kind": "carousel",
+  "pageControl": { "position": "bottom" },
+  "slides": [
+    { "align": "center", "gap": 12, "children": [
+      { "kind": "image", "mediaAssetId": "…" },
+      { "kind": "text", "text": "Track your streak", "style": { "color": "#0A0A0A" } }
+    ] },
+    { "align": "center", "gap": 12, "children": [
+      { "kind": "image", "mediaAssetId": "…" },
+      { "kind": "text", "text": "Stay consistent", "style": { "color": "#0A0A0A" } }
+    ] }
+  ]
+}
+```
+
+No buttons inside a carousel — paging is swipe-only ([carousel-import.md](carousel-import.md)).
+
+### Counter / progress / loader
+
+```jsonc
+{ "kind": "progress", "fillColor": "#6D5DF6", "trackColor": "#E5E7EB" }
+{ "kind": "counter", "startValue": 0, "endValue": 1000, "durationMs": 1200 }
+{ "kind": "loader", "variant": "circular", "targetPercent": 100, "onComplete": { "mode": "next" } }
+```
+
+## Decisions and external surfaces
+
+`decisions` accepts full `@getrheo/contracts` `DecisionNode` objects (the scaffold
+passes them through). RevenueCat paywalls use `externalSurfaces`:
+
+```jsonc
+{
+  "id": "surf_paywall",
+  "provider": "revenuecat",
+  "offeringId": "default",
+  "presentation": "paywall",
+  "outcomes": { "purchase_completed": "scr_done", "restore_completed": "scr_done", "dismissed": "scr_offer2" },
+  "fallback": "scr_offer2"   // required
+}
+```
+
+## Run it
+
+```bash
+node scripts/scaffold-manifest.mjs ./rheo-import.flow-spec.json --out ./rheo-import.manifest.json
+node scripts/validate-manifest.mjs ./rheo-import.manifest.json
+node scripts/audit-publish-manifest.mjs ./rheo-import.manifest.json
+```
+
+If scaffold prints `scaffold_status=schema_valid`, the skeleton is structurally
+correct. Then enrich `theme`/`style` from audit evidence and fix any
+publish-gate blockers ([publish-gates.md](publish-gates.md)). A complete worked
+spec lives at [../examples/flow-spec.example.json](../examples/flow-spec.example.json).

package/rheo/rheo-flow-import/references/font-import.md

@@ -0,0 +1,67 @@
+# Custom font import (rheo-import.fonts.json)
+
+Fonts are **not** media assets. Never list `.ttf`, `.otf`, `.woff`, or `.woff2` files in `rheo-import.assets.json`.
+
+## Two files, two jobs
+
+| File | Purpose |
+|------|---------|
+| `rheo-import.assets.json` | Images, Lottie JSON, videos only (`media.mediaAssetId` placeholders) |
+| `rheo-import.fonts.json` | Custom font files for app branding + `manifest.theme.fontFamily` |
+
+Dashboard import **rejects** a font path in `rheo-import.assets.json` when `type` is `image` (or any type that does not match the extension).
+
+## Copy paths
+
+- Put font binaries under `assets/fonts/` in the ZIP (not mixed into image folders).
+- Use a single `assets/` prefix in paths, e.g. `assets/fonts/CalSans-Regular.ttf` — avoid `assets/assets/fonts/...`.
+
+## rheo-import.fonts.json shape
+
+```json
+{
+  "fontFamilies": [
+    {
+      "name": "CalSans",
+      "styles": [
+        {
+          "id": "00000000-0000-0000-0000-000000000501",
+          "weight": 400,
+          "italic": false,
+          "path": "assets/fonts/CalSans-Regular.ttf",
+          "filename": "CalSans-Regular.ttf"
+        }
+      ]
+    }
+  ]
+}
+```
+
+- `name` — family string referenced by `manifest.theme.fontFamily` (e.g. `"CalSans"`).
+- `styles[].path` — ZIP path to the font file (extension must match the binary).
+- `styles[].id` — stable placeholder UUID per style (weight + italic), not used in manifest layers.
+
+Font rows do **not** use `type` or `contentType`. Upload MIME is inferred from the file extension on import.
+
+## Supported font MIME types (upload)
+
+| Extension | MIME used on sign-upload |
+|-----------|--------------------------|
+| `.ttf` | `font/ttf` |
+| `.otf` | `font/otf` |
+| `.woff` | `font/woff` |
+| `.woff2` | `font/woff2` |
+
+## Common agent mistakes (BLOCKING)
+
+1. **Font in `rheo-import.assets.json`** with `"type": "image"` and `image/png` — wrong file and wrong MIME.
+2. **Font in `rheo-import.assets.json`** with `"type": "font"` — still wrong file; use `rheo-import.fonts.json` only.
+3. **Only `manifest.theme.fontFamily`** without bundling font files — family name alone does not load the font.
+4. **Duplicate path prefix** — `assets/assets/fonts/...` from joining paths incorrectly.
+
+## Checklist before zipping
+
+- [ ] Every `.ttf`/`.otf`/`.woff`/`.woff2` appears only in `rheo-import.fonts.json`, not in `rheo-import.assets.json`
+- [ ] `manifest.theme.fontFamily` matches a `fontFamilies[].name`
+- [ ] Each style `path` exists in the ZIP under `assets/fonts/`
+- [ ] No font file uses `media.mediaAssetId` in the manifest

package/rheo/rheo-flow-import/references/import-workflow.md

@@ -0,0 +1,240 @@
+# Import Workflow
+
+Generate a complete Rheo import from an existing app flow. If the source flow uses media, output a ZIP bundle. Raw JSON is acceptable only after an explicit asset audit finds no local media.
+
+## Mandatory Intake Questionnaire (blocking)
+
+Ask these questions **before** running the audit or generating a manifest. Record every answer in chat. Do not skip when the repo structure looks obvious.
+
+1. Which file, route, or coordinator starts the existing flow?
+2. What is the business purpose of this flow in one sentence?
+3. Should the import optimize for **visual fidelity** or **editable structure** in Rheo?
+4. If source code and screenshots disagree, which is more current?
+5. Which steps must stay native/host-owned (signature pad, camera, custom WebView, paywall SDK) vs approximated in Rheo?
+6. Match motion from the codebase (may differ slightly from Rheo presets)? (yes/no)
+7. Does the app use i18n/localization? If yes, which locale is the default/fallback? All `text.default` values must be resolved strings from that locale — never raw keys.
+
+If the user has not named an entry point, stop after question 1 and wait for an answer.
+
+## Steps
+
+1. Fetch the latest Rheo Manifest Agent Profile:
+   - Preferred raw docs URL: `/docs/md/developer-guide/agent-manifest-profile`.
+   - If fetching fails, read [manifest-agent-profile-fallback.md](manifest-agent-profile-fallback.md).
+   - Record the profile version used.
+2. Complete the mandatory intake questionnaire above. Do not proceed without answers.
+3. Run the bundled audit before generating — **from the target app root, not the skill folder**:
+   - `RHEO=/abs/path/to/rheo/rheo-flow-import` then `cd <target-app>`.
+   - `node "$RHEO/scripts/audit-import.mjs" --entry <flow-entry> --out rheo-import.audit.md`
+   - `--entry` is the flow's entry **file** (import graph is traced) or a **directory** (source subtree only). Repeat `--entry` for multiple roots, or comma-separate: `--entry a.tsx,b.tsx`. The audit does **not** scan the whole repo.
+   - Read the printed `audit_root` / `audit_entries` / `audit_scope` / `audit_scanned_files`. If `audit_root` is not the host app (e.g. it points inside the skill), fix `--entry`/`--root` and re-run — do not trust an audit rooted in the skill.
+   - When intake Q6 is **yes**, add `--suggest-animations rheo-import.animations.json`.
+   - Use the audit report as the evidence source for regions, styles, backgrounds, assets, and motion.
+   - If the audit cannot run, explain why and manually produce the same report sections.
+4. Identify the host stack: React Native / Expo, SwiftUI, or best-effort other mobile stack.
+5. Find the flow entry point:
+   - Ask for the file/route/coordinator if the user did not provide it.
+   - React Native examples: Expo Router path, React Navigation screen, `OnboardingScreen`.
+   - SwiftUI examples: `NavigationStack` root, onboarding view, coordinator push.
+6. Trace reachable steps:
+   - Follow imports and navigation calls.
+   - Extract UI strings, button labels, input field keys, paywall calls, auth calls, permission prompts, links, and terminal navigation.
+   - When the audit reports localization ([localization-import.md](localization-import.md)): resolve `t('key')` / `formatMessage` ids from the **default locale** JSON (e.g. `locales/en.json`), not the key itself. Set `manifest.defaultLocale` to that locale.
+   - Detect branches from conditionals, feature flags, platform checks, or stored user state.
+7. Infer screen regions from audit findings:
+   - Look for top bars, safe-area header containers, `Header`, `Toolbar`, back icons, close buttons, and progress indicators.
+   - Put back/close controls and flow progress into `regions.header` when they appear above main content.
+   - Look for sticky CTA containers, `Footer`, bottom safe-area wrappers, and buttons outside scroll/content containers.
+   - Put persistent bottom CTAs into `regions.footer`, not at the bottom of `regions.body`.
+   - Use `regions.body` for scrollable or main content.
+8. Extract style tokens from audit findings:
+   - Inspect theme files, design-token files, Tailwind/NativeWind config, CSS variables, `StyleSheet.create`, shared component variants, and button/text primitives.
+   - Map primary/background/foreground/accent colors into `manifest.theme` when clearly available.
+   - Reuse obvious font sizes, font weights, spacing, border radius, and CTA variants from source components.
+   - Set `style.color` on text layers when screens use dark/saturated backgrounds (`bg-red-600`, `text-white`, etc.).
+   - Prefer the app’s named tokens over arbitrary black-and-white defaults.
+   - Black-and-white fallback is allowed only when the audit finds no color evidence **and** the user confirms there is no theme file.
+9. Map screen backgrounds and gradients:
+   - For `BackgroundGradient`, `LinearGradient`, or `expo-linear-gradient`, set `screen.containerStyle.backgroundFill` to `{ "kind": "color", "color": "<linear-gradient CSS>" }`.
+   - Example: `linear-gradient(180deg, #CCFBF1 0%, #F5F5F4 100%)` for a teal-to-stone shell gradient.
+   - When a screen overrides with a solid brand color (e.g. red education pager), use that hex on the screen and white text.
+   - Do not put gradients only in `manifest.theme.background` — theme background is a flat default, not a per-screen gradient.
+10. Map carousels and in-screen pagers (see [carousel-import.md](carousel-import.md)):
+   - When source uses `infoSteps`, `currentInfoStep`, horizontal `translateX` pagers, or `pagingEnabled` lists, emit `kind: "carousel"`.
+   - Each slide is a vertical `stack` with image, title, and body text from that slide.
+   - Add `pageControl: { "position": "bottom" }` when dot indicators exist (dots only).
+   - Carousels are **swipe-only** — no Next/Continue button on the carousel layer. Do not add footer/body buttons for in-pager paging.
+   - Use `regions.footer` only when the source CTA advances the **next screen in the flow**, or for single-slide carousels that need an explicit Continue.
+   - Bundle every slide image; every asset referenced in the carousel must appear in `rheo-import.assets.json`.
+   - Do not collapse multi-slide routes into one static screen with a single image.
+11. Map layout, alignment, borders, and shadows:
+   - Parent vertical stacks that center content need `align: "center"` (and `justify: "center"` when appropriate).
+   - Hero images belong inside centered stacks, not as lone siblings in an unaligned vertical stack.
+   - Card rows (rating, testimonials, why-it-works cards) use wrapping stacks with `style.background`, `style.radius`, `style.padding`, `style.border`, and `style.shadow` from source.
+12. Map custom fonts from audit findings ([font-import.md](font-import.md)):
+   - Detect `Font.loadAsync`, `useFonts`, Tailwind `fontFamily`, and `font-*` classes tied to loaded families.
+   - Copy every `.ttf`, `.otf`, `.woff`, and `.woff2` file into `assets/fonts/` in the ZIP (path like `assets/fonts/CalSans-Regular.ttf`).
+   - Write `rheo-import.fonts.json` with stable placeholder UUIDs per font style (weight + italic).
+   - Set `manifest.theme.fontFamily` to the primary family name used in source (e.g. `CalSans`).
+   - **Do not** add font files to `rheo-import.assets.json` — not as `type: "image"`, not as `type: "font"`. Fonts are not `media.mediaAssetId` assets.
+   - Dashboard import uploads fonts and merges them into app branding; the manifest only references the family name string.
+13. Map choice option default and selected states:
+   - For `single_choice` and `multiple_choice`, each selectable option is a child `stack` layer.
+   - Map unselected Tailwind/classes to `style` on that stack (border, background, padding, radius).
+   - Map selected classes to `selectedStyle` on the same stack — the renderer merges selected over default.
+   - When label text color changes on selection, set default `style.color` on the nested text layer and selected color via `selectedStyle` on the stack or nested text as appropriate.
+   - Audit flags `selected === … ? … : …` ternaries — do not ship choice screens with only default styling.
+14. Extract assets from audit findings:
+   - Follow static imports, `require(...)`, image maps, Lottie JSON imports, video imports, and asset constants used by traced screens.
+   - Inspect shared components and design primitives too; hero illustrations and logos are often hidden behind `Illustration`, `Logo`, `Avatar`, `Mascot`, or `ImageBackground` components.
+   - Inspect platform asset catalogs and config references where relevant, for example Expo `assets/`, React Native image folders, Swift asset catalogs, and bundled Lottie/video directories.
+   - Copy referenced local assets into an `assets/` folder in the output bundle.
+   - For each asset, generate a stable placeholder UUID and use that UUID as `media.mediaAssetId` in the manifest.
+   - Write `rheo-import.assets.json` mapping placeholder UUIDs to bundled file paths.
+   - If a referenced asset cannot be copied, stop and report the missing asset instead of silently dropping the media layer.
+15. Ask targeted follow-up questions for audit ambiguity:
+   - Ask only when ambiguity changes the manifest materially.
+   - Continue with low-confidence review notes when not blocked.
+   - Examples: shared header vs per-step header, exact gradient mapping, light/dark asset choice, conflicting button token sources.
+16. Use screenshots/recordings if supplied:
+   - Use them for visual hierarchy, copy confirmation, colors, media placement, and step order.
+   - Do not override clear source behavior unless the user says the visual artifact is newer.
+17. Build a private flow model:
+   - ordered screens
+   - branches
+   - inputs
+   - external surfaces
+   - terminal outcomes
+   - unmappable native behavior
+18. Generate `rheo-import.manifest.json`:
+   - Emit a complete graph with explicit `next.default` edges.
+   - Use decision nodes for clear branches.
+   - Use RevenueCat external surfaces for detected RevenueCat paywalls.
+   - Prefer fidelity when the user chose visual fidelity: carousels, gradients, shadows, and centered stacks.
+   - **Layer ids:** `scr_*` / `lyr_*` only on screens and layers; UUID placeholders **only** for `media.mediaAssetId` and font sidecars ([layer-schema-pitfalls.md](layer-schema-pitfalls.md#layer-ids-vs-media-placeholder-uuids)).
+   - **Container layers:** every `button`, `back_button`, `hyperlink`, `stack`, choice input, and auth layer must include its `children` (or `slides`) array ([manifest-rules.md](manifest-rules.md#container-layers-required-children)).
+   - **Header back buttons:** `kind: "back_button"`, Rheo `variant` enum only (map source `outline`/`text`/`link`), nested `icon`/`text` children, **no `action`**, `icon.family: "ionicons"` ([layer-schema-pitfalls.md](layer-schema-pitfalls.md#back_button-header-chrome)).
+   - **Choice screens:** every `single_choice` / `multiple_choice` includes `fieldKey`, `children` (≥2 option stacks), `optionBindings`, and `branching` — never `"options"` arrays ([layer-schema-pitfalls.md](layer-schema-pitfalls.md#single_choice--multiple_choice)).
+   - When intake Q6 is **yes** and the workspace plan includes animations, apply motion from [animation-import.md](animation-import.md) (audit presets, stagger, conservative `restingMotion`). Omit motion when Q6 is **no** or plan lacks animations.
+19. Validate and publish gate audit:
+   - Run `node "$RHEO/scripts/validate-manifest.mjs" ./rheo-import.manifest.json` (schema + dashboard publish rules).
+   - Run `node "$RHEO/scripts/audit-publish-manifest.mjs" ./rheo-import.manifest.json` and read `rheo-import.publish-gates.md`.
+   - Fix every **blocking** issue (especially missing `style.color` on text and button labels, missing Continue on input screens, entry/completion path).
+   - See [publish-gates.md](publish-gates.md) for the full checklist mirrored from the builder **Publish** button.
+   - If safe normalization is needed, run `node "$RHEO/scripts/normalize-manifest.mjs" ./rheo-import.manifest.json`, then re-run validate + publish audit.
+20. Bundle:
+   - If there are no assets or fonts, provide `rheo-import.manifest.json` and explicitly state `no local assets found`.
+   - If there are assets or fonts, create `rheo-import.zip` containing `rheo-import.manifest.json`, optional `rheo-import.assets.json`, optional `rheo-import.fonts.json`, and files under `assets/`.
+   - Do not finish with JSON-only output when any traced screen references local image, Lottie, video, or font files.
+
+## Output
+
+Primary artifact:
+
+- No assets after explicit audit: `rheo-import.manifest.json`.
+- With assets: `rheo-import.zip`.
+
+`rheo-import.assets.json` — **images, Lottie, and video only** (never fonts):
+
+```json
+{
+  "assets": [
+    {
+      "id": "00000000-0000-0000-0000-000000000101",
+      "path": "assets/hero.png",
+      "type": "image",
+      "contentType": "image/png",
+      "name": "hero.png"
+    }
+  ]
+}
+```
+
+**Supported `rheo-import.assets.json` MIME types (dashboard import rejects others):**
+
+| `type` | `contentType` values | Extensions |
+|--------|----------------------|------------|
+| `image` | `image/png`, `image/jpeg`, `image/webp`, `image/gif`, `image/svg+xml` | `.png`, `.jpg`, `.jpeg`, `.webp`, `.gif`, `.svg` |
+| `lottie` | `application/json` | `.json` |
+| `video` | `video/mp4`, `video/webm`, `video/quicktime` | `.mp4`, `.webm`, `.mov` |
+
+Do **not** put `.ttf`, `.otf`, `.woff`, or `.woff2` in this file — use `rheo-import.fonts.json` ([font-import.md](font-import.md)). Do **not** bundle HEIC or AVIF as images. Match `type` and `contentType` to the file extension (do not label a `.json` Lottie as `type: "image"`).
+
+`rheo-import.fonts.json` — **custom fonts only** (separate from assets.json):
+
+```json
+{
+  "fontFamilies": [
+    {
+      "name": "CalSans",
+      "styles": [
+        {
+          "id": "00000000-0000-0000-0000-000000000501",
+          "weight": 400,
+          "italic": false,
+          "path": "assets/fonts/CalSans-Regular.ttf",
+          "filename": "CalSans-Regular.ttf"
+        }
+      ]
+    }
+  ]
+}
+```
+
+Choice option stack example (each option child of `single_choice` / `multiple_choice`):
+
+```json
+{
+  "id": "lyr_goal_a",
+  "kind": "stack",
+  "style": {
+    "border": { "width": 1, "color": "#E5E7EB" },
+    "background": "#F9FAFB",
+    "radius": 12,
+    "padding": 16
+  },
+  "selectedStyle": {
+    "border": { "width": 1, "color": "#6D5DF6" },
+    "background": "#6D5DF610"
+  },
+  "children": [
+    {
+      "id": "lyr_goal_a_text",
+      "kind": "text",
+      "text": { "default": "Option A" },
+      "style": { "color": "#0A0A0A" }
+    }
+  ]
+}
+```
+
+Wrap option stacks in a full choice layer — see [layer-schema-pitfalls.md](layer-schema-pitfalls.md#single_choice--multiple_choice) for the required `fieldKey`, `optionBindings`, and `branching` wrapper.
+
+Mention review notes in chat, not inside the manifest, unless Rheo contracts support the metadata.
+
+## Completion Gate
+
+Before final response, answer these for yourself:
+
+- Did I complete the mandatory intake questionnaire and record answers in chat?
+- Did I run audit with `--entry` and use carousel/style/background/layout/font/choice findings?
+- Did I bundle custom fonts in `rheo-import.fonts.json` only (no `.ttf`/`.otf`/`.woff` rows in `rheo-import.assets.json`) and set `manifest.theme.fontFamily`?
+- If the app uses i18n, did every `text.default` use resolved default-locale copy (not translation keys)?
+- Did every choice option stack include both `style` and `selectedStyle` when the audit flagged selected ternaries?
+- Did I emit `carousel` layers for every multi-slide route the audit flagged without duplicating pager buttons in `regions.footer`?
+- Did I apply gradients to `screen.containerStyle.backgroundFill` and set text colors on colored screens?
+- Did I center images and map card borders/shadows to wrapping stacks?
+- Did I inspect source asset references from every traced screen and shared visual component?
+- Did I either create `rheo-import.zip` or explicitly confirm no local assets were found?
+- Does every `media.mediaAssetId` refer to a placeholder UUID listed in `rheo-import.assets.json` when assets exist?
+- Does the ZIP include every file listed in `rheo-import.assets.json`?
+- Did publish gate audit pass with zero blocking issues?
+- Did every `back_button`, `button`, and `hyperlink` layer include a `children` array with nested label content (not omitted)?
+- Did every layer use `lyr_*` ids (no asset UUIDs as layer ids)?
+- Did every `back_button` use a Rheo `variant` enum value and omit `action`?
+- Did every `single_choice` / `multiple_choice` include `fieldKey`, `optionBindings`, and `branching`?
+- Did `node "$RHEO/scripts/validate-manifest.mjs"` exit 0 before zipping?
+
+If any answer is no, the import is not complete.
+
+Also verify that high-confidence audit findings were either used in the manifest/ZIP or explicitly explained in review notes.