Record that Hermes on talos is wired to the robot and passes its MCP test

With the owner's authorisation, ~/.hermes/config.yaml and .env on talos gained
the robot's MCP server and token (backed up first). `hermes mcp test robot`
connects in 789 ms and discovers look(). A real agent turn, which would send a
camera image to the hosted model, is left for the owner to approve.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AFN8nRRCiDiMN7ChBpHJhs

CONTEXT.md

@@ -227,6 +227,18 @@ left. The token is in `/etc/robot-mcp.env` (root:hermes, mode 640), generated by
 are superseded (package 5 rewrites the installer). **Not yet verified:** a real Hermes client, and
 whether Hermes passes MCP image content to the model (HANDOFF package 6).
 
+**Hermes on talos is wired to it (2026-10-05, with the owner's authorisation).** Hermes Agent v0.21.5 is
+installed on talos (`~/.hermes`; hosted main model `grok-4.6` via xai-oauth; vision is auxiliary and
+runs locally, `qwen3-vl-8b-abliterated` on straylight; the `ornith-*` models are the local ones on
+straylight/dixie). `~/.hermes/config.yaml` gained an `mcp_servers.robot` block (URL
+`http://10.55.0.2:8765/mcp`, `Authorization: Bearer ${ROBOT_MCP_TOKEN}`) and `~/.hermes/.env` gained
+`ROBOT_MCP_TOKEN`; backups are `config.yaml.bak-20261005T002659-robot-mcp` and
+`.env.bak-20261005T002659-robot-mcp`. `hermes mcp list` shows it enabled and **`hermes mcp test
+robot` passes: connected in 789 ms, 1 tool (`look`)**, which is the HANDOFF acceptance check. Not done
+yet: a real agent turn that calls `look()` (it would send a camera image to the hosted model, so it
+needs the owner's say-so), which is also what settles whether Hermes hands MCP images to the model.
+A fresh `HERMES_HOME` hangs on first-run setup, so test against the real one.
+
 ## Face recognition (opt-in)
 
 `hermes_vision.recognize` / `people`: SFace embeddings on YuNet's landmarks. Nothing is stored until