Session title changes don't propagate to the Android app

### Summary

Renaming a Claude Code session is not reflected in the Android app. The app keeps showing the title the session had when it first synced.

### Steps to reproduce

1. Start a session on the desktop (local session, `sessionId: local_...`, `isRemote: false`).
2. Send a first message, then rename the session (session-management `set_session_title`, `session_id: "self"`).
3. `get_session` confirms the new title on the desktop side.
4. Open the same session in the Android app.

### Expected

The app shows the current session title.

### Actual

The app shows the title from the initial sync. Force-stopping the app and reloading does not update it. The desktop side is correct throughout.

### Impact

Sessions are typically auto-renamed *after* the first message, because the title is derived from it. On Android this means essentially every session shows a stale or empty title.

### Environment

- Windows 11 Pro 26200, Claude Code desktop app
- Android app, force-stop + reload attempted

Start at the session-management set_session_title entry point and compare its update with what get_session returns on the desktop side. Trace how the renamed session reaches the Android app and how the app reloads session metadata. Done means a title changed after the first message is shown in Android, including after force-stopping and reopening the app.

Rédigé par le modèle d'indexation à partir du texte de l'issue.