A connection that cannot point at the machine it is running on

"Nothing runs on the LLeMbas host" is the sentence the absent sandbox and the
absent local MCP rest on, and an SSH profile aimed at 127.0.0.1 walked straight
past it -- through a real login, with every gate in policy.py still applying,
onto the machine holding the database and the Fernet key. From the SSH layer
down it is indistinguishable from a container on the network, so nothing here
could have noticed.

One switch, three positions: never, one named port, anywhere. The middle one is
the one with a real use -- a container that published its SSH port on the
loopback interface is genuinely somewhere else -- and port 22 is refused even
there, because that one is this host's own sshd.

Enforced in five places, because a row can predate a setting: saving a profile,
`session.resolve` (the control every agent tool, the terminal and the canvas go
through), the composer's picker, browsing, and the draft the panels open against
before a chat exists. Check refuses before it opens its socket rather than after.

And the recognition never resolves a name on the request path. `refusal` runs
several times per page render; the first version of this looked names up inline
and the suite went from two minutes to not finishing. Literal forms are decided
from the string, a name is settled where a network call is already expected, and
the answer lives on the row. The gap that leaves is written down rather than
discovered.

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

PLAN.md

@@ -400,6 +400,11 @@ seen working.
       the outer container does, and switching to a shorter panel drops the
       reader at the bottom of the page
 - [ ] Sidebar scroll no longer chains to the document
+- [x] **A connection may not point at this machine** unless an administrator
+      says so, in one of three positions — never, one named port, or anywhere.
+      An SSH profile aimed at `127.0.0.1` walked past the sentence the whole
+      security story rests on, looking from the SSH layer down exactly like a
+      container on the network
 
 ### Phase 1 — the scheduling tools (`0.9.0`)
 - [ ] **A model can schedule.** There was no tool for it — the seam was left