fix(mobile): throttle streaming thread visit updates

[saphid]

Streaming thread updates sent one visit command per watermark from React Native. Apply the web client's ten-second trailing throttle, retaining the newest watermark. Thread navigation and unseen completion still dispatch immediately; hidden content and selection cleanup cancel scheduled sends.

Rebuilt head 3b17e2142 includes current V2 3aa47e294 and test-only prerequisite #10865 (merge first). Feature remains one file, 27 additions and 6 deletions. Mobile typecheck, targeted lint and formatting pass. No new simulator run was performed; the prior measured UI evidence below is historical and bound to its stated revisions. CI pending. Direct Claude Opus 5 high review remains unavailable due to expired OAuth (exit 1 before inference).

Historical simulator measurements and recordings

Measured at persisted thread.visited events on one isolated iPhone 16 Pro simulator (iOS 26.5), with one burst per revision: 20 real thread.metadata.update commands at approximately 250 ms intervals over five seconds. Both runs used the same visible thread and disposable V2 server.

Revision	Updates	Persisted visit writes	Result
Before (ThreadDetailScreen.tsx from b9fa1399c)	20	20	One visit for each update
After (#9931 9d459a6bb, integrated at fa6a1ab04)	20	2	Visits 10.010 seconds apart; final watermark equals the newest update

This measures write volume and dispatch spacing, not rendering speed. Title updates provide a controlled source of updatedAt changes; this was not a timed provider-token stream. The shared native Debug build exited 0; only the JavaScript bundle changed. The integrated candidate also includes #9929, explaining the visible file chip in the after recording.

Before: clean recording · Before: annotated recording

After: clean recording · After: annotated recording

Recordings preserve original timing (before 29.53 s; after 53.63 s), with no idle trimming or speed changes. Captions report the stored-event measurements; the videos do not display a request counter. These caption-only recordings were visually inspected; the interaction-packet validator requires tap/swipe events and was not applicable.

Before/after stills

React Native typecheck and targeted lint passed in frozen integration verification. Android was not separately exercised. Targets Julius’s Orchestrator V2 branch in #2829; this changes only React Native.

A direct Claude Opus 5 high review attempt exited 1 because OAuth expired before model execution; no Claude review occurred. Implemented and verified with GPT-6 in Codex/T3.

Targets V2 #2829. Updated with GPT-6 in Codex/T3.

[macroscopeapp]

Macroscope has since reviewed this pull request. An earlier review was skipped by a cost limit; a review has now completed, so that notice no longer applies.

[macroscopeapp]

Approvability

Verdict: Approved at 3b17e21

Macroscope's review found this PR approvable — The mobile change is a narrowly scoped fix that throttles redundant streaming visit writes while preserving newest-watermark, navigation, and completion semantics. The accompanying server change is test-only, with no production runtime impact.

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

[t3-code]

reviewed diff and relevant surrounding code at 5c4609f5eb0948f5c5e6c1d61834e240b958eee3. no blocking findings.

the effect keeps a trailing newest watermark, bypasses the throttle for unseen completion/thread changes, and cancels pending work when content hides. isolated execution of the actual effect callback passed initial dispatch, trailing update, completion, thread switch, hidden cleanup and dedupe checks with mocked clock/command. no code changes needed. this was not a mounted react or native-device test.

ci snapshot: no failing or pending checks; some checks are skipped. this is a comment review, not an approval or merge.

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.

Dismissing prior approval to re-evaluate 53e0828

[cursor]

Bugbot is paused — on-demand spend limit reached

Bugbot uses usage-based billing for this team and has hit its on-demand spend limit.

A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue.