chore: retire legacy wechat-hermes-gateway xmpp_bot, unify bridge to :5807

Old xmpp_bot.py (PID-locked separately) coexisted with new xmpp_agent_core,
causing duplicate JID connections and split bridge traffic (5802 vs 5807).
Deploy scripts now use new bot's :5807 bridge with X-Api-Key auth.

deploy/linux/sync-venv.sh

@@ -41,8 +41,8 @@ fi
 
 # 自动检测 repo 根目录并设为 AGENTSMEETING_ROOT（A-F 端点依赖此路径找 .git 和 gateway/temp）
 export AGENTSMEETING_ROOT="$REPO_DIR"
-# XMPP Bridge（EasyTier/RDP 操作通过 Windows 的 xmpp_bot :5802 代理）
-export XMPP_BRIDGE_URL="http://192.168.1.16:5802"
+# XMPP Bridge（EasyTier/RDP 操作通过 Windows 的 xmpp_agent_core :5807 代理）
+export XMPP_BRIDGE_URL="http://192.168.1.16:5807"
 cd "$VENV_DIR"
 nohup python3 dashboard.py > "$DASH_LOG" 2>&1 &
 sleep 3

deploy/windows/check.ps1

@@ -9,7 +9,7 @@ if ($bot) { Write-Host "xmpp_bot:     RUNNING (PID $($bot.ProcessId))" -Foregrou
 else { Write-Host "xmpp_bot:     STOPPED" -ForegroundColor Red }
 
 # HTTP bridge test
-try { $r = Invoke-RestMethod "http://127.0.0.1:5802/messages" -TimeoutSec 3 -ErrorAction Stop; Write-Host "http_bridge:  OK ($($r.count) msgs)" -ForegroundColor Green }
+try { $r = Invoke-RestMethod "http://127.0.0.1:5807/messages" -Headers @{"X-Api-Key"="xxm_bridge_8f3a2c"} -TimeoutSec 3 -ErrorAction Stop; Write-Host "http_bridge:  OK ($($r.count) msgs)" -ForegroundColor Green }
 catch { Write-Host "http_bridge:  ERROR" -ForegroundColor Yellow }
 
 # WeChat

deploy/windows/start.bat

@@ -15,6 +15,6 @@ start /b "" /D "D:\F\NewI\opencode\daily-workspace\projects\AgentsMeeting" "C:\U
 timeout /t 10 /nobreak >nul
 
 echo [3/3] EasyTier...
-curl -s -X POST http://127.0.0.1:5802/easytier -H "Content-Type: application/json" -d "{\"action\":\"start\"}" >nul
+curl -s -X POST http://127.0.0.1:5807/easytier -H "Content-Type: application/json" -H "X-Api-Key: xxm_bridge_8f3a2c" -d "{\"action\":\"start\"}" >nul
 
 echo === Done ===