Sync the self-hosting stack

README.md

@@ -63,6 +63,12 @@ answers on OpenSSH *and* through an enrolled agent; a Proxmox node has a cluster
 agent. Each route carries its own address, its own credentials and its own health — so a vendor API
 that stops answering no longer makes a device unmanageable while its console is up.
 
+**And a terminal goes over a route you choose.** On a host reachable both ways, opening a shell asks
+which — its agent, or an SSH connection — because those are different networks, different credentials
+and different accounts on the far end. The choice is made before the shell opens, it is recorded on
+the session and in the audit trail, and every route is held to the same limits: the same idle and
+duration ceilings, the same recording, the same retention policy.
+
 **Documents.** A conversation accumulates what the assistant writes: reports and runbooks in
 Markdown, diagrams in Mermaid, tabular data as a workbook. What it writes is always a *source*, and
 Jarvis renders the file on download — PDF and Word from prose, Excel and CSV from a workbook, HTML