Allow Remote sessions to outlive connection forms

docs/tentacle-sessions.md

@@ -114,6 +114,29 @@ cleanup context, so pre-lease inspection does not depend on a revocation event.
 No form values accompany that cleanup. Session failure/disable still uses
 normal process supervision. Existing non-remote interactions keep their path.
 
+An explicit return-to-desktop action may instead finish with:
+
+```json
+{"remote_background":{"lease":"0123456789abcdef0123456789abcdef","epoch":1},"done":true}
+```
+
+This terminal result requires an already-open, unexpired lease belonging to the
+requesting process session. If this interaction approved an epoch, it must match
+the requested lease. Forms, continuations, polling, clipboard, reader/consent
+requests and uninterruptible speech cannot accompany it; ordinary speech/Braille
+presentation is allowed. A polling response cannot detach a form. Go exposes
+`Interaction.RemoteBackground`; Python uses the dictionary above.
+
+On success, core releases the interaction/result slots without invoking child
+cancellation or revoking that epoch. The original policy/session lease remains
+its owner: heartbeats, expiry, lock, handoff, disconnect, replacement, disable,
+update and process loss retain their existing behavior. This result neither
+renews authority nor starts networking. The Tentacle must offer an explicit
+status/disconnect command; reopening status needs no new consent, while a new
+connection still does. Ordinary cancellation and form closure retain their
+existing cleanup behavior. `RemoteLeaseContext` checks identity/lifetime only;
+desktop effects still require `RemoteContext` with their specific grant.
+
 This addition requires the matching updated reader; protocol 1.1 by itself does
 not imply that an older reader accepts the new interaction field. Remote still
 has no release manifest advertising a minimum supported reader version.