A terminal panel beside an agent chat

A real shell on the chat's own connection, opened and closed like the
inspector and never beside it. The modes govern the model; what a person
types is theirs, since they hold the credential and could open the same
shell with an ssh client. The model cannot see the panel -- a button
copies the output you choose into the composer.

The session outlives the socket: closing the panel leaves a build
running, and coming back reattaches with the scrollback. Two tabs share
one shell and the smaller window decides the size. It ends on an idle
timeout, on deleting the chat, on disabling, moving or deleting the
connection, and on a restart -- which says why rather than quietly
opening a fresh shell that has lost the working directory.

The nginx template's `Connection ""` is right for SSE and fails every
WebSocket handshake, so `location /` now uses a `map $http_upgrade`;
update.sh grows a drift check for it, because the only symptom on a
stale vhost is a panel that cannot connect.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/lembas/services/agent/ssh.py

@@ -90,7 +90,7 @@ def spec_from(profile: SshProfile) -> dict[str, Any]:
     }
 
 
-def _connect_kwargs(spec: dict[str, Any]) -> dict[str, Any]:
+def connect_kwargs(spec: dict[str, Any]) -> dict[str, Any]:
     """Everything asyncssh must be told rather than left to discover.
 
     See the module docstring: every one of these has a default that is wrong
@@ -175,7 +175,7 @@ class SshExecutor:
             raise ExecError(problem)
         import asyncssh
 
-        return asyncssh.connect(self.spec["host"], **_connect_kwargs(self.spec))
+        return asyncssh.connect(self.spec["host"], **connect_kwargs(self.spec))
 
     def _wrap(self, exc: Exception) -> ExecError:
         import asyncssh
@@ -345,5 +345,6 @@ __all__ = [
     "available",
     "capture_host_key",
     "check",
+    "connect_kwargs",
     "spec_from",
 ]