[BUG] Remote Control at startup creates a new remote session on resume instead of reattaching the recorded one

What happened

• I had 6 interactive Claude Code sessions with Remote Control on. Each was renamed with /rename, and each showed its name in the iOS Claude app.
• After a Windows reboot I resumed all 6. Remote Control connected automatically (remoteControlAtStartup: true in ~/.claude/settings.json).
• Each session registered a new remote session instead of reattaching the one recorded in its transcript:
• ~/.claude/sessions/<pid>.json had a new bridgeSessionId (session_01<new>).
• The transcript's bridge-session entry still pointed to the old one (cse_01<old>).
• In the iOS app, the new live sessions had auto-generated names. The old ones stayed in the list as offline entries with the correct names.
• /rename on the PC didn't update the phone title, even though it was saved locally (custom-title entry written, nameSource: "user"). Renaming a session in the iOS app didn't stick either.

Expected

The Remote Control docs say that resuming a conversation reconnects to the Remote Control session recorded in it, so the phone should keep showing the original sessions with their names.

Workaround found

In each session I ran /remote-control and chose Disconnect, then ran /remote-control again with no name. Each session reattached to its original remote session (bridgeSessionId went back to session_01<old>), and the names came back on the phone. So a manual connect reattaches correctly, and only the automatic connect at startup creates a new session.

Repro

1. In /config, turn on Remote Control for all sessions.
2. Start a session, run /rename my-name, and check that the name shows in the iOS app.
3. Reboot the machine.
4. Resume the session with claude --resume <id>.
5. Check the iOS app: the live session has an auto-generated name, and "my-name" is offline.
6. Run /rename again on the PC: the phone title doesn't change.

Environment

• Claude Code 2.1.299
• Windows 11 Pro 10.0.26200
• Claude iOS app
• All 6 sessions behaved the same way.

Related

#59960 and #86607 (both closed as not planned) describe the rename half of this; the new-session-on-resume part isn't covered by either.