fix(mobile): Android Files sheet scrolls its tree instead of dragging the sheet#33223

Problem

On Android, the thread Files bottom sheet ignores swipes on its file tree. Swipes move the whole sheet instead, so entries below the visible area cannot be reached by touch scrolling.

Closes https://github.com/pingdotgg/t3code/issues/33224

Change

• inspector-host.android.tsx gives the visible pane the lower zIndex. React Native orders native siblings by zIndex, so the visible pane comes first in native child order. Hidden panes remain transparent, excluded from accessibility, and pointerEvents="none".
• thread-file-navigator-pane.tsx renders the tree before the app bar and uses android:flex-col-reverse to keep the header visually above it, the same workaround Sheet.android.tsx uses. On iOS the inspector AppBar only registers native header options, so its position in JSX changes nothing there.
• FileTreeBrowser.tsx sets nestedScrollEnabled={false} (Android-only prop; React Native turns it on by default for lists with a refresh control). With nested scrolling on, upward swipes scroll the tree but downward swipes collapse the sheet.
• Each of the two ordering changes carries a one-line comment so a later cleanup does not revert it.

The bottom sheet drags from the first nested-scrolling view it finds; the exact native target was inferred from device experiments, not observed in a debugger. With the fix, a downward swipe inside the tree scrolls the tree (and at the top, pulls to refresh) instead of collapsing the sheet; the sheet still moves from its header, grabber, close button and Back.

Scope and approval

Fixes the linked, triaged bug. Three files, six lines: the pane ordering in the shared Android inspector host, the Files pane's child order, and the tree's nested-scroll flag. The pane ordering applies to every Android inspector pane, and the nested-scroll flag to every FileTreeBrowser (Files sheet, full-screen Files and directory routes); both are covered in Verification. No server, contract or provider change.

Verification

vp run check:changed passes on the merged head (format, lint, knip, typecheck of 2 packages, React Compiler on the 3 files, 8 adjacent tests). Native gesture routing cannot be exercised by the jsdom tests, so the proof is device recordings.

Pooled emulators and simulators, real app and dev client, fresh databases (T3CODE_DEV_SEED=0) seeded by the same synthetic driver on each side: a git repo with 40 folders × 6 files, a nested needle-match.txt, 30 modified files, one stopped thread. Before = main 4c361199f4, after = 23310d1489 (later commits on the branch only merge main).

Environment: Pixel 9 and Pixel Tablet emulators, Android 16, 1080×2424 whole-device frames, font scale 0.94; iPhone 17 Pro simulator, iOS 27.2, medium text. Dark unless noted.

F01 after the first swipe up, and L01 (light, settled sheet; Diff0 at fuzz 0, DiffT at fuzz 2%):

What else changed: L01 differs only in the clock and cellular icon (AE 923 at fuzz 0), so the reorder leaves the sheet's layout unchanged. Gesture frames differ in list offset, sheet height and backdrop dimming, which follow from the fix. iOS frames differ by a few pixels of final scroll offset under the translucent header.

Every row with narrated steps, timestamps, all stills and diff images: evidence-index.md, overflow-menu row: F11-overflow-section.md. Fixture matrix: matrix.md, capture scope: capture-scope.md. Seed and drivers: seed.mjs, capture.py, device-ios.py, diffs.py.

Earlier physical-device recordings (Samsung Galaxy A54, Android 16, identical patch on an older base): before, after. On that phone, removing any one of the three changes brought the bug back (no tree scroll without the pane zIndex change or the reorder; downward swipes collapsed the sheet with nested scrolling on).

Not verified: Git-pane list scrolling with an overflowing Git overview (the fixture's overview fits on screen), TalkBack traversal order, and iPad inspector columns (iOS does not run the Android host, and the iOS AppBar adds no native child, so the iPhone rows cover the iOS ordering change).