@tastic/hud 0.6.0 → 0.8.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tastic/hud",
-  "version": "0.6.0",
+  "version": "0.8.1",
   "description": "Visual component kit for local-multiplayer React Native games: inline (non-modal) popovers, dropdowns, color pickers, gauges, ready buttons, and dialogs, built to stay scoped to one player's own zone on a shared screen",
   "keywords": [
     "react-native",
@@ -33,6 +33,13 @@
       "types": "./dist/index.d.ts",
       "import": "./dist/index.mjs",
       "require": "./dist/index.js"
+    },
+    "./skia-gate": {
+      "react-native": "./src/SkiaGate.tsx",
+      "browser": "./src/SkiaGate.web.tsx",
+      "types": "./dist/SkiaGate.d.ts",
+      "import": "./dist/SkiaGate.mjs",
+      "require": "./dist/SkiaGate.js"
     }
   },
   "main": "dist/index.js",
@@ -63,14 +70,14 @@
   },
   "prettier": "@infinitetoken/eslint-config/prettier",
   "devDependencies": {
-    "@infinitetoken/eslint-config": "0.2.0",
-    "@infinitetoken/jest-config": "^0.2.0",
+    "@infinitetoken/eslint-config": "^0.2.0",
+    "@infinitetoken/jest-config": "^0.3.0",
     "@infinitetoken/tsconfig": "^0.4.1",
     "@rific/auto-paper": "^0.10.3",
     "@rific/feedback-press": "^0.10.8",
-    "@rific/updater": "^0.4.2",
+    "@rific/updater": "^0.6.0",
     "@shopify/react-native-skia": "^2.6.2",
-    "@tastic/core": "^0.2.0",
+    "@tastic/core": "^0.3.0",
     "@testing-library/dom": "^10.4.1",
     "@testing-library/react": "^16.3.2",
     "@types/jest": "^30.0.0",
@@ -94,7 +101,7 @@
     "@rific/feedback-press": ">=0.10.0",
     "@rific/updater": ">=0.4.0",
     "@shopify/react-native-skia": ">=1.5.0",
-    "@tastic/core": ">=0.1.0",
+    "@tastic/core": ">=0.3.0",
     "react": ">=19.0.0",
     "react-native": ">=0.76.0",
     "react-native-paper": ">=5.0.0",

package/src/BaseSettingsDialog.tsx

@@ -1,7 +1,7 @@
 import { AutoAppearancePicker, Dialog, useAutoPaperTheme } from '@rific/auto-paper'
 import { Button, SoundContext, TouchableRipple, useHapticSettings, useSoundSettings, useVibration } from '@rific/feedback-press'
 import { useUpdater } from '@rific/updater'
-import { useIsTouchPrimaryDevice } from '@tastic/core'
+import { useIsTouchPrimaryDevice, useRotation } from '@tastic/core'
 import { ReactNode, useContext, useState } from 'react'
 import { Platform, ScrollView, StyleSheet, View } from 'react-native'
 import { Icon, Portal, Text } from 'react-native-paper'
@@ -26,10 +26,11 @@ function SettingIcon({ source, color, containerColor }: SettingIconProps) {
 export interface BaseSettingsDialogProps {
   visible: boolean
   onDismiss: () => void
-  // Live physical-hold rotation (see @tastic/split-screen's getViewRotation) — this is a centered,
-  // app-wide modal with no per-player zone to match (unlike an in-game round-over dialog), so it
-  // just rotates its own content in place; defaults to 0 for a caller that doesn't track one (a
-  // game with no face-to-face two-player mode has nothing to stay consistent with anyway).
+  // Explicit override for the live physical-hold rotation (see @tastic/core's useRotation) — this is
+  // a centered, app-wide modal with no per-player zone to match (unlike an in-game round-over
+  // dialog), so it just rotates its own content in place. Defaults to a live ambient read via
+  // useRotation() when omitted; pass this only when a caller's own reading needs to differ from the
+  // ambient one (rare — most callers should simply omit it).
   rotation?: number
   // Each app's own OTA version (e.g. release.otaVersion) — not something this package can read
   // itself, since every consuming app tracks its own release.ts independently. Accepts a number too
@@ -76,8 +77,10 @@ export interface BaseSettingsDialogProps {
 // is the seam for whatever isn't shared: a game with its own board/difficulty settings (or a stats
 // backup flow, or anything else genuinely specific to it) renders those below Appearance, not by
 // forking this component.
-export function BaseSettingsDialog({ visible, onDismiss, rotation = 0, version, lockOrientation, onLockOrientationChange, deferBottomEdgeGestures, onDeferBottomEdgeGestures, hideSound = false, hideHaptics = false, hideAppearance = false, hideUpdateCheck = false, onUpdateError, children }: BaseSettingsDialogProps) {
+export function BaseSettingsDialog({ visible, onDismiss, rotation: rotationOverride, version, lockOrientation, onLockOrientationChange, deferBottomEdgeGestures, onDeferBottomEdgeGestures, hideSound = false, hideHaptics = false, hideAppearance = false, hideUpdateCheck = false, onUpdateError, children }: BaseSettingsDialogProps) {
   const { dark, colors } = useAutoPaperTheme()
+  const ambientRotation = useRotation()
+  const rotation = rotationOverride ?? ambientRotation
   // Also gates the Lock Orientation row below (alongside showLockOrientation itself) — true
   // unconditionally on native (see the hook's own doc), so this only actually excludes a
   // desktop/laptop browser, where a mouse-driven window has no physical orientation to lock

package/src/BaseStatsScreen.tsx

@@ -1,5 +1,6 @@
 import { useAutoPaperTheme } from '@rific/auto-paper'
 import { Button, IconButton } from '@rific/feedback-press'
+import { useRotation } from '@tastic/core'
 import { ReactNode, useState } from 'react'
 import { ScrollView, StyleSheet, View } from 'react-native'
 import { Icon, Portal, Text } from 'react-native-paper'
@@ -10,12 +11,12 @@ import { Icon, Portal, Text } from 'react-native-paper'
 type MD3TextVariant = 'displayLarge' | 'displayMedium' | 'displaySmall' | 'headlineLarge' | 'headlineMedium' | 'headlineSmall' | 'titleLarge' | 'titleMedium' | 'titleSmall' | 'labelLarge' | 'labelMedium' | 'labelSmall' | 'bodyLarge' | 'bodyMedium' | 'bodySmall'
 
 interface Props {
-  // Live physical-hold rotation (see @tastic/split-screen's getViewRotation) — this dialog renders
-  // as a centered Portal modal, unaffected by whichever screen's own FakeLandscapeView wraps its
-  // trigger, so it has to rotate its own card content to read right-side-up for whichever way the
-  // phone is actually being held. Defaults to 0 for a caller that doesn't track one — matches
-  // BaseSettingsDialog's own identical prop, though the first apps consuming this screen shell
-  // don't wrap it in a FakeLandscapeView at all and so never have a nonzero one to give.
+  // Explicit override for the live physical-hold rotation (see @tastic/core's useRotation) — only
+  // affects this component's own Portal-rendered reset-confirm overlay, which (like any Portal
+  // content) is unaffected by whichever screen's own FakeLandscapeView wraps the trigger and so has
+  // to rotate itself. Defaults to a live ambient read via useRotation() when omitted — note this
+  // does NOT make the header/scrollable content below rotate; the caller's own screen still needs
+  // its own FakeLandscapeView wrap for that (this component has no transform on its own main body).
   rotation?: number
   title?: string
   // 'headlineSmall' (this screen's own default, below) — was originally 'displaySmall' (the full
@@ -67,8 +68,10 @@ interface Props {
 // black/white convention. `children` is the seam for whatever isn't shared: this component has no
 // opinion on what a "stat" is or how achievements are catalogued — see StatRow/StatSection/
 // AchievementRow for the smaller presentational pieces built to go inside it.
-export function BaseStatsScreen({ rotation = 0, title = 'Achievements', titleVariant = 'headlineSmall', onBack, insets, onReset, resetLabel = 'Reset All Stats', resetConfirmTitle = 'Reset Everything?', resetConfirmBody = 'This permanently erases all stats and achievements. This cannot be undone.', fg: fgOverride, bg: bgOverride, cardBg: cardBgOverride, accentColor: accentColorOverride, children }: Props) {
+export function BaseStatsScreen({ rotation: rotationOverride, title = 'Achievements', titleVariant = 'headlineSmall', onBack, insets, onReset, resetLabel = 'Reset All Stats', resetConfirmTitle = 'Reset Everything?', resetConfirmBody = 'This permanently erases all stats and achievements. This cannot be undone.', fg: fgOverride, bg: bgOverride, cardBg: cardBgOverride, accentColor: accentColorOverride, children }: Props) {
   const { dark, colors } = useAutoPaperTheme()
+  const ambientRotation = useRotation()
+  const rotation = rotationOverride ?? ambientRotation
   const [confirmResetVisible, setConfirmResetVisible] = useState(false)
   const showReset = !!onReset
 

package/src/ConfirmDialog.tsx

@@ -0,0 +1,104 @@
+import { useAutoPaperTheme } from '@rific/auto-paper'
+import { Button } from '@rific/feedback-press'
+import { StyleSheet, View } from 'react-native'
+import { Icon, Portal, Text } from 'react-native-paper'
+
+export interface ConfirmDialogProps {
+  visible: boolean
+  title: string
+  message: string
+  confirmLabel: string
+  cancelLabel: string
+  onConfirm: () => void
+  onCancel: () => void
+  // Live physical-hold rotation (see @tastic/split-screen's getViewRotation) - same convention as
+  // BaseSettingsDialog's own rotation prop; defaults to 0 for a caller with no per-player zone to
+  // match (a portrait-only or single-player game has nothing to stay consistent with).
+  rotation?: number
+  // Any react-native-paper Icon `source` name, shown above the title - defaults to a plain
+  // question mark, since this component has no way to know why a caller is asking.
+  icon?: string
+  // Whether the confirm button reads as destructive (the fleet's shared `danger` semantic role)
+  // instead of the default primary-colored affirmative action.
+  destructive?: boolean
+}
+
+// A themed replacement for the native Alert.alert/window.confirm two-button confirm pattern - the
+// same "retro card overlay" look BaseSettingsDialog's own update-check info messages already use
+// (see its onInfo/infoMessage), generalized here into its own reusable, exported component for any
+// caller that needs a real yes/no decision instead of a single OK dismissal. A solid backdrop +
+// centered card, not react-native-paper's own Dialog (which BaseSettingsDialog uses instead) -
+// this renders identically on every platform, including web, where react-native-web's Alert.alert
+// is a hard no-op (confirmed: its entire implementation is `static alert() {}`) and Dialog's own
+// Portal-based positioning has its own web quirks BaseSettingsDialog already works around.
+export function ConfirmDialog({ visible, title, message, confirmLabel, cancelLabel, onConfirm, onCancel, rotation = 0, icon = 'help-circle-outline', destructive = false }: ConfirmDialogProps) {
+  const { dark, colors } = useAutoPaperTheme()
+  if (!visible) return null
+
+  // High-contrast retro look: literal black/white by appearance, not auto-paper's own (slightly
+  // tinted) background role - same convention BaseSettingsDialog's own overlay card uses.
+  const fg = dark ? '#FFFFFF' : '#000000'
+  const cardBg = dark ? '#111111' : '#F2F2F2'
+  const cardBorder = dark ? 'rgba(255,255,255,0.2)' : 'rgba(0,0,0,0.2)'
+  const accent = destructive ? colors.danger : colors.primary
+  const onAccent = destructive ? colors.onDanger : colors.onPrimary
+
+  return (
+    <Portal>
+      <View style={styles.overlay}>
+        <View style={[styles.card, { backgroundColor: cardBg, borderColor: cardBorder }, rotation % 360 !== 0 && { transform: [{ rotate: `${rotation}deg` }] }]}>
+          <Icon source={icon} size={64} color={accent} />
+          <Text variant='headlineLarge' style={[styles.title, { color: accent }]}>
+            {title}
+          </Text>
+          <Text variant='bodyLarge' style={[styles.body, { color: fg }]}>
+            {message}
+          </Text>
+          <View style={styles.actions}>
+            <Button mode='outlined' onPress={onCancel} style={styles.actionButton}>
+              {cancelLabel}
+            </Button>
+            <Button mode='contained' onPress={onConfirm} style={styles.actionButton} buttonColor={accent} textColor={onAccent}>
+              {confirmLabel}
+            </Button>
+          </View>
+        </View>
+      </View>
+    </Portal>
+  )
+}
+
+const styles = StyleSheet.create({
+  actionButton: {
+    flex: 1
+  },
+  actions: {
+    flexDirection: 'row',
+    gap: 12,
+    width: '100%'
+  },
+  body: {
+    textAlign: 'center'
+  },
+  card: {
+    alignItems: 'center',
+    borderRadius: 20,
+    borderWidth: 1,
+    gap: 16,
+    maxWidth: 360,
+    padding: 32
+  },
+  overlay: {
+    alignItems: 'center',
+    backgroundColor: 'rgba(0,0,0,0.72)',
+    bottom: 0,
+    justifyContent: 'center',
+    left: 0,
+    position: 'absolute',
+    right: 0,
+    top: 0
+  },
+  title: {
+    fontWeight: 'bold'
+  }
+})

package/src/ControlSchemePicker.tsx

@@ -0,0 +1,53 @@
+import { useIsTouchPrimaryDevice } from '@tastic/core'
+import { Platform } from 'react-native'
+
+import { MenuOption, SectionedDropdown } from './SectionedDropdown'
+import { PopoverHost } from './usePopoverHost'
+
+export interface ControlSchemePickerProps<T extends string | number> {
+  id: string
+  host: PopoverHost
+  value: T
+  onChange: (value: T) => void
+  options: MenuOption<T>[]
+  // Another seat's currently-selected scheme, if any — passed straight through as the underlying
+  // section's own takenValue (see SectionedDropdown's own doc: stays in the list, shown disabled,
+  // rather than filtered out). Two local seats sharing one physical keyboard (and, depending on your
+  // own option set, one mouse) can't both be assigned the same scheme at once; this is what a caller
+  // wires up to prevent that.
+  takenValue?: T
+  accentColor: string
+  mutedColor: string
+  onAccentColor?: string
+  dark: boolean
+  align?: 'left' | 'right' | 'center'
+  labelFontFamily?: string
+}
+
+// A single-select SectionedDropdown, opinionated for exactly one job: letting a local seat pick
+// which physical input drives it in a couch-multiplayer game. Fixes the trigger icon and
+// accessibility label so every game's control-scheme picker looks and reads the same, and — the
+// actual reason this exists as its own component rather than a usage snippet in each app's own
+// docs — bakes in the "does this even mean anything right now" gate every consumer was independently
+// re-deriving: a physical keyboard scheme has no meaning on a touch-primary device (there's nothing
+// to pick a *keyboard* layout for), and this repo's own components target React Native Web, where
+// `Platform.OS !== 'web'` means native/touch already, so keying off `useIsTouchPrimaryDevice` alone
+// isn't enough on its own — a native touch device still needs the `Platform.OS` check to be excluded
+// the same way a desktop browser needs the touch check. Renders nothing at all when either
+// condition fails, rather than a disabled/empty picker, so a caller can mount this unconditionally
+// inside its own per-seat layout (a `View` row alongside a color picker, say) without its own
+// `Platform`/`useIsTouchPrimaryDevice` branch — an always-rendered-but-sometimes-null child is a
+// no-op in a flex layout, so the surrounding row collapses to just its other children automatically.
+//
+// Deliberately generic over `T` (matching SectionedDropdown's own `MenuOption<T>`) rather than
+// hardcoding a fixed scheme union: this repo has no opinion on which schemes exist — the raw
+// physical-key layouts (wasd/arrows/ijkl/numpad) live in `@tastic/input`, and any extra values with
+// no keys of their own (a "keep using pointer input" option, say) are purely a per-app label — so a
+// caller always supplies its own `options` (and typically its own `T`) rather than this component
+// importing `@tastic/input` and choosing a set for every consumer.
+export function ControlSchemePicker<T extends string | number>({ id, host, value, onChange, options, takenValue, accentColor, mutedColor, onAccentColor, dark, align, labelFontFamily }: ControlSchemePickerProps<T>) {
+  const isTouchPrimary = useIsTouchPrimaryDevice()
+  if (Platform.OS !== 'web' || isTouchPrimary) return null
+
+  return <SectionedDropdown id={id} host={host} icon='keyboard-outline' accessibilityLabel='Control scheme' sections={[{ kind: 'single', id: 'controls', options, value, onChange, takenValue }]} accentColor={accentColor} mutedColor={mutedColor} onAccentColor={onAccentColor} dark={dark} align={align} labelFontFamily={labelFontFamily} />
+}

package/src/CornerActionButtons.tsx

@@ -12,6 +12,14 @@ interface Props {
   // @tastic/split-screen's rotateInsets) — this component just adds the fixed 8px margin on top,
   // it doesn't know anything about physical device orientation itself.
   insets: { top: number; left: number; right: number }
+  // Overrides the top-left button's icon (a react-native-paper/MaterialCommunityIcons name) and its
+  // accessibility label — default 'arrow-left'/'Back'. Not every screen's top-left control is
+  // actually "undo the last navigation": a flat menu/detail screen with nothing deeper to pop back
+  // through often wants a literal home/menu affordance driving an absolute navigation instead (see
+  // e.g. Solitaire's GameChrome, whose onBack navigates straight to its root route). Pass both
+  // together — an icon without a matching label (or vice versa) misleads screen readers/tooltips.
+  backIcon?: string
+  backLabel?: string
 }
 
 // Back (top-left) + Settings (top-right) icon buttons, fixed at the screen's rotated corners — the
@@ -20,10 +28,10 @@ interface Props {
 // right answer for a screen where the top corners themselves fall *inside* one player's own rotated
 // zone (two-player face-to-face) — see SharedActionBand for that case instead, which callers select
 // between based on their own game-mode/orientation state (this component has no opinion on which).
-export function CornerActionButtons({ onBack, onSettings, fg, insets }: Props) {
+export function CornerActionButtons({ onBack, onSettings, fg, insets, backIcon = 'arrow-left', backLabel = 'Back' }: Props) {
   return (
     <>
-      <IconButton icon='arrow-left' iconColor={fg} size={24} style={[styles.back, { top: 8 + insets.top, left: 8 + insets.left }]} onPress={onBack} accessibilityLabel='Back' />
+      <IconButton icon={backIcon} iconColor={fg} size={24} style={[styles.back, { top: 8 + insets.top, left: 8 + insets.left }]} onPress={onBack} accessibilityLabel={backLabel} />
       <IconButton icon='cog' iconColor={fg} size={24} style={[styles.topRight, { top: 8 + insets.top, right: 8 + insets.right }]} onPress={onSettings} accessibilityLabel='Settings' />
     </>
   )

package/src/CornerStatusBadges.tsx

@@ -0,0 +1,87 @@
+import { StyleSheet, View } from 'react-native'
+import { Icon } from 'react-native-paper'
+
+// Mirrors @tastic/split-screen's own type of the same name, duplicated here rather than imported —
+// this package has never taken a dependency on @tastic/split-screen; every orientation/rotation-
+// derived value it touches (ConfirmDialog's and BaseSettingsDialog's own `rotation` props, this
+// component's orientationMode/p1OnRight below) is always a plain value the caller already resolved
+// via that package's own hook, never something this package reads itself.
+export type OrientationMode = 'faceToFace' | 'sideBySide'
+
+export interface CornerStatusBadgeSeat {
+  // Any react-native-paper Icon `source` name. Omit to still render the badge itself, empty — a
+  // seat with nothing to show right now is different from no seat at all (see `p1`/`p2` on
+  // CornerStatusBadgesProps below), and the empty badge is itself the answer ("nothing"), not a
+  // reason to hide the corner.
+  icon?: string
+}
+
+export interface CornerStatusBadgesProps {
+  orientationMode: OrientationMode
+  // Same "is this seat on the right" convention as @tastic/split-screen's own p1OnRight — only
+  // meaningful when orientationMode is 'sideBySide'; ignored in 'faceToFace', where seat 1 always
+  // owns the bottom half of a shared screen and seat 2 the top half, regardless of physical rotation.
+  p1OnRight: boolean
+  // Independently optional — omit a seat entirely to skip rendering its badge at all (e.g. a solo
+  // mode with no second seat to show anything for). Pass an object (even `{}`) to render that
+  // seat's badge with nothing in it.
+  p1?: CornerStatusBadgeSeat
+  p2?: CornerStatusBadgeSeat
+}
+
+const BADGE_SIZE = 30
+
+// Deliberately understated (small, low-opacity, no per-seat color) — a quiet corner landmark, not
+// something that should compete for attention with whatever's on screen underneath it.
+function StatusBadge({ icon }: { icon?: string }) {
+  return <View style={styles.badge}>{icon && <Icon source={icon} size={16} color='rgba(255,255,255,0.85)' />}</View>
+}
+
+// Generic per-seat corner status badge: at most one caller-supplied icon per seat (or none), each
+// pinned to that seat's own screen corner. Has zero opinion on what the icon means — originally
+// extracted from LightCycles' PowerupHud.tsx and Snake's SnakePowerupHud.tsx, which both used this
+// exact positioning and styling to reveal a held power-up, but this component only ever sees a
+// resolved icon name (or undefined) per seat, never the domain value behind it, so it's equally
+// suited to any other per-seat status a caller wants glanceable in a screen corner (connection
+// state, a turn-order marker, anything that's a single icon or nothing). Corner picked per seat
+// from orientationMode/p1OnRight — the same "is this seat on the right" convention
+// @tastic/split-screen's own consumers already use for zone/rotation decisions — so each badge
+// always sits in that seat's own zone rather than a side fixed regardless of which way the device
+// is being held. In 'faceToFace', column doesn't matter (each seat's zone spans the full width):
+// seat 1 stays bottom, seat 2 stays top, regardless of p1OnRight.
+export function CornerStatusBadges({ orientationMode, p1OnRight, p1, p2 }: CornerStatusBadgesProps) {
+  const p1OnRightSide = orientationMode === 'sideBySide' && p1OnRight
+  const p2OnLeftSide = orientationMode === 'sideBySide' && !p1OnRight
+  return (
+    <>
+      {p1 && (
+        <View pointerEvents='none' style={p1OnRightSide ? styles.bottomRight : styles.bottomLeft}>
+          <StatusBadge icon={p1.icon} />
+        </View>
+      )}
+      {p2 && (
+        <View pointerEvents='none' style={p2OnLeftSide ? styles.topLeft : styles.topRight}>
+          <StatusBadge icon={p2.icon} />
+        </View>
+      )}
+    </>
+  )
+}
+
+const styles = StyleSheet.create({
+  badge: {
+    alignItems: 'center',
+    backgroundColor: 'rgba(0,0,0,0.28)',
+    borderColor: 'rgba(255,255,255,0.18)',
+    borderRadius: BADGE_SIZE / 2,
+    borderWidth: 1,
+    height: BADGE_SIZE,
+    justifyContent: 'center',
+    opacity: 0.7,
+    width: BADGE_SIZE
+  },
+  bottomLeft: { bottom: 12, left: 12, position: 'absolute' },
+  bottomRight: { bottom: 12, position: 'absolute', right: 12 },
+  topLeft: { left: 12, position: 'absolute', top: 12 },
+  topRight: { position: 'absolute', right: 12, top: 12 }
+})

package/src/InlineColorPicker.tsx

@@ -1,12 +1,12 @@
 import { defaultColors, getContrastColor, SeedColor } from '@rific/auto-paper'
 import { TouchableRipple } from '@rific/feedback-press'
-import { clamp } from '@tastic/core'
+import { clamp, useRotation } from '@tastic/core'
 import { ScrollView, StyleSheet, useWindowDimensions, View } from 'react-native'
 import { Icon, Text } from 'react-native-paper'
 
 import { MONO_FONT } from './fonts'
 import { PopoverBody } from './PopoverBody'
-import { useAutoAlign } from './useAutoAlign'
+import { PopoverRotation, useAutoAlign } from './useAutoAlign'
 import { PopoverHost } from './usePopoverHost'
 
 // Presence check, not a full-string "is this exactly one emoji" validation — this only decides a
@@ -62,6 +62,10 @@ interface Props {
   // Manual override — omit to let the popover measure its own trigger and pick whichever alignment
   // keeps it from overflowing the screen edge (see useAutoAlign).
   align?: 'left' | 'right' | 'center'
+  // Explicit override for the rotation a @tastic/split-screen-style FakeLandscapeView (or
+  // equivalent) ancestor is currently applying — see SectionedDropdown's identical prop for the
+  // full reasoning. Defaults to a live ambient read via @tastic/core's useRotation() when omitted.
+  rotation?: PopoverRotation
   // Trigger glyph — defaults to a plain palette. Pass a distinct icon per slot (e.g. a face for a
   // human, a robot for CPU) to convey identity through the icon itself. Overridden by `tag` below
   // when present.
@@ -89,7 +93,9 @@ interface Props {
 // Renders inline rather than as a full-screen modal, scoped to its own panel — a modal color
 // picker would block the whole screen for one player while another can't touch their own panel at
 // the same time, which defeats the point of a split-screen lobby.
-export function InlineColorPicker({ id, host, value, onChange, previewValue, swatches = defaultColors, takenValue, allowSwapTaken, dark, align: alignOverride, icon = 'palette', tag, labelFontFamily = MONO_FONT, autoDismiss = true, columns, size = DEFAULT_SIZE }: Props) {
+export function InlineColorPicker({ id, host, value, onChange, previewValue, swatches = defaultColors, takenValue, allowSwapTaken, dark, align: alignOverride, rotation: rotationOverride, icon = 'palette', tag, labelFontFamily = MONO_FONT, autoDismiss = true, columns, size = DEFAULT_SIZE }: Props) {
+  const ambientRotation = useRotation()
+  const rotation = rotationOverride ?? ambientRotation
   const menuBg = dark ? '#000000' : '#FFFFFF'
   const { width: windowWidth } = useWindowDimensions()
   const autoColumns = clamp(Math.floor((windowWidth - 2 * SCREEN_MARGIN + SWATCHES_GAP) / (SWATCH_SIZE + SWATCHES_GAP)), MIN_COLUMNS, MAX_COLUMNS)
@@ -99,7 +105,7 @@ export function InlineColorPicker({ id, host, value, onChange, previewValue, swa
   const swatchesHeight = SWATCHES_BORDER_WIDTH * 2 + SWATCHES_PADDING * 2 + SWATCH_SIZE * swatchRows + SWATCHES_GAP * (swatchRows - 1)
 
   const open = host.openId === id
-  const { align: autoAlign, maxHeight, measured, triggerRef, verticalAlign } = useAutoAlign(open, swatchesWidth, swatchesHeight)
+  const { align: autoAlign, maxHeight, measured, triggerRef, verticalAlign } = useAutoAlign(open, swatchesWidth, swatchesHeight, rotation)
   const align = alignOverride ?? autoAlign
   const displayFor = previewValue ?? ((hex: string) => hex)
   const displayValue = displayFor(value)

package/src/SectionedDropdown.tsx

@@ -1,12 +1,13 @@
 import { getBlendedColor, getColorRoles } from '@rific/auto-paper'
 import { IconButton, TouchableRipple } from '@rific/feedback-press'
+import { useRotation } from '@tastic/core'
 import { ScrollView, StyleSheet, TextStyle, View } from 'react-native'
 import { Icon, Text } from 'react-native-paper'
 
 import { MONO_FONT } from './fonts'
 import { PopoverBody } from './PopoverBody'
 import TriggerGaugeHost from './TriggerGaugeHost'
-import { useAutoAlign } from './useAutoAlign'
+import { PopoverRotation, useAutoAlign } from './useAutoAlign'
 import { PopoverHost } from './usePopoverHost'
 
 const MENU_BORDER_WIDTH = 1
@@ -99,6 +100,17 @@ interface Props {
   // keeps it from overflowing the screen edge (see useAutoAlign). Only pass this to force a specific
   // side regardless of where the trigger actually sits.
   align?: 'left' | 'right' | 'center'
+  // Explicit override for the rotation a @tastic/split-screen-style FakeLandscapeView (or any other
+  // ancestor rotated the same way — a bare CSS `transform: rotate()`, not an actual OS-level
+  // orientation change) is currently applying. Defaults to a live ambient read via @tastic/core's
+  // useRotation() when omitted, so most callers never need to pass this at all. Pass it explicitly
+  // only when a caller's own reading needs to differ from the ambient one (e.g. a fading dual-zone
+  // layout whose panel content deliberately lags the live reading behind a transition). Correctness
+  // matters here regardless of source: measureInWindow reports the trigger's PRE-rotation layout
+  // position (see useAutoAlign's own doc comment for why, and why it can't recover this any other
+  // way), so a wrong rotation value picks an alignment for where the trigger *used to be* before
+  // rotating, clipping off the edge it's actually now near instead of the one it was near.
+  rotation?: PopoverRotation
   // Whether picking a value in a *single-select* section closes the popover. Defaults to true
   // (the old, pre-press-away default: pick one thing, you're done). Multi-select rows never
   // auto-close regardless of this — see MultiSelectSection's own comment. Worth setting false for a
@@ -116,7 +128,9 @@ interface Props {
 // powerups are enabled, say) is just this with one 'multi' section (optionally with allClear); a
 // combined menu (e.g. spawn frequency + which types, in one menu) is just two sections in the same
 // array.
-export function SectionedDropdown({ id, host, icon, accessibilityLabel, sections, accentColor, mutedColor, onAccentColor, dark, align: alignOverride, autoDismiss = true, labelFontFamily = MONO_FONT, allClearLabels = { all: 'All', clear: 'Clear' } }: Props) {
+export function SectionedDropdown({ id, host, icon, accessibilityLabel, sections, accentColor, mutedColor, onAccentColor, dark, align: alignOverride, rotation: rotationOverride, autoDismiss = true, labelFontFamily = MONO_FONT, allClearLabels = { all: 'All', clear: 'Clear' } }: Props) {
+  const ambientRotation = useRotation()
+  const rotation = rotationOverride ?? ambientRotation
   const menuBg = dark ? '#000000' : '#FFFFFF'
   // mutedColor is translucent (fine for the icon/text tints below, each a single paint), but the
   // caret is deliberately drawn overlapping the box's own top border (PopoverBody's CARET_DIP,
@@ -142,7 +156,7 @@ export function SectionedDropdown({ id, host, icon, accessibilityLabel, sections
       const divider = sectionIndex > 0 ? MENU_DIVIDER_HEIGHT : 0
       return sum + rows + footer + divider
     }, 0)
-  const { align: autoAlign, maxHeight, measured, triggerRef, verticalAlign } = useAutoAlign(open, MENU_MAX_WIDTH, estimatedHeight)
+  const { align: autoAlign, maxHeight, measured, triggerRef, verticalAlign } = useAutoAlign(open, MENU_MAX_WIDTH, estimatedHeight, rotation)
   const align = alignOverride ?? autoAlign
 
   // Trigger reflects the selected option's own icon only when there's exactly one section and it's

package/src/SkiaGate.tsx

@@ -0,0 +1,45 @@
+import type { ComponentType, ReactNode } from 'react'
+import { useEffect, useState } from 'react'
+
+export interface SkiaGateProps<P extends object> {
+  // A dynamic import, e.g. `() => import('./Board')` — hoist to module scope at the call site
+  // (never an inline closure written directly in JSX) so its identity stays stable across
+  // renders; it's this component's own useEffect dependency below.
+  getComponent: () => Promise<{ default: ComponentType<P> }>
+  componentProps: P
+  // Rendered while getComponent()'s promise is still pending. Defaults to null.
+  fallback?: ReactNode
+}
+
+// Native Skia renders through JSI — no WASM/CanvasKit fetch to wait on — so this file just
+// lazily mounts whatever getComponent() resolves to, once it resolves. The .web.tsx sibling
+// (picked by Metro/webpack's own platform-extension resolution for web bundles) is a different
+// implementation entirely: a direct re-export of @shopify/react-native-skia's own WithSkiaWeb,
+// which gates the same mount behind LoadSkiaWeb() first — CanvasKit's WASM build has to actually
+// finish loading before anything that imports '@shopify/react-native-skia' can evaluate its own
+// top-level `Skia` binding without crashing (see loadSkiaWeb.web.ts's own comment).
+//
+// No React.lazy()/Suspense here, deliberately: lazy() can't be called inline during render
+// (react-hooks/static-components — a getComponent prop that isn't referentially stable would
+// give a new component identity, and therefore an unwanted remount, on every render that passes
+// a fresh one) and can't be cached in a ref either (react-hooks/refs forbids reading or writing
+// ref.current during render, only inside an effect). Awaiting the import directly and setting
+// state from the resolved module sidesteps both — setState only ever runs from the promise
+// callback, never synchronously in render or in the effect body itself.
+export function SkiaGate<P extends object>({ getComponent, componentProps, fallback = null }: SkiaGateProps<P>) {
+  const [Component, setComponent] = useState<ComponentType<P> | null>(null)
+
+  useEffect(() => {
+    let cancelled = false
+    getComponent().then((mod) => {
+      if (!cancelled) setComponent(() => mod.default)
+    })
+    return () => {
+      cancelled = true
+    }
+  }, [getComponent])
+
+  if (!Component) return fallback
+
+  return <Component {...componentProps} />
+}

package/src/SkiaGate.web.tsx

@@ -0,0 +1,9 @@
+// Web needs CanvasKit's WASM loaded before any Skia <Canvas> evaluates — see loadSkiaWeb.web.ts's
+// own comment for why a plain useEffect-based loader can't fix this (it's a module-evaluation-
+// order problem, not a component-lifecycle one). Only this file (picked by Metro/webpack's
+// platform-extension resolution for web bundles) may import from
+// '@shopify/react-native-skia/src/web' — a static import of that subpath from a native-reachable
+// file pulls canvaskit-wasm's `require('fs')` into the native bundle and breaks iOS/Android
+// builds; this file vs. SkiaGate.tsx is what actually keeps it out, the same split
+// loadSkiaWeb.web.ts/loadSkiaWeb.ts already use.
+export { WithSkiaWeb as SkiaGate } from '@shopify/react-native-skia/src/web'

package/src/TriggerGaugeHost.tsx

@@ -1,26 +1,18 @@
-import { lazy, Suspense } from 'react'
-
-import { loadSkiaWeb } from './loadSkiaWeb'
+import { SkiaGate } from './SkiaGate'
 import { TriggerGaugeProps } from './TriggerGauge'
 
 // TriggerGauge.tsx's `Skia` import binds to global.CanvasKit at module-evaluation time, which on web
-// only exists once loadSkiaWeb()'s WASM fetch resolves (see that file's own comment) — a plain
-// `import { TriggerGauge } from './TriggerGauge'` at the top of this file would already have
-// evaluated that binding, against a not-yet-loaded, undefined CanvasKit, before anything in a
-// consuming app renders at all, since bundlers evaluate the whole static import graph up front. This
-// file therefore never imports TriggerGauge itself except as a type (erased at compile time,
-// carrying no runtime module reference) — `lazy()` is what actually defers the real import to
-// runtime, after loadSkiaWeb() resolves. Always lazy, on every platform, rather than a native/web
-// branch here, purely to keep this file simple — loadSkiaWeb() itself already resolves immediately
-// on native (see its own file split), so the Suspense boundary there just clears on the next tick,
-// not a perceptible delay. The Suspense fallback renders nothing, so a
-// consumer's trigger icon still shows immediately and the gauge ring just pops in a beat later.
-const LazyTriggerGauge = lazy(() => loadSkiaWeb().then(() => import('./TriggerGauge').then((m) => ({ default: m.TriggerGauge }))))
+// only exists once CanvasKit's WASM fetch resolves — a plain `import { TriggerGauge } from
+// './TriggerGauge'` at the top of this file would already have evaluated that binding, against a
+// not-yet-loaded, undefined CanvasKit, before anything in a consuming app renders at all, since
+// bundlers evaluate the whole static import graph up front. This file therefore never imports
+// TriggerGauge itself except as a type (erased at compile time, carrying no runtime module
+// reference) — getTriggerGauge below, hoisted to module scope so its identity stays stable across
+// renders (see SkiaGate's own comment on why that matters), is what actually defers the real import
+// to runtime. No explicit loadSkiaWeb() call here on web: SkiaGate.web.tsx (WithSkiaWeb) already
+// gates its own mount behind CanvasKit being ready, and on native there's nothing to wait on at all.
+const getTriggerGauge = () => import('./TriggerGauge').then((mod) => ({ default: mod.TriggerGauge }))
 
 export default function TriggerGaugeHost(props: TriggerGaugeProps) {
-  return (
-    <Suspense fallback={null}>
-      <LazyTriggerGauge {...props} />
-    </Suspense>
-  )
+  return <SkiaGate getComponent={getTriggerGauge} componentProps={props} />
 }