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/supervisord.conf

@@ -91,6 +91,19 @@ stdout_logfile_maxbytes=0
 stderr_logfile=/dev/stderr
 stderr_logfile_maxbytes=0
 
+[program:control-server]
+; Browser-control HTTP endpoint on the BROWSER HOST. A remote `bot` posts
+; commands here so xdotool / CDP run on THIS machine (real input on this
+; screen). Only meaningful in full/browser roles. Internal network only.
+command=/app/docker/run-if-role.sh full,browser node /app/bot/scripts/stream-test/control-server.mjs
+directory=/app/bot
+priority=360
+autorestart=true
+stdout_logfile=/dev/stdout
+stdout_logfile_maxbytes=0
+stderr_logfile=/dev/stderr
+stderr_logfile_maxbytes=0
+
 [program:bot]
 command=/app/docker/run-if-role.sh full,bot /app/docker/run-bot.sh
 directory=/app/bot