docs(repo): list useHostedAuth as not mapped in the Expo verification map

.changeset/verify-expo-map-hosted-auth.md

@@ -0,0 +1,2 @@
+---
+---

.claude/skills/verify-clerk-expo/features/README.md

@@ -59,6 +59,6 @@ Each feature file starts with an H1 title and one paragraph describing the user-
 - [Native and JS session sync](./native-js-sync.md) covers a native sign-out and a native password sign-in reaching `useAuth`, `useUser`, and `useSession`, that sign-in surviving a relaunch, a second native sign-in in one process, a ticket sign-in reaching the native profile, and a JS sign-out clearing the hooks.
 - [Native modules](./native-modules.md) covers `useSignInWithGoogle` opening the native Google sign-in, a cancel of it on iOS, and on Android when back closes Google's page, and `useBiometricCredentials` reporting what its native module found on the device.
 
-Not mapped yet: SSO through `useSSO` (no real OAuth on simulators), a Google or Apple native sign-in with a real account, passkeys, enrolling or using a biometric (no associated domains or Secure Enclave on the simulator), session tasks in the native views, and the update screen that `<ClerkProvider>` shows over the app on iOS and Android when the instance requires a newer version of it (`packages/expo/src/update-required/`, or the native clerk-ios or clerk-android screen when the app does not install `expo-application`; it needs a minimum version for `com.clerk.exponativebuildfixture` in the instance's native app settings, which the standard settings do not set and a settings file cannot declare).
+Not mapped yet: SSO through `useSSO` (no real OAuth on simulators), sign-in and sign-up in Account Portal through `useHostedAuth` from `@clerk/expo/hosted-auth`, which opens a browser that no spec drives and the test app has no button for (`packages/expo/src/hooks/useHostedAuth.ts`), a Google or Apple native sign-in with a real account, passkeys, enrolling or using a biometric (no associated domains or Secure Enclave on the simulator), session tasks in the native views, and the update screen that `<ClerkProvider>` shows over the app on iOS and Android when the instance requires a newer version of it (`packages/expo/src/update-required/`, or the native clerk-ios or clerk-android screen when the app does not install `expo-application`; it needs a minimum version for `com.clerk.exponativebuildfixture` in the instance's native app settings, which the standard settings do not set and a settings file cannot declare).
 
 Organizations have no page, because a user of the test app has no way to reach organization UI. This holds for the native components only. `@clerk/expo/web` exports the clerk-js OrganizationProfile, OrganizationSwitcher, OrganizationList, and CreateOrganization for Expo web, but the test app runs native only. `@clerk/expo-native-components` exports AuthView, UserButton, and UserProfileView and no OrganizationSwitcher or OrganizationProfileView. The profile that the UserButton opens lists `Manage account`, `Security`, `Add account`, and `Sign out`, with `Switch account` once a second session exists, and no organization row, in the pinned clerk-ios and clerk-android releases, though the standard settings turn organizations on. The one organization screen that a native view shows is a session task in AuthView, choose or create an organization, which needs `force_organization_selection` on. The harness seeds users, sign-in tickets, and, through `host.seedOrganization`, organizations whose members hold one of the harness roles. It cannot seed invitations, so no spec can reach a choose-organization task that lists an invitation. Today such a state can be shown only with a local patch that is not committed, and the description of the pull request that shows it says so.