Remote Control: make the ~4h session resume window configurable (or allow resurrecting expired sessions)

Summary

The documented resume window for claude remote-control sessions is ~4 hours ("These commands work for about four hours after the server stopped"). For an always-on home server on flaky wifi this is too short and is not configurable. Please make it configurable, or provide a way to resurrect sessions after the window.

Use case

• claude remote-control runs as a systemd service on an always-on machine, serving many long-lived sessions (project-specific "workstream" sessions, 7-13 at a time).
• A network outage >10 min makes server mode exit (documented). If nobody notices for >4 hours (overnight, or away from home), the sessions can no longer be brought back with claude remote-control, --continue, or --session-id; they show "This session's environment was deleted".
• The full transcripts are still on disk and stored server-side, so nothing about the data requires the cutoff.

Request (any of these)

1. A setting / env var / flag to extend or disable the 4h window (e.g. --resume-window 7d).
2. Let --session-id <id> re-attach an archived or expired session to the current environment regardless of age.
3. A UI action on the "environment was deleted" banner to "continue in this machine's environment".

Environment

Claude Code 2.1.296, Linux, server mode under systemd --user.