sync: update from private repo (ddadfd71)

docs/docker.md

@@ -20,8 +20,11 @@ opens a setup wizard in the UI where you point MAESTRO at your LLM. To preset th
 endpoint instead, `cp .env.example .env` and set `OLLAMA_BASE_URL`/`OLLAMA_MODEL`
 (see [The LLM endpoint](#the-llm-endpoint)).
 
-Compose publishes the UI on `127.0.0.1:9876` only, so a fresh instance is not
-reachable from your LAN. See [Going beyond localhost](#going-beyond-localhost).
+Compose publishes the UI on `9876` on **all host interfaces**, so a Docker host
+is reachable from your LAN out of the box. That also means a fresh instance is
+exposed and **unauthenticated** — anyone who can reach the port can run code on
+the host via the agent's Bash tool. Read [Going beyond localhost](#going-beyond-localhost)
+before leaving it up on a shared network.
 
 ### Windows (WSL2)
 
@@ -129,14 +132,16 @@ Rebuild after pulling new code with `docker compose up -d --build`.
 
 ## Going beyond localhost
 
-The default binding is intentionally local-only. Before exposing MAESTRO to a
-network:
+By default Compose publishes `9876` on all interfaces, so the instance is already
+reachable from your LAN — **and unauthenticated**. Before you rely on it on any
+shared or untrusted network, harden it:
 
 1. Enable authentication (OAuth, or local accounts).
 2. Set `safety.bash_sandbox: always`.
 3. Terminate TLS — either MAESTRO's native HTTPS or a reverse proxy in front.
-4. Change the compose port mapping from `127.0.0.1:9876:9876` to the interface
-   you intend to serve.
+
+To keep an instance **local-only** instead (e.g. reach it over an SSH tunnel),
+pin the compose port mapping back to `127.0.0.1:9876:9876`.
 
 See [SECURITY.md](../SECURITY.md) and
 [getting-started.md](getting-started.md) for the full hardening checklist.