logging + e2e test fixes

CLAUDE.md

@@ -323,7 +323,7 @@ The following MCP servers are configured for this project:
 | redis                 | Redis cache inspection (localhost:6379)     |
 | sentry-selfhosted-mcp | Error tracking via Bugsink (localhost:8000) |
 
-**Note:** MCP servers are currently only available in **Claude CLI**. Due to a bug in Claude VS Code extension, MCP servers do not work there yet.
+**Note:** MCP servers work in both **Claude CLI** and **Claude Code VS Code extension** (as of January 2026).
 
 ### Sentry/Bugsink MCP Server Setup (ADR-015)
 
@@ -366,3 +366,26 @@ To enable Claude Code to query and analyze application errors from Bugsink:
    - Search by error message or stack trace
    - Update issue status (resolve, ignore)
    - Add comments to issues
+
+### SSH Server Access
+
+Claude Code can execute commands on the production server via SSH:
+
+```bash
+# Basic command execution
+ssh root@projectium.com "command here"
+
+# Examples:
+ssh root@projectium.com "systemctl status logstash"
+ssh root@projectium.com "pm2 list"
+ssh root@projectium.com "tail -50 /var/www/flyer-crawler.projectium.com/logs/app.log"
+```
+
+**Use cases:**
+
+- Managing Logstash, PM2, NGINX, Redis services
+- Viewing server logs
+- Deploying configuration changes
+- Checking service status
+
+**Important:** SSH access requires the host machine to have SSH keys configured for `root@projectium.com`.