Status of preventShadowTreeCommitExhaustion and its Reanimated pairing (DISABLE_COMMIT_PAUSING_MECHANISM)

[alexnaiman]

Hi, I'd like to get a clearer picture on the current status and roadmap of the preventShadowTreeCommitExhaustion feature flag.

We're seeing scroll jitter on animated components with the New Architecture enabled, and Reanimated's performance docs point to preventShadowTreeCommitExhaustion (RN side) paired with DISABLE_COMMIT_PAUSING_MECHANISM (Reanimated side) as the main fix.

The feature flags docs recommend enabling preventShadowTreeCommitExhaustion via a patch to ReactNativeFeatureFlagsDefaults.h and building React Native from source, rather than setting reactNativeReleaseLevel to experimental (which pulls in unrelated flags). They also note this will ultimately be addressed by a Fabric commit branching mechanism, which landed in RN 0.85 behind its own feature flag (facebook/react-native#54835).

This same patch-based workaround is also referenced in reanimated#6992 (sticky header flickering with useAnimatedScrollHandler), and prior discussion in reanimated#8950 (Feb 2026) touches on the same topic.

Questions:

1. Is the preventShadowTreeCommitExhaustion patch + build-from-source approach considered safe for production apps today?
2. Is the Fabric commit branching mechanism from #54835 meant to eventually replace the need for this patch, and if so, is there a rough timeline for it becoming the default?
3. Once that mechanism stabilizes, would preventShadowTreeCommitExhaustion still be relevant, or does it become redundant?

Thanks!