[Android | iOS] Add borderRadius to mentions in chat

patches/react-native/details.md

@@ -271,13 +271,6 @@
 - Upstream PR/issue: [facebook/react-native#55398](https://github.com/facebook/react-native/pull/55398)
 - E/App issue: [#90623](https://github.com/Expensify/App/issues/90623)
 
-### [react-native+0.83.1+036+rounded-inline-code-background.patch](react-native+0.83.1+036+rounded-inline-code-background.patch)
-
-- Reason: Draws inline code block background with rounded corners on iOS when `borderTopLeftRadius` is set.
-- Upstream PR/issue: 🛑
-- E/App issue: https://github.com/Expensify/App/issues/57556
-- PR introducing patch: https://github.com/Expensify/App/pull/79815
-
 ### [react-native+0.83.1+037+fix-deadlock-APP-7B2.patch](react-native+0.83.1+037+fix-deadlock-APP-7B2.patch)
 
 - Reason: Fixes a fatal iOS app hang (APP-7B2) caused by a deadlock in Fabric's `ComponentDescriptorRegistry`. During HybridApp OldDot->NewDot transitions, a background thread lazily registering legacy interop component descriptors via `ComponentDescriptorRegistry::add()` holds a `unique_lock(mutex_)` while constructing a descriptor that calls `RCTUnsafeExecuteOnMainQueueSync`. Simultaneously, the main thread (driven by `CADisplayLink` animation ticks) tries to acquire `shared_lock(mutex_)` in `findComponentDescriptorByHandle_DO_NOT_USE_THIS_IS_BROKEN`. This creates a circular dependency: main waits for the lock, background waits for main. The fix moves descriptor construction outside the `unique_lock`, so the lock is only held for the two map insertions.
@@ -291,4 +284,24 @@
 - Reason: Fixes a fatal iOS crash (APP-8BM) in HybridApp where `RCTNetworking`'s default URL-request-handler provider builds its handler list using an Objective-C array literal (`@[...]`) with `[moduleRegistry moduleForName:"BlobModule"]` at index 3. During OldDot↔NewDot bridge transitions, the `__weak _turboModuleRegistry` in `RCTModuleRegistry` is zeroed by ARC at the start of `TurboModuleManager` dealloc — before `[RCTNetworking invalidate]` clears the handler cache — leaving a window where a concurrent in-flight network request calls `prioritizedHandlers`, finds the cache empty, and tries to rebuild it with a nil `BlobModule`. Since `@[…]` compiles to `+[NSArray arrayWithObjects:count:]` which raises `NSInvalidArgumentException` on any nil element, the crash is fatal. The fix replaces the literal with an `NSMutableArray` built from the three always-non-nil handlers (`RCTHTTPRequestHandler`, `RCTDataRequestHandler`, `RCTFileRequestHandler`) and conditionally appends `BlobModule` only when the registry lookup is non-nil, turning a guaranteed crash into a graceful "no blob handler for this window".
 - Upstream PR/issue: 🛑
 - E/App issue: https://github.com/Expensify/App/issues/92413
-- PR introducing patch: https://github.com/Expensify/App/pull/92918
+- PR introducing patch: https://github.com/Expensify/App/pull/92918
+
+### [react-native+0.83.1+039+nested-text-border-radius.patch](react-native+0.83.1+039+nested-text-border-radius.patch)
+
+- Reason:
+
+    ```
+    Adds borderRadius / per-corner radius support for nested <Text> backgrounds on iOS and Android.
+    On the C++ side, borderRadius + borderTopLeftRadius / borderTopRightRadius /
+    borderBottomLeftRadius / borderBottomRightRadius fields are added to TextAttributes and wired
+    through BaseTextProps and conversions. borderRadius acts as a fallback for unset individual
+    corners; unset corners default to 0 when any radius prop is present. On Android, a custom
+    DrawCommandSpan with ReactBackgroundDrawSpan draws rounded-rect backgrounds using the four
+    effective corner radii. On iOS, a custom NSLayoutManager subclass
+    (RCTTextLayoutManagerWithBorderRadius) overrides fillBackgroundRectArray to draw per-corner
+    rounded rectangles using CGPath, with per-line outer-corner rounding for multiline spans.
+    ```
+
+- Upstream PR/issue: 🛑
+- E/App issue: https://github.com/Expensify/App/issues/78873
+- PR introducing patch: https://github.com/Expensify/App/pull/84556