[DOCS+UX] Remote Control: docs don't say sessions live under Code tab; QR code doesn't deep-link there either

The Remote Control documentation at https://code.claude.com/docs/en/remote-control has a discoverability gap, and the QR code workflow doesn't paper over it the way it should.

Issue 1 — Docs don't specify the Code tab.

The "Connect from another device" section says:

Open claude.ai/code or the Claude app and find the session by name in the session list. Remote Control sessions show a computer icon with a green status dot when online.

This treats "the Claude app" as homogeneous. A user opening the Claude app for the first time lands on their Chats list, sees nothing, and assumes the feature is broken — when in fact they need to navigate to the Code tab.

Suggested fix: add a single sentence, e.g.

Open the Claude app and tap the Code tab. Remote Control sessions appear in the session list there, marked with a computer icon and green status dot.

Issue 2 — The QR code doesn't deep-link to the session.

Scanning the QR code shown by claude remote-control (or pressing spacebar to display it) opens the Claude app, but lands on the app's default surface (typically Chats) rather than navigating directly to the Code tab and the active Remote Control session. The user still has to know to tap the Code tab and find the session manually.

This is the bigger problem. The QR code is positioned as the "quick access from your phone" path, but it doesn't actually take you to the session — it just launches the app. If the QR code carried a deep link that opened the session directly, the docs gap would be much less painful.

Suggested fix: make the QR code (and the session URL it encodes) deep-link directly to the Code tab and the session, bypassing the app's default landing surface.

For context: I personally lost ~30 minutes troubleshooting this before realizing the session was waiting under Code. The feature itself works; the navigation and the QR flow are the barriers.