fix(mobile): preserve navigation after native swipe back

[juliusmarminge]

A tap immediately after swiping Back can be ignored: the router still considers the dismissed page current, or a late dismissal pops the newly opened page too. This synchronizes card history when the destination appears and scopes dismissal to the original route, preserving later pushes. Outgoing native screens remain attached until UIKit finishes its own pop.

Cancelled swipes retain their history. Modal and workspace dismissal behavior keeps its existing path. This is an iOS JavaScript change with no native dependency or runtime bump.

Validation:

• 21 focused stack projection tests passed, including real StackRouter regressions for late dismissals, same-page reopening, and cancellation.
• Mobile TypeScript, targeted lint, and React Doctor passed.
• iPhone 17 Pro Max on iOS 26.5: 12 rapid swipe-back/page changes reached the expected destination. Same-page reopening, cancelled swipes, and file/diff navigation passed; the unsent draft survived.
• A double-swipe stress probe unexpectedly opened a different file and its actions menu. This remains untriaged: it may be an automation targeting problem or a separate touch/navigation race. That run is not counted as passing evidence.

Before: a late card dismissal consumes a subsequent push, or navigating to the still-current page does nothing. After: the source-relative pop preserves the new route, and the completed swipe permits reopening the same page. The regression tests exercise both router histories.

Simulator recording:

https://gh-file-drop-api-prod-mi5fy3sowv63ufte.pinglabs.workers.dev/f/67c47d67790f6767/t3-swipe-navigation-proof.mp4

Implemented and verified with GPT-6.1-Sol through the Codex harness in T3 Code.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This is a focused iOS navigation fix, but it introduces a non-trivial stateful handoff between native swipe transitions and router history across several lifecycle callbacks. The added tests cover key router cases, while the production event-sequencing logic remains complex enough to warrant human review.

Notes:

• Diff unchanged. Approvability was decided on eligibility alone.

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

[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: 03cd452f-225e-47d5-9747-eccc19d8ae3c

📥 Commits

Reviewing files that changed from the base of the PR and between e8f5850 and 0c61583.

📒 Files selected for processing (3)

• apps/mobile/src/native/createV5StackNavigator.ios.tsx
• apps/mobile/src/native/workspace-stack-projection.test.ts
• apps/mobile/src/native/workspace-stack-projection.ts

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

---

📝 Walkthrough

Walkthrough

The iOS native stack now converts native Back gestures into router pop actions. It tracks routes through native dismissal and validates pop destinations. Tests cover valid destinations, cancelled swipes, and invalid pop sources.

Changes

Native card pop handling

Layer / File(s)	Summary
Build native stack pop actions apps/mobile/src/native/workspace-stack-projection.ts, apps/mobile/src/native/workspace-stack-projection.test.ts	nativeStackPopAction validates the dismissed route and destination before creating a POP action. Tests cover explicit and default destinations, newer pushes, reopened routes, and invalid or cancelled swipes.
Resolve native Back handoffs apps/mobile/src/native/createV5StackNavigator.ios.tsx	V5CardStackView records the active route when it starts disappearing. When another route appears, it dispatches a validated pop action. Popped routes remain attached until their dismissal callbacks complete.

Priority: ➖ Normal

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Bug fix

Sequence Diagram(s)

sequenceDiagram
  participant NativeStack
  participant V5CardStackView
  participant Router
  NativeStack->>V5CardStackView: Report active route disappearance
  V5CardStackView->>V5CardStackView: Record native pop source
  NativeStack->>V5CardStackView: Report another route appeared
  V5CardStackView->>V5CardStackView: Create nativeStackPopAction
  V5CardStackView->>Router: Dispatch pop action
  NativeStack->>V5CardStackView: Report dismissal completion
  V5CardStackView->>V5CardStackView: Clear completing-pop route

Loading

Merge Risk: ⚪ Minimal · up to 0c615

No actionable merge-blocking issue is established. Native callback ordering remains unverified, but the inspected route-retention path preserves cards through dismissal.

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description clearly explains the problem, implementation, verification results, limitations, and user impact. It does not include the required Scope and approval information or an explicit explana…	Add a Scope and approval section. Link the triaged issue or maintainer approval with the approval comment, or explain why this obvious focused bug fix qualifies without prior approval. Keep the existing verification details and untriaged st…

✅ Passed checks (3 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title is concise, conventional, and accurately describes the main iOS navigation fix.

Full details: Description check

Explanation

The description clearly explains the problem, implementation, verification results, limitations, and user impact. It does not include the required Scope and approval information or an explicit explanation for why this focused fix qualifies without prior issue approval.

Resolution

Add a Scope and approval section. Link the triaged issue or maintainer approval with the approval comment, or explain why this obvious focused bug fix qualifies without prior approval. Keep the existing verification details and untriaged stress-probe limitation documented as written.

• Fix all pre-merge checks with AI

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

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

---

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

[github-actions]

🚀 Expo continuous deployment is ready!

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

	🤖 Android	🍎 iOS
Fingerprint	badb3892a265f68257fdbe7dddac7d5be9704d50	e7043135687084dfd330615a9990f5fb5135a131
Build Details	Build Permalink Details Distribution: INTERNAL Build profile: preview:dev Runtime version: badb3892a265f68257fdbe7dddac7d5be9704d50 App version: 2.0.0 Git commit: 69af73366a589b63194c30640f17d09bb6cecd0e	Build Permalink Details Distribution: INTERNAL Build profile: preview:dev Runtime version: e7043135687084dfd330615a9990f5fb5135a131 App version: 2.0.0 Git commit: 69af73366a589b63194c30640f17d09bb6cecd0e
Update Details	Update Permalink Details Branch: pr-17268 Runtime version: badb3892a265f68257fdbe7dddac7d5be9704d50 Git commit: 69af73366a589b63194c30640f17d09bb6cecd0e	Update Permalink Details Branch: pr-17268 Runtime version: e7043135687084dfd330615a9990f5fb5135a131 Git commit: 69af73366a589b63194c30640f17d09bb6cecd0e
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	5.0 KiB	0 B (0.0%)	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	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	20.9 KiB	20.9 KiB	0 B (0.0%)	29.3 KiB	✅
Codex	Live turn messages	2	2	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	+7 B (+0.1%)	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	+7 B (+0.6%)	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: e8f5850 · PR result: 0c61583 · 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.