create-disposabl-app 0.0.4 → 0.1.1

package/dist/templates/default/apps/mobile/.agents/skills/expo-examples/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: expo-examples
+description: Expo's official example projects - the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched pattern to adapt, or when scaffolding a new project from one with `npx create-expo --example`.
+allowed-tools: "Read,Bash(gh api:*),Bash(git clone:*),Bash(npx create-expo:*),Bash(npx degit:*),Bash(bun create:*)"
+version: 1.0.0
+license: MIT
+---
+
+# Expo Examples
+
+[expo/examples](https://github.com/expo/examples) is Expo's official library of ~70 **integration examples** — directories named `with-<library>` (e.g. `with-stripe`, `with-maps`), each built around **one** library or service. These are not full apps: they're **managed** projects (no `ios/`/`android/` dirs — native setup is via config plugins), and the typical one is a **single screen of ~100–200 lines**. Mine them for the canonical integration *pattern* — the dependency set, `app.json` config plugins, and minimal wiring Expo maintains against the current SDK — and adapt that into the user's app. Don't expect to lift an application architecture from them.
+
+Reach for an example before hand-rolling an integration. (Kinds — full-stack, showcases, starters — are noted in `./references/catalog.md`.)
+
+## Two modes
+
+1. **Inspiration / adapt** (most common) — the user already has a project. Find the matching example, read its key files, and apply the *pattern* to their code.
+2. **Scaffold** — greenfield. Start a fresh project directly from the example.
+
+## Workflow
+
+### 1. Find the right example
+
+Map the user's need to an example name (e.g. payments → `with-stripe`, auth → `with-clerk`). `./references/catalog.md` is a categorized snapshot for fast triage — but it drifts, so confirm against the live list:
+
+```bash
+# Live example names:
+gh api repos/expo/examples/contents --jq '.[] | select(.type=="dir" and (.name|startswith(".")|not)) | .name'
+# Aliases (renamed) + deprecated (dead/moved) examples — check before recommending:
+gh api repos/expo/examples/contents/meta.json --jq '.content' | base64 -d
+```
+
+`meta.json` is the source of truth for what's renamed or dead (deprecated examples are removed from the repo tree but still listed here, each with a `message`). If an example is in its `deprecated` map, don't recommend it — follow the `message` to the modern path. If it's in `aliases`, use the `destination`.
+
+### 2a. Inspiration mode — study without touching the user's project
+
+The common case: the user already has an app and wants to see how Expo does something. Read the example as **reference** and apply the patterns by hand — never scaffold an example on top of their project.
+
+**First, list the whole example in one call.** Integration code is often nested (e.g. Stripe's server routes live in `app/api/`), so a one-level listing misses the important files:
+
+```bash
+gh api 'repos/expo/examples/git/trees/master?recursive=1' \
+  --jq '.tree[].path | select(startswith("with-stripe/"))'
+```
+
+**Then read the high-signal files first:** `README.md` (setup) → `package.json` (deps) → `app.json` (config plugins / permissions) → the integration code the manifest revealed → `.env` (required secrets). Per file:
+
+```bash
+gh api repos/expo/examples/contents/with-stripe/utils/stripe-server.ts --jq '.content' | base64 -d
+# No gh? Raw URL (branch is master):
+curl -s https://raw.githubusercontent.com/expo/examples/master/with-stripe/utils/stripe-server.ts
+```
+
+**Reading more than a couple of files?** Many integrations are spread across server routes, a client provider, and config (Stripe is). Skip the per-file calls — pull the whole example into a **throwaway/gitignored dir (not the user's project)** and read it freely with Grep/Read, then apply by hand:
+
+```bash
+npx degit expo/examples/with-stripe /tmp/expo-ref/with-stripe   # clean copy, no git history
+# fallback without degit (sparse-checkout, no full ~64 MB clone):
+git clone --depth 1 --filter=blob:none --sparse https://github.com/expo/examples.git /tmp/expo-ref/examples \
+  && (cd /tmp/expo-ref/examples && git sparse-checkout set with-stripe)
+```
+
+Read from there with Grep/Read; delete the scratch dir when done.
+
+### 2b. Scaffold mode — new project from an example
+
+```bash
+npx create-expo --example with-stripe   # short form:  npx create-expo -e with-stripe
+bun create expo --example with-stripe    # with bun
+```
+
+### 3. Adapt into the user's app — non-destructively (critical)
+
+When the user already has an app, **add only what the example introduces; never overwrite their setup.**
+
+- **Version-align — don't copy pinned versions.** Examples track the **latest** SDK, so their `package.json` pins won't match an older project. Add only the *missing* deps with `npx expo install <pkg>` (it resolves SDK-correct versions) instead of copying exact versions.
+- **Merge config, don't replace it.** Add only the `app.json`/`app.config.*` plugins and permissions the example introduces that the user lacks — keep their existing config block intact.
+- **Port the integration code.**
+- **Recreate env vars** from the example's `.env` shape — it holds placeholders, never working secrets.
+
+**Done when** the integration code is ported and every dependency, config plugin, permission, and env var it needs is accounted for in the user's app — not when it merely *looks* wired up.
+
+## Gotchas
+
+- **Default branch is `master`,** not `main` (matters for raw URLs and sparse checkout).
+- **Single-click deploy.** Every example has a launch URL: `https://launch.expo.dev/?github=https://github.com/expo/examples/tree/master/<example>`.
+
+## Related skills
+
+- Native UI components (@expo/ui package) → `expo-ui`
+- Styling and native-feeling screens → `expo-native-ui`
+- Navigation and routing → `expo-router`
+- Authoring a native module → `expo-module`
+- Upgrade the SDK before adopting a latest-SDK example → `expo-upgrade`
+
+## References
+
+- `./references/catalog.md` — categorized snapshot of the example library for fast triage.
+
+## Submitting Feedback
+If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
+```bash
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-examples" "<actionable feedback>"
+```
+Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/templates/default/apps/mobile/.agents/skills/expo-examples/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Expo Examples"
+  short_description: "Adapt or scaffold from the expo/examples repo of with-* integrations (Stripe, Clerk, Supabase, maps, SQLite, and more)"
+  default_prompt: "Use $expo-examples when integrating a third-party library or service into an Expo app to find the canonical with-* example to adapt, or to scaffold a new project with npx create-expo --example."

package/dist/templates/default/apps/mobile/.agents/skills/expo-examples/references/catalog.md

@@ -0,0 +1,105 @@
+# Example catalog (snapshot)
+
+A categorized view of [expo/examples](https://github.com/expo/examples) for fast triage. Each entry is a **single-concern integration demo** (one library/service, managed project, usually one screen) — not a full app. This snapshot drifts — the **live repo is the source of truth**. Confirm the exact name against `gh api repos/expo/examples/contents` and check `meta.json` for aliases/deprecations (see SKILL.md step 1) before recommending or scaffolding.
+
+Use any name with `npx create-expo --example <name>` (scaffold) or inspect it via `gh api repos/expo/examples/contents/<name>/<file>`.
+
+Most are single-screen integrations; a few differ:
+
+- **Full-stack** (include Expo Router `+api` routes — a backend too): `with-stripe`, `with-clerk`, `with-better-auth`, `with-openai`, `with-router-ai`, `with-graphql`, `with-s3`, `with-satori`.
+- **Larger showcases:** `with-shadcn`, `with-router-tv`, `with-router-menus`, `with-react-navigation`, `with-webgpu`.
+- **Starters (not integrations):** `blank`, `stickersmash`.
+
+## Auth & identity
+- `with-clerk` — Clerk authentication
+- `with-auth0` — Auth0 login
+- `with-better-auth` — Better Auth
+- `with-magic` — Magic passwordless auth
+- `with-facebook-auth` — Facebook login
+- `with-firebase-saml-login` — Firebase SAML SSO
+
+## Payments
+- `with-stripe` — Stripe payments (native + web)
+
+## Backend, data & storage
+- `with-convex` — Convex realtime backend
+- `with-legend-state-supabase` — Supabase + Legend-State sync
+- `with-firebase-storage-upload` — Firebase Storage uploads
+- `with-aws-storage-upload`, `with-s3` — AWS / S3 file uploads
+- `with-apollo`, `with-graphql` — GraphQL clients
+- `with-formdata-image-upload` — multipart image upload
+
+## Local database & state
+- `with-sqlite` — expo-sqlite
+- `with-libsql` — libSQL / Turso
+- `with-tinybase` — TinyBase local-first store
+- `with-zustand` — Zustand state management
+
+## Navigation & routing
+- `with-router` — Expo Router basics
+- `with-react-navigation` — React Navigation (stacks + tabs)
+- `with-drawer-navigation` — drawer navigator
+- `with-router-menus` — native context menus with Router
+- `with-router-uniwind` — Router + Uniwind styling
+- `with-router-ai` — Router + AI chat UI
+- `with-router-tv` — Router on TV
+- `with-react-router` — React Router (web)
+
+## Styling & UI
+- `with-tailwindcss` — Tailwind / NativeWind
+- `with-styled-components` — styled-components
+- `with-shadcn` — shadcn-style components
+- `with-moti` — Moti animations
+- `with-custom-font` — custom fonts
+- `with-svg` — react-native-svg
+- `with-icons` — icon sets
+- `with-splash-screen` — custom splash screen
+- `with-video-background` — full-screen video background
+
+## Animation & graphics
+- `with-reanimated` — Reanimated
+- `with-skia` — React Native Skia 2D graphics
+- `with-three`, `with-react-three-fiber` — three.js / R3F 3D
+- `with-webgpu` — WebGPU
+- `with-processing` — Processing-style sketches
+- `with-react-flow` — node/flow diagrams
+- `with-victory-native` — charts
+
+## AI & ML
+- `with-openai` — OpenAI API
+- `with-router-ai` — AI chat app with Expo Router
+- `with-google-vision` — Google Cloud Vision
+- `with-tfjs-camera` — TensorFlow.js on the camera
+
+## Media & device
+- `with-camera` — expo-camera
+- `with-maps` — react-native-maps
+- `with-webrtc` — WebRTC
+- `with-pdf` — render / view PDFs
+
+## Web & rendering
+- `with-nextjs` — Next.js + Expo
+- `with-rsc` — React Server Components
+- `with-react-strict-dom` — React Strict DOM
+- `with-react-compiler` — React Compiler
+- `with-html` — render raw HTML
+- `with-satori` — OG image generation with Satori
+- `with-workbox` — service worker / PWA
+- `with-webbrowser-redirect` — expo-web-browser auth redirect
+
+## Platform: TV, widgets
+- `with-tv` — Apple TV / Android TV
+- `with-widgets` — iOS / Android home-screen widgets
+
+## Tooling, testing & monorepo
+- `with-typescript` — TypeScript baseline
+- `with-yarn-workspaces` — Yarn monorepo
+- `with-storybook` — Storybook
+- `with-maestro` — Maestro E2E tests
+- `with-sentry` — Sentry error monitoring
+- `with-socket-io` — Socket.IO realtime
+- `with-github-remote-build-cache-provider` — remote build cache on GitHub
+
+## Starters
+- `blank` — minimal app
+- `stickersmash` — the tutorial app

package/dist/templates/default/apps/mobile/.agents/skills/expo-migrate-module/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: expo-migrate-module
+description: Migrate an existing Apple/Swift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) while preserving its JavaScript and TypeScript contract. Use when converting or incrementally adopting @ExpoModule, @JS, @Event, @SharedObject, or @Record in an existing module. Do not use for creating a new module, general Expo SDK upgrades, or Android/Kotlin migrations.
+version: 1.0.0
+license: MIT
+---
+
+# Migrate an Expo Module
+
+Migrate the Swift side of an existing Expo module without changing its observable JS API. Treat the current JS/TypeScript surface and tests as the compatibility contract. Leave Kotlin on the 1.0 DSL unless the user explicitly expands the task.
+
+## Prerequisite
+
+Use `expo` `57.0.21` or newer. Earlier `57.x` versions can compile the macros but lack many of the 2.0 features and performance optimizations, so do not target them. Before editing, check the target's installed version (`expo` in `package.json`/lockfile, or `npm ls expo`). If it is older, stop and tell the user to upgrade first.
+
+Check the example app's own `package.json` too, not only the module root. The example app is the integration surface you build and launch in step 4, so it needs the same floor.
+
+This is a floor, not a guarantee: the exact macro and core surface still varies within `57.x`, so step 2 must still verify the checked-out source.
+
+SDK 57 ships the macros as **experimental and undocumented**, with the official beta in SDK 58. The API can still change under you. Say this to the user before a large migration, and prefer incremental mixed mode over converting a module wholesale.
+
+## References
+
+- Read `references/migration-map.md` before changing source. It contains the 1.0-to-2.0 mappings, semantic traps, and mixed-mode rules.
+- Read `references/example.md` for a full before/after walkthrough of one module through mixed mode to a complete migration. Consult it when you need to see how the per-member rules compose.
+- Read `references/compatibility.md` when the checked-out `expo-modules-core` version or branch is not known to support every requested macro. It explains how to verify the actual compile-time and runtime surface instead of guessing from a version number, and lists what the macros plugin gained through `0.10.0`.
+
+## Workflow
+
+### 1. Establish the contract
+
+Inspect repository instructions and the worktree before editing. Locate the Swift module classes, records, shared objects, native views, JS/TS bindings, tests, example app, podspec, `expo-module.config.json`, and installed or checked-out `expo-modules-core`.
+
+Inventory every exported item before rewriting it:
+
+- module and shared-object JS names
+- function names, arity, labels, defaults, nullability, sync/async behavior, errors, and queue/thread semantics (note which `AsyncFunction` bodies do blocking or long-running work, and any `.runOnQueue(...)`)
+- property names, mutability, and constant caching behavior
+- event wire names and payload shapes
+- record field names, defaults, requiredness, and nullability
+- shared-object constructors and instance/static placement (`Function` vs `StaticFunction`/`StaticAsyncFunction`)
+- lifecycle hooks and views
+
+Use the TypeScript declarations and JS call sites to resolve ambiguity. Do not silently "improve" requiredness, rename an event, or change sync behavior during a syntax migration.
+
+### 2. Verify the available 2.0 surface
+
+Inspect the macro declarations and matching core hooks in the dependency actually used by the target. Do not assume that all items in the 2.0 design are present because one macro compiles.
+
+Classify each 1.0 item as:
+
+- **Migrate:** both its macro and required core runtime support exist.
+- **Keep in DSL:** mixed mode preserves it safely, or 2.0 lacks an equivalent.
+- **Blocked:** migration would alter the JS contract or requires unavailable runtime support.
+
+Prefer an incremental mixed-mode result over speculative generated code. Keep `definition()` for any remaining DSL elements; delete it only when it is empty and the resolved module name is preserved by `@ExpoModule`.
+
+### 3. Apply the migration
+
+Migrate one semantic group at a time: module naming, functions, properties/constants, events, shared objects, then records. Keep the diff narrow.
+
+Follow these invariants:
+
+- Preserve every existing JS-visible name explicitly when Swift naming rules or macro defaults differ.
+- Keep original optional/default behavior. An optional 1.0 record field must not become required merely because 2.0 can express required fields.
+- Do not migrate same-JS-name overloads unless the checked-out macro groups and dispatches them.
+- Preserve async threading behavior. A 1.0 `AsyncFunction` body ran off the JS thread; a 2.0 `async` `@JS` member starts on it and leaves only at the first `await`. A body that never awaits therefore blocks the JS thread, with no change to the JS signature. Audit what runs before the first `await`, and never leave blocking I/O on the JS actor. Fix with `@JS(.concurrent)`, or restructure onto Swift Concurrency or a continuation. Queue-pinned functions get the same treatment. See the threading section in `references/migration-map.md`.
+- Verify core support before migrating views, unions, synchronous events, shared-object static members, or free-form `Any` arguments. The macros plugin has shipped ahead of core on every one of these, so check the checked-out core rather than a plugin version, and leave unsupported members on the 1.0 DSL. `references/compatibility.md` has the per-capability checks.
+- Keep `expo-module.config.json` listing every module class under `apple.modules`. The entries are bare Swift class names, so renaming a class during migration detaches the module silently: it builds, then is absent at runtime. A migrated class must also stay `public` or `open`. SDK 58's auto-discovery is what retires these entries.
+- Do not change Kotlin, JS wrappers, or public `.d.ts` files unless the user requested an API change.
+- Never write macro-generated symbols into the module's source. The macro emits them; hand-writing or overriding them is not part of a migration.
+
+After each group, search for old DSL entries and call sites that should have moved. Avoid broad formatting or unrelated cleanup.
+
+### When a 2.0 equivalent is missing or a group fails
+
+When step 2 classified an item as **Blocked**, or a migrated group fails to build or breaks the contract, do not force it. Stop on that group and:
+
+1. **Ask the user how to proceed** for that item, with two options:
+   - **Co-exist:** keep the item in the 1.0 `definition()` DSL alongside the migrated `@ExpoModule` (mixed mode) and continue with the other groups.
+   - **Revert:** back out the group's edits, leaving it untouched on 1.0, and move on.
+
+   Default to co-existence when mixed mode is verified safe, since it preserves the most progress. Revert when the half-applied change left the module in a non-building state and cannot be salvaged incrementally.
+
+2. **Open a tracking issue on `expo/expo`** noting the functionality that 2.0 does not yet cover, so the gap is recorded rather than silently worked around. Use `gh issue create --repo expo/expo` and confirm with the user before posting (per repo conventions, do not post outward-facing comments without approval). Include:
+   - the 1.0 member and its JS contract
+   - the specific macro or core hook that is missing (cite the evidence gap from `references/compatibility.md`)
+   - the `expo-modules-core` version/branch checked out
+
+   Reference the issue in the handoff so the remaining DSL entry is traceable to a known limitation.
+
+Keep going with the groups that do migrate cleanly; one blocked member does not block the rest.
+
+### 4. Verify behavior
+
+Run the narrowest available checks first, then the real integration surface:
+
+1. Build or type-check the Apple module against the target `expo-modules-core`.
+2. Run native unit tests and JS/TS tests.
+3. Build and launch the example app when the repository provides one.
+4. Confirm `expo-module.config.json` still names every module class under `apple.modules`, matching the Swift class names as they now stand. A stale entry builds clean and fails only at runtime, so the example app must actually resolve the module, not merely compile.
+5. Compare the final exported surface with the inventory from step 1.
+6. Search for stale `Name`, migrated `Function`/`AsyncFunction`/`StaticFunction`/`StaticAsyncFunction`/`Property`/`Constant`/`Events` entries, old `sendEvent` calls, `@Field`, and duplicate registrations. Search the source you wrote, not macro expansion output.
+
+Expansion tests alone are insufficient: generated macro code can look correct while failing to link or run against a mismatched core. If dependencies changed or macro plugin flags are missing, reinstall JS dependencies as appropriate, run the repository's CocoaPods installation workflow, and restart Xcode before diagnosing plugin communication failures.
+
+## Handoff
+
+Never print macro-generated or core-internal symbol names to the user. `references/compatibility.md` cites them so you can grep for them, but they are implementation details that change between plugin revisions, and they are noise in a report. Name a capability by its macro (`@JS static`, `@Event(sync:)`) and by observable JS behavior. Say "the installed core does not support decoding free-form dictionary arguments yet", not the name of the missing method. The exception is a tracking issue on `expo/expo`, where the specific missing hook is the point.
+
+Report:
+
+- which members moved to 2.0
+- which members intentionally remain in the 1.0 DSL and why
+- any compatibility-sensitive choices, especially event names, record requiredness, constants, and queues
+- the commands run and any verification not completed
+
+## Submitting Feedback
+If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
+```bash
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-migrate-module" "<actionable feedback>"
+```
+Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/templates/default/apps/mobile/.agents/skills/expo-migrate-module/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Migrate Expo Module"
+  short_description: "Migrate Swift Expo modules from 1.0 DSL to 2.0"
+  default_prompt: "Use $expo-migrate-module to migrate this Expo module's Swift implementation from the 1.0 definition DSL to the 2.0 macro API without changing its JavaScript contract."

package/dist/templates/default/apps/mobile/.agents/skills/expo-migrate-module/references/compatibility.md

@@ -0,0 +1,130 @@
+# Expo Modules API 2.0 Compatibility Checks
+
+The Expo Modules API 2.0 design and implementation evolve across the macros plugin and `expo-modules-core`. Verify the checked-out dependency instead of relying on an SDK-number claim.
+
+## Find the actual declarations
+
+Locate `ExpoModulesMacros.swift` in the target repository or installed dependencies (use your search tool, or portable shell commands - do not assume `rg` is installed):
+
+```bash
+find . -name 'ExpoModulesMacros.swift' -not -path '*/node_modules/.cache/*'
+```
+
+Inspect the declarations that the user's source can import:
+
+```bash
+grep -nE 'public macro (ExpoModule|JS|Event|SharedObject|Record|Union|ViewProps|ExpoView)' <path-to-ExpoModulesMacros.swift>
+```
+
+A declaration proves only that Swift recognizes the attribute, not that the code the macro generates will compile and run against the installed core.
+
+## Check paired core support
+
+The macros plugin and core can drift independently, so a successful macro expansion does not prove the generated code links or is called at runtime.
+
+> The symbol names in this section are macro internals, for your own verification only. Never print them in the conversation, name them in your report, or write them into the migrated module's source. Report a capability by its macro (`@JS static`, `@Event(sync:)`) and by observable JS behavior. See the reporting rule in `SKILL.md`.
+
+**Fast pre-check.** Search core for the hooks the generated code calls, to rule out an unsupported capability before you write any Swift:
+
+```bash
+grep -rnE '_decorateModule|_decorateSharedObject|_constructSharedObject|_jsName|EventEmitter|emitSync|StaticProperty|AnyViewProps|PropsDiff|_updateViewProps|didCreate|__expo_onStartListeningToEvent|decodeAnyDictionary|decodeAnyArray|JSOptions|UnionCaseMismatch' <expo-modules-core>
+```
+
+An absent hook is strong evidence the capability is unavailable. A present one is weaker: it proves the symbol exists, not that its signature matches what the plugin generates or that core ever calls it.
+
+**Confirm by compiling.** Write the smallest `@JS` member that uses the capability, build the module target against the checked-out core, and read the diagnostics:
+
+- The build succeeds: the capability is supported end to end.
+- The macro reports an error or warning: the plugin itself rejects the construct. The diagnostic names the supported alternative.
+- Expansion succeeds but linking fails on an undefined symbol: the plugin is ahead of core. Keep the member in the 1.0 DSL.
+
+Then exercise the member from the example app or a test, because a binding can link and still never be invoked.
+
+## Capability gates
+
+Treat these as independent capabilities. Confirm each by compiling a minimal member that uses it, then calling it from JS:
+
+| Capability | Macro surface | Core hook to grep (internal) | Confirm by |
+| --- | --- | --- | --- |
+| Module functions/properties | `@ExpoModule`, `@JS` | `_decorateModule` and its call site | calling the function and reading the property from JS |
+| Module name | `@ExpoModule("Name")` | `_jsName` and the name lookup that reads it | resolving the module under its expected JS name |
+| Records | `@Record` | coding conformances and field decode/encode | round-tripping a record argument and a record return value |
+| Async events | `@Event` | `EventEmitter` on modules and shared objects | receiving an emitted event through the module's JS listener |
+| Shared-object instances | `@SharedObject`, `@JS` | `_decorateSharedObject(prototype:)`, construction hook | constructing one from JS and calling an instance member |
+| Shared-object static members | `@JS static` | `_decorateSharedObject(constructor:)`, distinct from the `prototype:` overload | calling the member on the JS class itself, not an instance |
+| Synchronous events | `@Event(sync:)` | `emitSync` overloads | observing the listener run before the emit call returns |
+| Task-returning functions | `@JS` returning `Task` | `JavaScriptEncodable` for `Task` (encode-only) | awaiting the returned promise in JS |
+| Views | `@ViewProps`, `@ExpoView` | `AnyViewProps`, `PropsDiff`, `_updateViewProps` | rendering the view and updating every prop from JS |
+| Module lifecycle methods | lifecycle members on the module class | `AnyModule` requirements and holder call sites | observing each hook fire |
+| Free-form `Any` arguments | `@JS` with `Any`, `[Any]`, `[String: Any]` | `decodeAny`, `decodeAnyArray`, `decodeAnyDictionary` | building it, then passing a JS object through |
+| Off-JS-thread async start | `@JS(.concurrent)` | `JSOptions` and the options-taking `@JS` overload (plugin `0.10.0`) | the `@JS` declaration accepting an options argument |
+| Typed N-case unions | `@Union` | `Union` macro declaration and `UnionCaseMismatch` (plugin `0.10.0`) | round-tripping each case through the JS boundary |
+| Autolinked `@ExpoModule` discovery | none, it is a build-time step | none, `scan-modules` plus the autolinking consumer | the module loading without an `expo-module.config.json` entry |
+
+If a capability cannot be confirmed, keep that item in the 1.0 DSL.
+
+## Known migration hazards
+
+Use this only as a warning list; checked-out source wins.
+
+- Async threading changed architecturally, not just syntactically: a 2.0 `async` member starts on the JS thread and leaves it at the first suspension point, where a 1.0 `AsyncFunction` never ran there. A verbatim migration can move blocking work onto the JS thread with no signature change. `@JS(.concurrent)` (plugin `0.10.0`) restores the 1.0 behavior, but needs a paired `JSOptions` type and a second `@JS` overload in core. See the threading table in `references/migration-map.md`.
+- Same-JS-name `@JS` overload grouping/dispatch was designed but not built; duplicate bindings could silently overwrite each other.
+- `@Union` landed in plugin `0.10.0`, but needs the paired `Union` macro declaration and `UnionCaseMismatch` exception in core. Decoding is first-match in case-declaration order, so preserving a 1.0 `Either`'s type order is part of the contract. See the unions section in `references/migration-map.md`.
+- Decode errors lacked the 1.0 argument-index wrapper. This affects diagnostics rather than call semantics, but tests asserting exact messages may fail.
+- `@ViewProps` had only an initial pure-macro slice; the UIKit typed props runtime and `@ExpoView` contract were still gated on core.
+- `@Event(sync: true)` macro generation existed, but core `emitSync` was still required.
+- Default asynchronous `@Event` was supported after core added `EventEmitter` to modules and shared objects.
+- `@JS` functions/properties, range-based arity, default/optional-aware calls, `@Record` field synthesis, async `@JavaScriptActor`, and shared-object decoration had landed in the macros work.
+- Shared-object `@JS static`/`class` members bind onto the constructor object through a `constructor:`-labeled decoration hook, separate from the `prototype:` one used for instance members. The plugin has emitted this binding since `v0.7.0`, but core shipped the `prototype:` overload well ahead of it, so a static member can expand and then fail to link. Instance support does not imply static support. Keep `StaticFunction`/`StaticAsyncFunction` entries in the 1.0 `Class(...)` block until the `constructor:` overload is present.
+- Async `@JS` bindings are two-phase: arguments decode synchronously before the asynchronous boundary, and return values encode on the JS thread. A 1.0 async function whose argument decoding had side effects ordered after the hop can therefore observe a different order.
+
+## Landed in the macros plugin since 0.8.0
+
+Free-form `Any` arguments and `scan-modules` shipped in `0.9.0`, both covered below. `@JS(.concurrent)` (see the threading section in `references/migration-map.md`) and `@Union` (see the unions section) shipped in `0.10.0`.
+
+All four are macro-side only. The plugin generates the code, but each needs a paired declaration or runtime hook in `expo-modules-core`, and core has been the lagging half throughout. A plugin version number therefore tells you nothing about whether a feature is usable. Check the checked-out core, per the capability gates above.
+
+### Free-form `Any` arguments in `@JS` (plugin `0.9.0`)
+
+`Any`, `[Any]`, and `[String: Any]` are accepted as **argument** types and decode through dedicated entry points instead of the type's own `.decode`:
+
+Free-form is decode-only, so the position where the type appears decides whether it is allowed:
+
+- **argument** (function, constructor, setter): compiles, with a warning steering you to `[String: JavaScriptValue]`
+- **return type**: compile error
+- **property**: compile error, because its getter always encodes
+
+Optional (`[String: Any]?`) and nested (`[String: [String: Any]]`) spellings are unsupported.
+
+These bindings decode through `JavaScriptValue.decodeAny`, `decodeAnyArray`, and `decodeAnyDictionary`. Core shipped the macro side first, so where those methods are absent the member expands and then fails to link. Confirm by building one minimal free-form argument against the checked-out core before migrating any others.
+
+Prefer `[String: JavaScriptValue]` when you can change the Swift signature without changing the JS contract. A 1.0 DSL function taking a loosely typed dictionary is often expressible that way, and it is the alternative the macro's own warning points to.
+
+### `scan-modules` for autolinked module discovery (plugin `0.9.0`)
+
+The scanner CLI merged into the shipped `ExpoModulesMacros-tool` binary, so one executable serves both the compiler plugin protocol (no arguments) and a CLI:
+
+```bash
+ExpoModulesMacros-tool scan-modules --platform iOS --define DEBUG ios/
+```
+
+Its JSON output is versioned and reports each detected module's access level. It evaluates `#if` conditions against `--platform` and repeatable `--define`, answers `canImport` for a curated set of Apple SDK frameworks, and prunes `node_modules` along with test and example directories (`Tests`, `UITests`, `__tests__`, `__mocks__`, `example`, `examples`, `e2e`).
+
+The intent is that `expo-modules-autolinking` detects `@ExpoModule` classes automatically, replacing the `expo-module.config.json` module list. **The scanner shipped ahead of that consumer**, so until autolinking actually calls it, discovery is not active. Consequences for a migration:
+
+- Keep the module's existing `expo-module.config.json` declarations, and verify they are correct before you finish. Listing every module class under `apple.modules` is a 1.0 requirement that still applies on SDK 57; 2.0 does not lift it. The entries are bare Swift class names with no compile-time link to the class, so a rename during migration silently detaches the module: it builds, and then is absent at runtime. SDK 58 adds auto-discovery, at which point these entries can be removed.
+- A migrated `@ExpoModule` class must be `public` or `open` to be linkable from the app target. The scanner reports each class's access level so inaccessible ones can be skipped with a diagnostic.
+- Product sources kept under a pruned directory name are invisible to the scanner. A package in that layout stays on `expo-module.config.json`, which opts it out of scanning.
+- You can run `scan-modules` yourself as a migration check: it lists which classes the macro attribute is actually detected on, which catches an `@ExpoModule` that landed in a conditional block or a non-public class.
+
+## Integration verification
+
+Use the target project's own commands. A robust sequence is:
+
+1. Run macro/unit tests if working inside the macros package.
+2. Compile the migrated native module against the paired core checkout.
+3. Re-run CocoaPods installation when plugin dependencies or injection changed.
+4. Restart Xcode after swapping a macro plugin binary; cleaning DerivedData alone may not reload it.
+5. Build the example app and execute existing JS/TS behavior tests.
+
+Do not report a migration complete based only on textual expansion tests.