@scalebun/react-native 2.0.0 → 2.0.2

package/src/features/journey/ScaleBunDebugRoot.tsx

@@ -28,12 +28,15 @@ import React, {
     type ReactNode,
 } from 'react';
 import { View, NativeEventEmitter, NativeModules } from 'react-native';
-import { resolveTouchTarget, describeTouchTarget } from './touchTarget';
+import { resolveTouchTarget, describeTouchTarget, targetIdentity } from './touchTarget';
+import { localPoint, normalizeRect, readRectSync, type NormalizedRect } from './targetGeometry';
+import { nativeTagOf, nearestRecordedOffset } from './scrollContext';
 import { resolvePlatformOS } from '../../core/context/device';
 import {
     INTERACTION_PROTOCOL_VERSION,
     generateInteractionId,
-    nearestInteractionStart,
+    correlateInteraction,
+    pruneInteractionStarts,
     type InteractionStartContext,
 } from './interactionProtocol';
 
@@ -53,6 +56,15 @@ function getBootstrap() {
 
 const JourneyContext = createContext<any>(null);
 
+/**
+ * Floor on how often a UI-state change may request a screenshot.
+ *
+ * One frame per second is far finer than any state a person perceives changing, and far coarser
+ * than a render loop — which is the case that matters, because a host may legitimately declare
+ * state from inside render and an oscillating dimension would otherwise capture continuously.
+ */
+const UI_STATE_CAPTURE_MIN_INTERVAL_MS = 1000;
+
 // ─── ScaleBunDebugRoot ───────────────────────────────────────────────────────────
 
 interface ScaleBunDebugRootProps {
@@ -275,6 +287,50 @@ export function ScaleBunDebugRoot({
         };
     }, [navigationRef]);
 
+    /**
+     * RN-11 — CAPTURE A FRAME WHEN THE UI CHANGES SHAPE.
+     *
+     * A declared state used to have no picture of its own. Nothing captured on `setUiState`, so a
+     * state's visual existed only if a screenshot happened to be taken for another reason — a
+     * navigation, a timer, or the interaction capture that fires AFTER the touch and therefore
+     * photographs the outcome. A drawer could be recorded as open with no frame showing it open,
+     * or with the frame of the screen that replaced it.
+     *
+     * The native capture reasons are NAVIGATION, MANUAL, INTERACTION and TIMER; none of them means
+     * "the UI changed shape". This routes through the MANUAL path, which is the only one reachable
+     * from JS. A dedicated native reason would let the backend tell a state capture from a
+     * developer-requested one, and that is a native change on both platforms — worth doing, not
+     * doable from here.
+     *
+     * RATE LIMITED, and the limit is not politeness. A screenshot is expensive, and while
+     * `uiState` already collapses redundant declarations, a genuinely oscillating dimension (a
+     * spinner toggling, a live-updating badge) would otherwise capture continuously. One frame per
+     * second is far finer than any state a person can perceive changing and far coarser than a
+     * render loop.
+     *
+     * Requests only; never awaits and never throws. If the session is not recording,
+     * `captureManualFrame` declines and the state simply has no frame — which is the honest
+     * outcome and is exactly what the analytics-only lane already reports elsewhere.
+     */
+    useEffect(() => {
+        let lastCaptureTs = 0;
+        const { onUiStateChange } = require('./uiState');
+        const unsubscribe = onUiStateChange(() => {
+            const now = Date.now();
+            if (now - lastCaptureTs < UI_STATE_CAPTURE_MIN_INTERVAL_MS) return;
+            lastCaptureTs = now;
+            try {
+                const { SessionManager } = require('../session/SessionManager');
+                const sm = SessionManager.getExistingInstance();
+                if (sm && typeof (sm as any).captureManualFrame === 'function') {
+                    /* Fire and forget: the tap that follows must not wait on a screenshot. */
+                    void (sm as any).captureManualFrame();
+                }
+            } catch { /* no-throw */ }
+        });
+        return unsubscribe;
+    }, []);
+
     // ─── Native Interaction Listener ────────────────────────────────────
     // Receives high-confidence ScaleBunNativeInteraction events from the native tracker
     // and forwards them to SessionManager as USER_ACTION events.
@@ -301,7 +357,30 @@ export function ScaleBunDebugRoot({
                             ? event.occurredAt
                             : (typeof event.timestamp === 'number' ? event.timestamp : Date.now()) -
                               (typeof event.durationMs === 'number' ? event.durationMs : 0);
-                    const start = nearestInteractionStart(interactionStartsRef.current, nativeOccurredAt);
+                    /**
+                     * RN-6 — correlate, then CONSUME. See interactionProtocol.ts for why
+                     * the join is on time at all, and why a refusal is the important part.
+                     *
+                     * Pruning first is part of the correctness, not tidying: a start older
+                     * than the tolerance can never be paired, but while it sits in the list
+                     * it is still counted by the ambiguity test, so a stale entry can turn a
+                     * clear pairing into a refusal — and the list only grows.
+                     */
+                    pruneInteractionStarts(interactionStartsRef.current, nativeOccurredAt);
+                    const correlation = correlateInteraction(
+                        interactionStartsRef.current,
+                        nativeOccurredAt,
+                    );
+                    const start = correlation.start;
+                    /**
+                     * ONE-TO-ONE. Without removing the matched start, a second native event
+                     * arriving within the window claims the SAME js evidence, so one tap's
+                     * target is stamped onto another tap that never had one — a duplicate
+                     * identity that reads as two genuine interactions on the same control.
+                     */
+                    if (correlation.index >= 0) {
+                        interactionStartsRef.current.splice(correlation.index, 1);
+                    }
 
                     // Cancel only this physical touch's fallback. A single timer used to cancel a
                     // previous rapid tap and silently lose it on devices without native tracking.
@@ -330,11 +409,63 @@ export function ScaleBunDebugRoot({
                         interactionId: event.interactionId || start?.interactionId || generateInteractionId(),
                         interactionProtocol: event.interactionProtocol || INTERACTION_PROTOCOL_VERSION,
                         occurredAt: nativeOccurredAt,
+                        /**
+                         * RN-6 — THESE FIVE FIELDS ARE THE ONLY ONES THE JOIN CARRIES, AND
+                         * THEREFORE THE ONLY ONES A BAD JOIN CAN FALSIFY.
+                         *
+                         * Coordinates below come from native and are right regardless. So a
+                         * mispairing does not produce visibly broken data: it produces heat
+                         * in the correct position attributed to the wrong control, in the
+                         * wrong UI state, on the wrong screen. Every field is individually
+                         * well-formed and nothing downstream can tell.
+                         *
+                         * When the correlation is not 'exact' they are left UNDEFINED rather
+                         * than filled from a best guess. An interaction with no target is
+                         * honest and visibly incomplete — the accounting lane can count it as
+                         * unplaceable and say why. An interaction with the WRONG target is
+                         * indistinguishable from a correct one and silently corrupts every
+                         * aggregate it enters. `null` is not `0`, and a guess is not a
+                         * measurement.
+                         */
                         ui: start?.ui,
                         stateStatus: start?.stateStatus ?? 'not_captured',
                         target: start?.target,
                         targetId: start?.targetId,
+                        targetSource: start?.targetSource,
                         screenName: start?.screenName,
+                        screenSource: start?.screenSource ?? 'none',
+                        targetRect: start?.targetRect,
+                        /**
+                         * RN-15 — WHERE IN THE CONTROL, computed where both halves exist: the
+                         * point comes from the native event and the rect was measured at
+                         * finger-down, in the same capture base. Pairing them here rather than
+                         * downstream stops anything later reaching for a different rect.
+                         */
+                        ...(() => {
+                            const lp = localPoint(
+                                start?.targetRect ?? null,
+                                event.normalizedX,
+                                event.normalizedY,
+                            );
+                            return lp ? { localU: lp.u, localV: lp.v } : {};
+                        })(),
+                        scrollX: start?.scrollX,
+                        scrollY: start?.scrollY,
+                        scrollSource: start?.scrollSource ?? 'none',
+                        itemKey: start?.itemKey,
+                        itemIndex: start?.itemIndex,
+                        /**
+                         * The join's own verdict, shipped with the row so it is auditable
+                         * rather than a claim made in a comment. 'ambiguous' and 'none' are
+                         * deliberately distinguished: 'none' means the JS handler never fired
+                         * (a real capture gap on this platform), 'ambiguous' means it fired
+                         * more than once too close together to attribute. Those have
+                         * different fixes, and collapsing them would hide which one is
+                         * actually happening in production.
+                         */
+                        correlation: correlation.outcome,
+                        correlationDeltaMs: correlation.deltaMs,
+                        correlationRunnerUpDeltaMs: correlation.runnerUpDeltaMs,
                         emitAutomaticAnalytics: start?.emitAutomaticAnalytics ?? captureAutomaticInteractions,
                         x: event.rawX,
                         y: event.rawY,
@@ -411,13 +542,28 @@ export function ScaleBunDebugRoot({
             const target = resolveTouchTarget(e);
             let ui: string | undefined;
             let screenName: string | undefined;
+            /**
+             * RN-8 — WHERE the screen name came from, carried with the interaction.
+             *
+             * Production shows 13.8% of Android interactions with a screen and 0.5% on iOS, and
+             * those figures cannot distinguish three unrelated causes: nothing was instrumented,
+             * a manual beacon was instrumented but never reached interactions, or auto-detection
+             * ran and failed. Each has a different owner. Recording the source turns one
+             * unactionable percentage into three answerable ones.
+             */
+            let screenSource: 'manual' | 'navigation' | 'none' = 'none';
             try {
                 const { uiStateSignature } = require('./uiState');
                 ui = uiStateSignature();
             } catch { /* no-throw */ }
             try {
                 const { AutoScreenDetector } = require('../navigation/AutoScreenDetector');
-                screenName = AutoScreenDetector.getInstance().getCurrentScreen() || undefined;
+                const detector = AutoScreenDetector.getInstance();
+                screenName = detector.getCurrentScreen() || undefined;
+                /* Read from the SAME call site as the name, so the two can never describe
+                   different moments — the detector is polled and its answer can change between
+                   two reads a few milliseconds apart. */
+                screenSource = screenName ? detector.getCurrentScreenSource() : 'none';
             } catch { /* no-throw */ }
             const start: TouchStartContext = {
                 interactionId: generateInteractionId(),
@@ -426,9 +572,88 @@ export function ScaleBunDebugRoot({
                 y: touch.pageY,
                 locationX: touch.locationX,
                 locationY: touch.locationY,
+                /**
+                 * RN-1 + RN-2 — the identity that is persisted, and it is now code-derived.
+                 *
+                 * `describeTouchTarget` returns `testID` -> structural path -> component name,
+                 * and never a caption or an accessibilityLabel. Before RN-2 it preferred free
+                 * text, so this line was writing user data ("Pay EGP 1,442", an order row
+                 * labelled with an email address, a contact's name) into the analytics store —
+                 * and, because `target` is an aggregation key, splitting one button into one
+                 * bucket per person at the same time.
+                 *
+                 * `targetId` used to be `target?.testID` alone, which is `undefined` in the
+                 * overwhelming majority of apps — no testIDs authored — so the field the
+                 * backend keys on was empty almost always. It now falls back to the structural
+                 * path, with `targetSource` recording WHICH it got.
+                 */
                 target: describeTouchTarget(target),
-                targetId: target?.testID,
+                targetId: targetIdentity(target).id,
+                /**
+                 * WHICH KIND of identity this is, because they are not equally trustworthy: a
+                 * `testID` is a promise from the app's authors that this control is this
+                 * control; a `path` is an inference that breaks when the tree is refactored.
+                 * Without this the accounting lane cannot distinguish "the control had no
+                 * identity" from "the identity is a structural guess", and both would render
+                 * as an equally confident target.
+                 */
+                targetSource: targetIdentity(target).source,
+                /* RN-4 — row identity from the app's own keyExtractor; see touchTarget.ts. */
+                itemKey: target?.itemKey,
+                itemIndex: target?.itemIndex,
+                /**
+                 * RN-13 — the control's rectangle, so `heat ∈ target` is decidable.
+                 *
+                 * Read SYNCHRONOUSLY here, in the same tick as the touch, and normalized against
+                 * the SAME measured root the tap's own coordinates use. Both halves matter:
+                 *
+                 *   - A callback measurement (`measureInWindow`) would resolve after this handler
+                 *     returns, so the rect attached to a tap could be the previous tap's, with
+                 *     nothing afterwards able to tell. `targetGeometry` refuses to guess: it reads
+                 *     now or reports null.
+                 *   - Normalizing against a window size instead of the root view is off by the
+                 *     status bar on most devices, which would read as "the heat is just outside
+                 *     the button" everywhere rather than as a measurement bug.
+                 *
+                 * `measureRoot()` is called first because the cached root rect is populated
+                 * asynchronously at mount; without it the first taps of a session normalize
+                 * against nothing and get a null rect for a reason that has nothing to do with
+                 * the control.
+                 */
+                /**
+                 * RN-3 — WHERE IN THE CONTENT, not just where on the glass.
+                 *
+                 * Two taps at the same screen coordinate one viewport apart are two different
+                 * controls. Without an offset they merge into one hotspot, and the heatmap shows
+                 * heavy engagement at a position where, in content terms, nothing in particular
+                 * is. The offset is also a CACHE dimension — two scroll states of one route must
+                 * not share a backdrop — so its absence corrupts the picture as well as the count.
+                 *
+                 * `ancestors` is innermost-first, so this takes the NEAREST scroller that has a
+                 * recorded position: a tap inside a horizontal carousel belongs to the carousel's
+                 * content, not to how far the page behind it had scrolled.
+                 *
+                 * Null when no ancestor has one — never zero. Zero is a real scroll position (the
+                 * top of a list), and reporting it for "unknown" would place every unmeasured tap
+                 * at the top of its content, indistinguishable from a genuine tap there.
+                 */
+                ...(() => {
+                    const hit = nearestRecordedOffset(
+                        (target?.ancestors ?? []).map((n) => nativeTagOf(n)),
+                    );
+                    return hit
+                        ? { scrollX: hit.x, scrollY: hit.y, scrollSource: 'wrapper' as const }
+                        : { scrollSource: 'none' as const };
+                })(),
+                targetRect: (() => {
+                    measureRoot();
+                    const root = rootRectRef.current;
+                    /* null -> undefined: the context field is optional, and an explicit null would
+                       serialise as a JSON null claiming "measured, and it was nothing". */
+                    return normalizeRect(readRectSync(target?.node), root ? { w: root.w, h: root.h } : null) ?? undefined;
+                })(),
                 screenName,
+                screenSource,
                 ui,
                 stateStatus: ui ? 'captured_nonempty' : 'not_instrumented',
                 emitAutomaticAnalytics: captureAutomaticInteractions,
@@ -473,7 +698,20 @@ export function ScaleBunDebugRoot({
             // WHAT was tapped, resolved from the React fiber on the touch event. Without this the tap
             // carries only coordinates, so every tap in the app groups into one row per gesture type.
             // Defensive by construction — returns undefined rather than throwing (see touchTarget.ts).
-            const tapped = start?.target ?? describeTouchTarget(resolveTouchTarget(e));
+            /**
+             * Resolved ONCE, so `target` and `targetId` cannot disagree about the same tap.
+             *
+             * The previous shape called `resolveTouchTarget(e)` inline for `target` while
+             * `targetId` came only from `start` — so on the fallback path (no JS start, or a
+             * refused correlation) the tap carried a description with NO id, and the two fields
+             * were computed from different sources. Anything joining on `targetId` therefore
+             * saw nothing for a tap that visibly had a target.
+             */
+            const freshTarget = start ? null : resolveTouchTarget(e);
+            const tapped = start?.target ?? describeTouchTarget(freshTarget);
+            const identity = start
+                ? { id: start.targetId, source: start.targetSource }
+                : targetIdentity(freshTarget);
 
             const gestureDetails: any = {
                 target: tapped,
@@ -482,8 +720,16 @@ export function ScaleBunDebugRoot({
                 occurredAt: start?.occurredAt ?? Date.now(),
                 ui: start?.ui,
                 stateStatus: start?.stateStatus ?? 'not_captured',
-                targetId: start?.targetId,
+                targetId: identity.id,
+                targetSource: identity.source,
                 screenName: start?.screenName,
+                screenSource: start?.screenSource ?? 'none',
+                targetRect: start?.targetRect,
+                scrollX: start?.scrollX,
+                scrollY: start?.scrollY,
+                scrollSource: start?.scrollSource ?? 'none',
+                itemKey: start?.itemKey,
+                itemIndex: start?.itemIndex,
                 emitAutomaticAnalytics: start?.emitAutomaticAnalytics ?? captureAutomaticInteractions,
                 x: start?.x ?? touch.pageX,
                 y: start?.y ?? touch.pageY,
@@ -506,6 +752,19 @@ export function ScaleBunDebugRoot({
                 const ny = Math.max(0, Math.min(1, (start?.y ?? touch.pageY) / rootRect.h));
                 gestureDetails.normalizedX = nx;
                 gestureDetails.normalizedY = ny;
+                /**
+                 * RN-15 on the JS-fallback lane.
+                 *
+                 * Computed here rather than in the literal above because that is where nx/ny first
+                 * exist. The rect is the SAME one the native lane uses, so one physical tap yields
+                 * the same local position whichever lane captured it — two lanes disagreeing about
+                 * where in a control a tap landed would be worse than neither reporting it.
+                 */
+                const lp = localPoint(start?.targetRect ?? null, nx, ny);
+                if (lp) {
+                    gestureDetails.localU = lp.u;
+                    gestureDetails.localV = lp.v;
+                }
                 gestureDetails.normalizedPrecomputed = true;
                 gestureDetails.viewportWidth = rootRect.w;
                 gestureDetails.viewportHeight = rootRect.h;
@@ -695,6 +954,28 @@ export function useScaleBunScreen(name: string): void {
             }
         } catch { /* no-throw */ }
 
+        /**
+         * RN-8 — TELL THE DETECTOR TOO, because interactions read their screen from IT.
+         *
+         * This hook fed SessionManager, PerformanceFeature, ProfilerFeature and JourneyManager
+         * — four consumers — and never `AutoScreenDetector`. But `handleTouchStart` resolves an
+         * interaction's `screenName` from `AutoScreenDetector.getCurrentScreen()`, so a
+         * manually-instrumented app produced perfectly-named SCREEN_VIEW events while every TAP
+         * carried no screen at all. `setManualScreen` existed and was called only by tests.
+         *
+         * That is the whole story for apps the auto-hook cannot help: expo-router, a custom
+         * navigator, anything not `@react-navigation/native`. The documented manual escape hatch
+         * did not reach the one field that partitions every heatmap.
+         *
+         * Requires the last-writer-wins fix in `_currentScreen()` to be useful: under the
+         * previous rule a manual screen was readable for only 2000 ms, so wiring this alone
+         * would have handed interactions a name that expired before most taps happened.
+         */
+        try {
+            const { AutoScreenDetector } = require('../navigation/AutoScreenDetector');
+            AutoScreenDetector.getInstance().setManualScreen(name);
+        } catch { /* no-throw */ }
+
         // Feed PerformanceFeature (screen context for perf metrics)
         // NOTE: Only sets screen identity. Does NOT call markScreenLoadStart/End.
         // AutoScreenLoadCollector handles timing independently via rAF + InteractionManager.

package/src/features/journey/ScaleBunScrollView.tsx

@@ -52,6 +52,35 @@ export const ScaleBunScrollView = React.forwardRef<ScrollView, ScrollViewProps>(
                     }
                 } catch { /* no-throw */ }
 
+                /**
+                 * RN-3 — record WHERE THIS scroller sits, keyed by its own native tag, so a later
+                 * tap can say which content was under the finger.
+                 *
+                 * OUTSIDE the `isActive` guard above, deliberately. That guard is correct for the
+                 * gesture tracker, which produces scroll EVENTS and should only do so while
+                 * recording. This is a different thing: it is the position a tap needs in order to
+                 * be placed in content rather than on glass, and a tap is captured on the always-on
+                 * analytics lane even when no recording is active. Gating this the same way would
+                 * make content depth absent in exactly the sessions the heatmap is built from.
+                 *
+                 * The tag is taken from the EVENT's target rather than from this component's ref,
+                 * so it identifies the scroller that actually moved. With nested scrollers the
+                 * event may come from an inner one, and keying by the wrapper would file the
+                 * carousel's offset under the list.
+                 */
+                try {
+                    const { recordScrollOffset, nativeTagOf } = require('./scrollContext');
+                    const { contentOffset, target } = event.nativeEvent as unknown as {
+                        contentOffset: { x: number; y: number };
+                        target?: unknown;
+                    };
+                    recordScrollOffset(
+                        typeof target === 'number' ? target : nativeTagOf(target),
+                        contentOffset.x,
+                        contentOffset.y,
+                    );
+                } catch { /* no-throw */ }
+
                 // Forward to user's onScroll handler
                 if (userOnScroll) {
                     userOnScroll(event);

package/src/features/journey/autoInstrumentScroll.ts

@@ -0,0 +1,155 @@
+import { nativeTagOf, recordScrollOffset } from './scrollContext';
+
+/**
+ * RN-3, ZERO-CONFIG — make every ScrollView report its offset, not just the wrapped ones.
+ *
+ * THE PROBLEM THIS SOLVES. Scroll offsets reach the SDK from `ScaleBunScrollView` and nowhere
+ * else, so an app using React Native's own `<ScrollView>` — which is most apps — produces taps
+ * with no content depth at all. Two taps at the same screen coordinate one viewport apart then
+ * merge into one hotspot, and the heatmap shows heavy engagement at a position where, in content
+ * terms, nothing in particular is. Asking every integration to swap its scroll views is a real
+ * migration cost and will never reach the long tail.
+ *
+ * WHY IT IS OFF BY DEFAULT, and why that is not timidity. This patches React Native's own module
+ * exports. Every scroll view in the host app — including ones inside third-party libraries the
+ * app did not write — starts routing through an SDK component. The failure mode of getting that
+ * wrong is not a wrong number in a dashboard, it is the host's UI behaving differently because an
+ * analytics SDK replaced a primitive. That is a decision an integrator makes with their eyes open,
+ * not a default they discover afterwards.
+ *
+ * THE PRECEDENT, AND ITS LESSON. The SDK already patches `@react-navigation/native` this way
+ * (`AutoScreenDetector._autoHookReactNavigation`). That hook shipped BROKEN: it assigned to module
+ * exports that are getters, which throws in strict mode, inside a `catch` that discarded the
+ * error. It reported success, captured no ref, and the whole screen-name pipeline stayed empty
+ * with nothing to indicate it. So this uses the same defence that fixed it — define the property
+ * rather than assign to it, then READ IT BACK — and refuses to claim success it has not verified.
+ *
+ * WHAT IT DELIBERATELY DOES NOT PATCH. `FlatList` and `SectionList` render a `ScrollView`
+ * internally, so patching that one export covers them without touching three. Fewer patch points
+ * is fewer ways to be wrong, and RN-4's row identity comes off the fiber regardless of which
+ * component rendered it.
+ */
+
+interface PatchResult {
+  /** True only when the replacement was verified by reading it back. */
+  installed: boolean;
+  /** Why not, when it did not install — for a diagnostic the host can act on. */
+  reason?: string;
+}
+
+let alreadyPatched = false;
+
+/**
+ * Replace an export on a module whose exports are GETTERS.
+ *
+ * React Native's index is compiled re-exports, which bundlers emit as accessors with a getter and
+ * no setter. Plain assignment throws in strict mode and silently does nothing in sloppy mode.
+ * Defining the property works where assigning does not, and the read-back is what turns a future
+ * failure into a visible one instead of a silent no-op.
+ */
+function redefine(target: Record<string, unknown>, key: string, value: unknown): boolean {
+  try {
+    Object.defineProperty(target, key, {
+      configurable: true,
+      enumerable: true,
+      writable: true,
+      value,
+    });
+    return target[key] === value;
+  } catch {
+    return false;
+  }
+}
+
+/**
+ * Wrap a scroll component so its offsets are recorded, forwarding everything else untouched.
+ *
+ * The host's own `onScroll` is called AFTER the offset is recorded and is never replaced: an SDK
+ * that swallows a host's handler breaks the app, which is a far worse outcome than missing
+ * analytics. Recording first also means a throwing host handler cannot cost us the measurement.
+ */
+function instrument(Original: any, React: any): any {
+  const Wrapped = React.forwardRef((props: any, ref: unknown) => {
+    const onScroll = (event: any) => {
+      try {
+        const target = event?.nativeEvent?.target;
+        const offset = event?.nativeEvent?.contentOffset;
+        if (offset) {
+          recordScrollOffset(
+            typeof target === 'number' ? target : nativeTagOf(target),
+            offset.x,
+            offset.y,
+          );
+        }
+      } catch {
+        /* no-throw: a scroll offset is never worth breaking a gesture over */
+      }
+      try {
+        props?.onScroll?.(event);
+      } catch (e) {
+        /* The host's handler is the host's problem, but it must still run and still throw where
+           they can see it — rethrow on a later tick so this wrapper is not in the stack. */
+        setTimeout(() => {
+          throw e;
+        }, 0);
+      }
+    };
+    /**
+     * `scrollEventThrottle` defaults to 16 only when the host has not chosen one. Overriding a
+     * host's explicit value would change how often their own handler runs — a behaviour change
+     * for a measurement, which is exactly the trade this module is not allowed to make.
+     */
+    const throttle = props?.scrollEventThrottle ?? 16;
+    return React.createElement(Original, {
+      ...props,
+      scrollEventThrottle: throttle,
+      onScroll,
+      ref,
+    });
+  });
+  Wrapped.displayName = 'ScaleBunAutoScrollView';
+  return Wrapped;
+}
+
+/**
+ * Patch React Native's `ScrollView` export so every scroll view reports its offset.
+ *
+ * Idempotent, no-throw, and honest about failure: returns `installed: false` with a reason rather
+ * than claiming a success it did not verify.
+ */
+export function autoInstrumentScrollViews(): PatchResult {
+  if (alreadyPatched) return { installed: true };
+  try {
+    // eslint-disable-next-line @typescript-eslint/no-var-requires
+    const RN = require('react-native') as Record<string, unknown>;
+    // eslint-disable-next-line @typescript-eslint/no-var-requires
+    const React = require('react');
+    const Original = RN.ScrollView;
+    if (typeof Original !== 'function' && typeof Original !== 'object') {
+      return { installed: false, reason: 'react-native has no ScrollView export to wrap' };
+    }
+    if ((Original as { __scalebunInstrumented?: boolean }).__scalebunInstrumented) {
+      alreadyPatched = true;
+      return { installed: true };
+    }
+    const Wrapped = instrument(Original, React);
+    (Wrapped as { __scalebunInstrumented?: boolean }).__scalebunInstrumented = true;
+    if (!redefine(RN, 'ScrollView', Wrapped)) {
+      return {
+        installed: false,
+        reason:
+          "react-native's ScrollView export could not be replaced — it is a getter with no " +
+          'configurable descriptor on this bundler. Use ScaleBunScrollView explicitly instead.',
+      };
+    }
+    alreadyPatched = true;
+    return { installed: true };
+  } catch (e) {
+    return { installed: false, reason: (e as Error)?.message ?? 'unknown failure' };
+  }
+}
+
+/** Test seam: forget that the patch ran, so a suite can exercise it more than once. */
+export function resetAutoInstrumentForTests(): void {
+  alreadyPatched = false;
+}