Point the unreachable-relay advice at the next session, not this app

[Alexgodoroja]

A session on a relay this app does not proxy to was turned away with:

This session is on http://127.0.0.1:8798, but this app proxies to https://shell.online. Start it with SHELL_ONLINE_SERVER=https://shell.online to open it here.

The diagnosis is right — the app reaches exactly one relay (vite.config.ts, server/lib/relay-proxy.ts), so that session genuinely cannot be opened. The advice is not.

The subject was the app. It follows "this app proxies to …", so "start it" reads as the app. But SHELL_ONLINE_SERVER is the CLI's variable (cmd/shell/main.go:386-394); the app reads VITE_RELAY_URL / RELAY_URL (app/server/lib/config.ts:220-234). Setting the named variable on the app does nothing.

It promised something it cannot deliver. The session being turned away has usually already finished, and both "ended" and the last screen arrive over the socket (connection.ts:230,323-324). Starting anything opens a new session; this one's screen only ever existed on the relay that recorded it.

Now reads:

This session is on http://127.0.0.1:8798, but this app reaches https://shell.online, so its screen is only available where it was started. A session started with SHELL_ONLINE_SERVER=https://shell.online opens here.

The existing test still asserts both origins and the variable are named; a new one pins the change of subject so the old phrasing cannot come back.

🤖 Generated with Claude Code