fix(mobile): preserve native editing, navigation, and durable media requests

Review threads live on the whole diff, not on one commit, so none are shown here - a thread's line means something in the branch's final form, and painting it into an intermediate step would put it on code it is not about.

packages/ios/fixtures/native-screen/NativeRenderUITests.swiftmodified+8-1

Changes to packages/ios/fixtures/native-screen/NativeRenderUITests.swift

		⋯38 linesShow the 38 lines above this hunk@@ -39,7 +39,14 @@ final class NativeRenderUITests: XCTestCase {
39	39	notes.tap()
40	40	XCTAssertTrue(keyboardIsVisible(app))
41	41	notes.typeText("Easy run")
42		- XCTAssertEqual(app.staticTexts["notes"].label, "Notes: Easy run")
	42	+ // Read the original acknowledgement first: inspecting other UIKit
	43	+ // elements must not hide a delayed bridge update from this assertion.
	44	+ let acknowledgement = app.staticTexts["notes"].label
	45	+ let typedValue = notes.value as? String
	46	+ let keyboardVisible = app.keyboards.firstMatch.exists
	47	+ XCTAssertEqual(typedValue, "Easy run", "the native text view lost typed characters")
	48	+ XCTAssertTrue(keyboardVisible, "typing dismissed the native keyboard")
	49	+ XCTAssertEqual(acknowledgement, "Notes: Easy run", "native value: \(typedValue ?? "nil"), keyboard visible: \(keyboardVisible)")
43	50	}
44	51
45	52	func testSwitchTapChangesUIKitStateAndDeliversValueChange() throws {