Fabric and TurboModules New Architecture opt-in leaves legacy bridge deprecation timeline unresolved

React Native projects can enable Fabric renderer and TurboModules via configuration, which changes native module loading semantics compared with the legacy Paper renderer and bridge.

The framework continues to maintain both code paths, and recent releases have shifted Hermes to default while New Architecture remains opt-in. This creates a compatibility boundary for libraries that still target the old bridge.

Without a published removal date for Paper and the legacy bridge, teams face uncertainty about investment in TurboModules migration versus maintaining dual implementations.

What is the current documented default for Fabric and TurboModules in the latest stable React Native release? Is there an official deprecation schedule for the legacy bridge and Paper renderer? How should library authors decide between supporting only TurboModules or maintaining dual bridge compatibility?