fix(mobile): prevent row presses during native back swipes

[juliusmarminge]

Starting an iOS back swipe on an interactive Settings row could begin the pop, then fire the row's press on release and navigate forward again. The environment row reproduced this before the fix.

Update the Screens fork from t3.8 to t3.17. Both edge and iOS 26 content back gestures cancel the nearest React surface touch handler when the gesture enters Began, following the existing legacy Screens behavior. A cancelled swipe also consumes that press; rejected gestures and later taps keep working. Existing native dismissal guards are unchanged.

The native implementation is in 2434ebc, packaged from 4b92b27. The archive retains the same upstream base and contains only this gesture change plus its version bump. Versions between these pins were reserved for separate local fork work.

Validation:

• Native iOS simulator build succeeded.
• iPhone 17 Pro, iOS 26.5: five completed row swipes, two immediate reopens, a cancelled row swipe, and an ordinary row tap passed. Edge Back also passed.
• Mobile TypeScript check passed; 21 workspace stack projection tests passed.
• The final archive's gesture source matches the simulator-tested native source byte for byte. The final version/provenance metadata differs from the tested package.

Before: a swipe starting on the environment row opened environment details instead of staying on Settings. After: Back completes without firing the row, and a new tap opens details normally. The recording uses labeled markers derived from the actual input commands, rather than OS touch visualization.

This native dependency change requires a new binary; an OTA alone cannot deliver it. The change is in iOS gesture handling; Android, web, and desktop behavior are unchanged.

Implemented with GPT-6.1-sol through the Codex harness in T3 Code.

---

[macroscopeapp]

Approvability

Verdict: Approved at 8a18ff5

Macroscope's review found this PR approvable — This replaces the mobile Screens fork with a small, isolated iOS gesture fix that cancels active row presses only when a back swipe is recognized; other platforms and normal taps retain their existing behavior. The native dependency update is fully wired through the package and lockfile and requires a new binary, but introduces no product-default or static-analysis changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	4.9 KiB	−23 B (−0.5%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	−23 B (−1.9%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	20.9 KiB	20.8 KiB	−41 B (−0.2%)	29.3 KiB	✅
Codex	Live turn messages	2	1	−1 (−50.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.2 KiB	21.2 KiB	0 B (0.0%)	29.3 KiB	✅
Claude	Live turn messages	2	2	0 (0.0%)	8	✅

Baseline: 6cd02e9 · PR result: 8a18ff5 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Team
• Run ID: d016e4cd-7ddf-43e2-9846-5ea93d7371dc

---

📥 Commits

Reviewing files that changed from the base of the PR and between 6cd02e9 and 8a18ff5.

---

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

---

📒 Files selected for processing (4)

• apps/mobile/deps/react-native-screens-5.0.0-t3.17.tgz
• apps/mobile/deps/react-native-screens-5.0.0-t3.8.tgz
• apps/mobile/package.json
• docs/operations/mobile-screens-fork.md

---

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 4 remain after this review.

---

---

📝 Walkthrough

Walkthrough

The mobile app’s react-native-screens dependency and the fork link and clone command in the operations documentation now reference the t3.17 version instead of t3.8.

Changes

Mobile screens fork version

Layer / File(s)	Summary
Update dependency and fork references apps/mobile/package.json, docs/operations/mobile-screens-fork.md	The dependency source, fork link, and clone command now reference the t3.17 version.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

---

Merge Risk: ⚪ Minimal · up to 8a18f

The pinned package includes the back-swipe fix for the Settings route. No actionable merge-blocking risk remains after normal checks.

Pre-merge checks | 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check		The title clearly identifies the main fix: preventing row presses during native mobile back swipes.
Description check		The description explains the problem, implementation, scope, provenance, verification steps, observed results, and binary-delivery requirement. It is sufficiently complete for review.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

---

---

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}