fix(mobile): slide settled threads out before collapsing

[StiensWout]

Settling a thread could spring the row back to the right before it disappeared. Settle now finishes the leftward exit, collapses the gap, and then commits the action. Failed settles restore the row, and recycled rows retain their original pending action.

Intercept the swipe release before Gesture Handler starts its return spring. Full swipes and the Settle button share the dismissal animation and respect Reduce Motion.

Validation: mobile typecheck and 41 thread-list tests pass. Native builds succeeded for the iOS simulator and iPhone; the clip below records two full-swipe settles on an iPhone 15 Pro Max. Simulator interaction testing was stopped at the maintainer's request.

iPhone recording

https://pub-b182a4071edc4521829926b34990540b.r2.dev/files/ed69ef0c-a417-421e-b445-bc7e1a1c7513/ios-settle-after.mp4

Implemented with GPT-6 in Codex, running through T3 Code.

Note

Slide settled threads out of view before collapsing in ThreadSwipeableRow

• Settle primary swipe actions now animate the row off-screen and collapse its height before invoking the settlement callback, instead of collapsing immediately
• The callback returns Promise<boolean>; a false result restores the row, and a rejected promise restores mounted rows and shows an error alert
• Patches ReanimatedSwipeable in react-native-gesture-handler@2.32.0.patch to accept a UI-thread release callback that can consume a full swipe release and take over the animation before the built-in spring runs
• ThreadSwipeable now keys its internal row component on resetKey, so changing a row's content identity (variant or snoozed state) remounts the swipeable instead of reusing stale animation state
• Risk: Settle is marked dismiss-before-commit in thread-list-v2-items.tsx; the gesture-handler patch must remain in sync with the upstream ReanimatedSwipeable source or the release callback contract breaks

^{Macroscope summarized e9e7585.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This changes an existing mobile interaction through a new UI-thread dismissal/collapse lifecycle and an application-maintained gesture-handler patch. The async commit timing, recycled-row cleanup, and dependency patch synchronization create enough runtime integration risk to require human review.

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