Docs say --teleport is cloud-only, but it works on Remote Control sessions from another machine

## Summary

`claude --teleport ` successfully pulls a **Remote Control** session that is running on a *different* machine into the local terminal. The documentation (and the in-product `claude-code-guide` agent, which answers from those docs) describes teleport as a Claude Code on the web (cloud) feature only, and the Remote Control docs say nothing about teleporting a Remote Control session. Either the docs are incomplete or this is unintended behaviour; in both cases users get told "there is no CLI way to do this" when there is.

## Environment

- Claude Code v2.1.268 (native build via mise), Linux (Arch / Omarchy), both machines on the same claude.ai account
- Machine A: `claude remote-control` server running, three sessions visible in claude.ai/code
- Machine B: plain terminal, non-git directory

## Steps to reproduce

1. On machine A, start `claude remote-control` and drive a session from claude.ai/code.
2. Copy the session link from claude.ai/code (`https://claude.ai/code/session_...`).
3. On machine B, run `claude --teleport session_...` in some directory.

## Observed

Teleport goes through "Validating session → Fetching session logs → Getting branch info → Checking out branch" and then shows the full conversation with:

> Session resumed. This terminal now has its own copy of the session: new work here stays local and will not appear in the Claude app. To continue on your phone later, run /remote-control in this session.

The "Checking out branch" step silently succeeds in a non-git directory.

## Expected

One of:

- The Remote Control docs and the teleport section of the web docs state that Remote Control sessions can be teleported to another machine, what is copied (transcript only, not files), and what happens with the branch step outside a git repo; **or**
- `--teleport` refuses Remote Control sessions with a clear message, if this is not meant to work.

Asking the `claude-code-guide` agent "does teleport work on Remote Control sessions" currently gets a confident "No, cloud sessions only", which is wrong.

## Minor related note

Running the same command from a Bash tool inside another Claude Code session prints `Transcript saving is off — inherited CLAUDE_CODE_CHILD_SESSION marker`, so the teleported copy is not persisted. That is reasonable, but a hint in the teleport output that the copy will not be saved would help.

Start by reviewing the Remote Control documentation and the teleport section of the web documentation, then reproduce `claude --teleport session_...` from a non-git directory against a Remote Control session. Confirm whether the behavior is supported; done means the relevant docs and resulting guide answers accurately describe teleporting, transcript and branch behavior, or the CLI clearly rejects unsupported sessions.

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