fix(mobile): restore native scroll-edge effects on forms and PRs

[juliusmarminge]

Settings and form scroll views were not explicitly registered with the v5 screen controller, and PR details/discussions forced the soft scroll-edge style. This left those screens outside the shared native header edge configuration.

Register primary form scroll views with UIKit and pass each route's scroll-edge options through the v5 navigator. PR details and discussions use that same configuration instead of forcing soft blur. Android keeps its existing native view hierarchy.

Validation: mobile typecheck passed; 25 focused scroll-edge/navigation tests passed; React Doctor reported no issues. Tested Settings, its Keyboard subpage, PR details, back navigation, and sheet dismissal in the iOS 27 simulator. Native hierarchy inspection confirmed the automatic edge effect. The Settings visual difference is subtle; this does not force a hard blur style. Other standalone legacy sheets were not changed.

Settings at rest

Before	After

PR details after scrolling

Implemented with GPT-6.1 Sol through the Codex harness.

---

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR changes the user-visible native scroll-edge treatment across shared forms, settings, and pull-request screens, including a new default configuration propagated through the iOS navigator. The behavior is focused but cross-cutting and changes product defaults, so the impact warrants human review.

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

[github-actions]

🚀 Expo continuous deployment is ready!

• Project → t3-code
• Platforms → android, ios
• Scheme → t3code-preview

	🤖 Android	🍎 iOS
Fingerprint	0067ded25bba7e8c0c06c7e1f7b244ed3ed8c2f9	9975816437b2ec3adda76eead1ca006e794033af
Build Details	Build Permalink Details Distribution: INTERNAL Build profile: preview:dev Runtime version: 0067ded25bba7e8c0c06c7e1f7b244ed3ed8c2f9 App version: 2.0.0 Git commit: 71e2b5a10d1bc189f78695d48e7156416c1c9190	Build Permalink Details Distribution: INTERNAL Build profile: preview:dev Runtime version: 9975816437b2ec3adda76eead1ca006e794033af App version: 2.0.0 Git commit: 71e2b5a10d1bc189f78695d48e7156416c1c9190
Update Details	Update Permalink Details Branch: pr-18507 Runtime version: 0067ded25bba7e8c0c06c7e1f7b244ed3ed8c2f9 Git commit: fb6dcf6ec5524a051e883ba3d066295cebec0910	Update Permalink Details Branch: pr-18507 Runtime version: 9975816437b2ec3adda76eead1ca006e794033af Git commit: fb6dcf6ec5524a051e883ba3d066295cebec0910
Update QR

[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: 37e2acd · PR result: 78f9228 · 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: bd5c30b2-548a-490b-8384-cb18e9c02d28

---

📥 Commits

Reviewing files that changed from the base of the PR and between 37e2acd and 78f9228.

---

📒 Files selected for processing (8)

• apps/mobile/src/components/ScreenScrollView.tsx
• apps/mobile/src/features/pull-requests/PullRequestDiscussionScreen.tsx
• apps/mobile/src/features/pull-requests/PullRequestRouteScreen.tsx
• apps/mobile/src/features/settings/SettingsFollowUpRouteScreen.tsx
• apps/mobile/src/features/settings/SettingsKeyboardRouteScreen.tsx
• apps/mobile/src/features/settings/SettingsMicrophoneRouteScreen.tsx
• apps/mobile/src/native/NativeScrollViewMarker.tsx
• apps/mobile/src/native/createV5StackNavigator.ios.tsx

---

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 adds a shared scroll-view wrapper that applies scroll-edge effects from explicit props, screen context, or platform defaults. The iOS navigator supplies each screen’s effect setting through context. Settings and pull request screens use the shared components.

Changes

Mobile scroll-edge effects

Layer / File(s)	Summary
Provide scroll-edge effects apps/mobile/src/native/NativeScrollViewMarker.tsx, apps/mobile/src/native/createV5StackNavigator.ios.tsx	The marker selects explicit effects, context values, or platform defaults. The shared scroll view wraps its content in the marker on iOS. The iOS navigator provides each screen’s scrollEdgeEffects setting through context.
Use shared scroll components apps/mobile/src/components/ScreenScrollView.tsx, apps/mobile/src/features/pull-requests/PullRequest*Screen.tsx, apps/mobile/src/features/settings/Settings*RouteScreen.tsx	Settings screens import the shared scroll view. Pull request screens import the app marker and remove explicit soft edge effects.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Sequence Diagram(s)

sequenceDiagram
  participant V5CardStackView
  participant NativeScrollEdgeEffectsContext
  participant ScreenScrollView
  participant NativeScrollViewMarker
  participant ScrollViewMarker
  V5CardStackView->>NativeScrollEdgeEffectsContext: provides screen scrollEdgeEffects
  ScreenScrollView->>NativeScrollViewMarker: renders shared scroll view
  NativeScrollViewMarker->>NativeScrollEdgeEffectsContext: reads effects when no explicit prop is set
  NativeScrollViewMarker->>ScrollViewMarker: applies selected effects on iOS

Loading

---

Merge Risk: ⚪ Minimal · up to 78f92

Settings and pull-request scroll views retain native edge effects, including when route options are absent. No actionable merge-blocking risk is evident; proceed with normal checks.

Pre-merge checks | 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check		The title clearly identifies the mobile fix and the restored native scroll-edge effects for forms and pull-request screens.
Description check		The description covers the problem, implementation, scope, verification results, test environments, and required UI evidence. It is detailed and directly aligned with the pull request objectives.
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 docstrings

• Commit to this branch
• Create a new PR

---

🧪 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.}