test(mobile): repin the RPC recording corpus and session closure after #22392

[Jinwoo-H]

	Files	Added	Deleted	Net
Test	1	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​12	$\color{#cf222e}{\Huge{\mathbf{−}}}$​4	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​8
Prod	788	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​788	$\color{#cf222e}{\Huge{\mathbf{−}}}$​788	0

ELI5

Main's CI is red for every open PR. Two test pins were wrong after #22392 landed; this puts both back in line with main. There is no product change.

What Changed

• RPC recording pin. fix(mobile): keep the streamed browser pane flipping on slow phones, and stop double taps #22392 recorded the RPC corpus with baseline set to one of its own branch commits (2c2b84ce9e). The squash merge left that commit unreachable from main, so the "RPC recording pin" ancestry job fails everywhere. This sets baseline to main's tip at the time (80e0bee23b) and re-records the whole corpus. All 787 goldens change only their baseline header line, so no recorded behaviour moved.
• Session route closure pin. SESSION_ROUTE_MODULES said 4217; main measures 4219. feat(native-chat): show context window usage in the composer #22301 added two src/shared modules (agent-session-context-usage.ts, agent-session-context-usage-schema.ts) to the session route without touching mobile/, so the mobile job never ran and main was already two over (4221) when fix(mobile): keep the streamed browser pane flipping on slow phones, and stop double taps #22392 took its correct -2 from a branch base that lacked them. Measured 4219 at 25d7c21fcb^, 4221 at 25d7c21fcb, 4221 before fix(mobile): keep the streamed browser pane flipping on slow phones, and stop double taps #22392, 4219 on main's tip. The pin is set to the measured value, with a history paragraph naming feat(native-chat): show context window usage in the composer #22301.

Why

Repinning to main's tip is the only baseline that is both reachable and recordable (the product sources match it exactly). Re-recording the full corpus proves the pin change is provenance-only.

Linked Issue

N/A: CI unblocker for #22392's squash.

Visual Proof

N/A: test pins only, no UI or behaviour change.

Testing

• rpc-recording-pin-guard.mts ancestry and reproduce: pass (reproduce: 791 tests from the pinned tree).

• Recording suites replayed against the corpus: 1752 passed.

• rpc-recording-pin-guard.test.ts: 19 passed.

• config/scripts closure suites (session-terminal closure, page-closure families, bundle build): 77 passed.

• I manually tested these changes locally

• Automated tests added/updated, or explained why not below

Checklist

• This PR is small and focused
• I explained what changed and why
• N/A for visual proof with reason
• Self-reviewed
• Cross-platform, SSH/remote impact: N/A (test pins only)

[pullfrog]

This run was cancelled 🛑

The workflow was cancelled before completion. Please check the link below for details.

  ^{｜ View workflow run ｜ via Pullfrog ｜ 𝕏}