fix(native): retain keyed controls and correct map and tab chrome

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-navigation/NativeNavigationUnitTests.swiftmodified+9-0

Changes to packages/ios/fixtures/native-navigation/NativeNavigationUnitTests.swift

		⋯434 linesShow the 434 lines above this hunk@@ -435,6 +435,15 @@ final class NativeNavigationUnitTests: XCTestCase {
435	435	await renderFrames()
436	436	XCTAssertEqual(CraftChrome.shared.selected, "/")
437	437	XCTAssertEqual(CraftChrome.shared.tabAccessory?.id, "/capabilities")
	438	+
	439	+ let background = try XCTUnwrap(stack("/details"))
	440	+ XCTAssertTrue(background.view.isHidden)
	441	+ let prepared = try XCTUnwrap(background.topViewController as? CraftNativeScreenController)
	442	+ // UIKit can deliver the prepared tab's first appearance after the
	443	+ // foreground push has finished. That callback must not claim chrome.
	444	+ prepared.viewDidAppear(false)
	445	+ XCTAssertEqual(CraftChrome.shared.tabAccessory?.id, "/capabilities")
	446	+ XCTAssertEqual(CraftChrome.shared.selected, "/")
438	447	}
439	448
440	449	func testDisappearingHiddenNativeTabCannotClearTheVisibleAccessory() async throws {