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.
- Replace start.ps1 with start.bat (avoids false-positive trojan warnings from Defender) - Mark wechat_agent.py as stopped in README.md, add article_processor doc - Keep start.ps1 deletion tracked Ultraworked with Sisyphus Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
- Platform-based architecture (Windows/Linux/Mac) - Agent instance registry (agents.yaml) - Management dashboard with cross-platform monitoring - xmpp_bot with HTTP bridge + health endpoints - wechat_agent with WeChat-Hermes bridging - Platform services: ProcessGuardian, HealthProbe, APIRouter, ChannelBridge - Deployment: systemd (Linux) + PowerShell (Windows) - Monitoring: SSH+ejabberdctl for cross-platform presence