Remote Control (mobile): answered AskUserQuestion prompts get stuck/re-loop; cross-device session state doesn't sync

## Summary

Using Claude Code's mobile "Control remoto" (Remote Control) view against a session started on desktop, two related problems show up repeatedly during the same long-running session:

### 1. Answered AskUserQuestion prompts get stuck / keep re-appearing in Remote Control

After answering an `AskUserQuestion` prompt from the mobile Remote Control view (tapping an option and hitting "Enviar"), the prompt closes momentarily but then reappears — including prompts that were already answered several turns earlier in the conversation and already acted upon by the assistant (e.g. a PR already merged, a build already triggered). The option I originally picked still shows the checkmark, but the screen won't let me move past it, and re-submitting doesn't resolve it — force-closing and reopening the app is the only workaround, and even that isn't always reliable.

Screenshot from a real occurrence (mobile, session titled "Redmi Note 8 vista de lectura fácil"): the visible question is "¿Fusiono el PR #242 para publicar la 0.8.17 (iconos + barra inferior en modo sombras)?" with "Fusiona ahora (Recomendado)" already checked — this exact question had already been answered and the PR had already been merged (confirmed server-side/in the desktop session transcript) well before this screenshot was taken.

### 2. Creating a new session from mobile Remote Control unexpectedly prompts to reconnect GitHub

When trying to start a *new* session from the mobile Remote Control view (while the stuck-prompt issue above was ongoing), the app prompted to connect/reconnect to GitHub before allowing session creation, with no clear reason given. This happened repeatedly ("es constante").

### 3. Background/root cause we suspect: cross-device session state doesn't sync back down

This may be the underlying cause of both of the above. Earlier in the same overall workflow (different day), the same user reported: continuing a conversation on desktop after it was left open on mobile, then going back to mobile, does not reflect the state resolved on desktop — the mobile client still shows the old/pending state and blocks further interaction, forcing a brand new conversation to be started instead of resuming the existing one. It looks like each client keeps its own local view of session/turn state without picking up updates made from another device in the same account, and stale UI (like an already-answered question) can get re-rendered/re-prompted instead of reconciling with the authoritative (server-side) state.

## Environment

- Client: Claude Code mobile, "Control remoto" (Remote Control) feature, controlling a session that was originally started/continued on a Windows desktop client (VSCode extension environment).
- This is a multi-day, long-running session with many turns, background task notifications (CI watch loops via `gh run watch`), and several `AskUserQuestion` calls in sequence — this may be relevant if the bug is related to session length, background-task interleaving, or the number of pending/resolved prompts accumulated in the transcript.

## Impact

- Makes the mobile Remote Control view effectively unusable once a stuck prompt appears — no reliable way to dismiss it or continue.
- Forces users to abandon in-progress mobile sessions and start new ones, losing continuity.
- Repeated unexplained GitHub re-auth prompts add friction and confusion on top of the stuck-prompt issue.

Filed on behalf of the user via Claude Code itself, at their explicit request, since they were unable to interact with the mobile UI enough to file it themselves.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

No repository files, tests, or code entry points are named. Start by reproducing the issue in the mobile Remote Control view with a long-running desktop session, then compare answered prompts and session state across devices. Done means resolved prompts stay dismissed, desktop changes appear on mobile, and creating a session does not unexpectedly require GitHub reconnection.

Written by the indexing model from the issue text.