feat: browser-control server on host (real input) + remote-bot routing + ignore env backups

- control-server.mjs runs chrome-control.mjs LOCALLY on the browser host, so a
  remote bot's controlBrowser (BROWSER_CONTROL_URL) drives real xdotool input
  on THIS screen instead of the bot machine. Published on the LAN.
- controlBrowser tool posts to BROWSER_CONTROL_URL when set, else runs locally.
- Drop hard depends_on ollama so a browser-host doesn't start Ollama.
- gitignore .env.bak*/*.bak (a backup with tokens had been left untracked).

docker-compose.yml

@@ -91,8 +91,17 @@ services:
       # Where the bot drives Chrome. Loopback for full/browser; on a remote bot
       # set CDP_HOST to the browser host's LAN IP (e.g. 192.168.10.9).
       CDP_HOST: ${CDP_HOST:-127.0.0.1}
-    depends_on:
-      - ollama
+      # Browser-control endpoint. The browser host serves it (BIND/PORT); a
+      # remote bot sets BROWSER_CONTROL_URL=http://<browser-host>:8777 so its
+      # controlBrowser tool posts there instead of running node locally. Empty
+      # on full/browser → the tool runs chrome-control.mjs locally.
+      BROWSER_CONTROL_BIND: ${BROWSER_CONTROL_BIND:-0.0.0.0}
+      BROWSER_CONTROL_PORT: ${BROWSER_CONTROL_PORT:-8777}
+      BROWSER_CONTROL_URL: ${BROWSER_CONTROL_URL:-}
+    # No hard depends_on ollama: a browser-host (`docker compose up -d javis`)
+    # must NOT pull in Ollama. Full/bot layouts start it with a plain
+    # `docker compose up -d` (all services); the bridge tolerates Ollama warming
+    # up lazily, so start order doesn't matter.
     # GPU: accelerates Whisper STT (and anything else CUDA) in this container.
     # Verified: faster-whisper float16 works on the RTX 5050 (sm_120).
     devices:
@@ -110,6 +119,9 @@ services:
       # Chrome CDP for a remote bot (JARVIS_ROLE=bot). Loopback by default; for a
       # LAN browser-host set CDP_PUBLISH_BIND=0.0.0.0 (internal network, no auth).
       - "${CDP_PUBLISH_BIND:-127.0.0.1}:${CDP_PORT:-9222}:9222"  # Chrome CDP
+      # Browser-control endpoint a remote bot posts to (real xdotool input runs
+      # on THIS host). Published on the LAN for the browser-host layout.
+      - "${CDP_PUBLISH_BIND:-127.0.0.1}:${BROWSER_CONTROL_PORT:-8777}:8777"  # control-server
       # The brain bridge is NOT published: it binds the container's loopback
       # (BRIDGE_HOST=127.0.0.1) and is only consumed by the bot in this same
       # container, so it needs no host port and stays unreachable off-container.