[Bug] Pinned sessions disappear from pinned area when paginated to page 2

Bug Description
Title: Web fleet view: pinned sessions drop off the pinned area once they paginate to page 2 Body: ## Summary In the Claude Code fleet view on web (claude.ai/code), pinned sessions silently stop appearing in the pinned area once they become old enough to fall onto the second page of the session list. The sessions are still active and still pinned — they just vanish from the UI. This defeats the purpose of pinning, whose value is to keep important sessions surfaced regardless of recency. (Pinning is a web-only feature; the mobile app has no pin behavior, so this is scoped to web.) ## Environment - Claude Code fleet view (Remote Control sessions), web only (claude.ai/code). The mobile app does not have a pin feature. - GET /v1/code/sessions is paginated (next_cursor), ~20 items per page. Account had ~37 total sessions across 2 pages when this occurred. ## Repro 1. Have enough sessions that the list paginates (20+). 2. Pin ~7 sessions. 3. Let 2 of the pinned sessions go idle while other sessions stay more recently active — so that, sorted by recency, those 2 land on page 2 of the session list. 4. Open the fleet view on web (claude.ai/code). ## Expected All pinned sessions appear in the pinned area, regardless of recency or which API page they fall on. Pins should be sticky. ## Actual Only the pinned sessions on page 1 render. Pinned sessions that paginated to page 2 disappear entirely — even though still active and pinned. ## Evidence (7 pinned, by last activity; redacted) | Pinned session | idle | API page | In pinned view? | status | |---|---|---|---|---| | Session A | ~minutes | 1 | yes | active | | Session B | ~minutes | 1 | yes | active | | Session C | ~hours | 1 | yes | active (connected) | | Session D | ~1 day | 1 | yes | active | | Session E | ~4 days | 1 | yes | archived | | Session F | ~5 days | 2 | NO | active | | Session G | ~5 days | 2 | NO | active | The two that disappeared are exactly the two least-recently-active pinned sessions, and the only two on page 2. ## Ruled out - Not connection state: connected and disconnected pinned sessions both render on page 1. - Not archival: an archived pinned session (E) still renders (page 1); the dropped ones are active. - Not deletion/unpin in data: both remain active and reachable at https://claude.ai/code/session_<id>. ## Hypothesized root cause The web fleet view appears to load only the first page of GET /v1/code/sessions and renders the pinned section from that page. Pinned sessions beyond page 1 are never fetched, so their pin isn't rendered. Pins should resolve independently of the recency-paginated list (dedicated pinned-sessions query, or fetch additional pages until all pins resolve). ## Impact Users lose visibility of pinned work as it ages — the opposite of what pinning promises, and it reads as "did something delete my pinned conversation?" Workaround: re-open the session to bump recency back onto page 1.

Environment Info

• Platform: darwin
• Terminal: vscode
• Version: 2.1.191
• Feedback ID: 7261d2d8-dc8b-4edb-9e0b-32ca36199b68

Errors

[]