更新英文README - 添加v2.0更新记录

Author: chu0119

README.md

@@ -345,3 +345,115 @@ Potential next improvements:
 ## License
 
 No open-source license is currently declared. Without explicit permission from the repository owner, redistribution, commercial reuse, and derivative publication are not granted.
+
+## v2.0.0 Update Log (2026-07-07)
+
+### 🚀 New Features
+
+#### Multi-Worker Architecture
+- **API Worker**: Independent HTTP request handling, supports horizontal scaling
+- **Monitor Worker**: Independent Telegram monitoring, each Worker manages 3-5 accounts
+- **Auto-deployment script**: `deploy-auto.sh` one-click multi-Worker deployment
+- **Worker status API**: `/status`, `/health` endpoints for Worker monitoring
+
+#### Health Check API
+- `GET /api/v1/health/` - Basic health check
+- `GET /api/v1/health/detailed` - Detailed status (database, Redis, system, Telegram)
+- `GET /api/v1/health/metrics` - Performance metrics
+
+#### Code Quality
+- **Unified error handling**: `AppException` exception system, standardized error responses
+- **Input validation**: Pydantic validators, prevent invalid input
+- **Code review**: Fixed 15 code quality issues
+
+### ⚡ Performance Optimization
+
+#### Dashboard API Performance Improvement
+
+| API | Before | After | Improvement |
+|-----|--------|-------|-------------|
+| `/dashboard/stats` | 3.4s | 0.17ms | 20,000x |
+| `/dashboard/sender-ranking` | 11s | 0.2ms | 55,000x |
+| `/dashboard/conversation-activity` | 9s | 20ms | 450x |
+| Serial loading total | 15s | 0.24s | 62x |
+
+#### Optimization Techniques
+- **Pre-computed fields**: Added `sender_count` to conversations table
+- **Subquery optimization**: Avoid large table JOINs
+- **Approximate counting**: Use `information_schema` for large table row counts
+- **Redis caching**: All API results cached for 60 seconds
+- **Virtual scrolling**: React Virtuoso for large list optimization
+
+### 🐛 Bug Fixes
+
+#### Critical Bugs
+- **Fixed `database is locked` error**: SQLite session file concurrent access conflict
+- **Fixed Redis connection failure returning False**: Caused TypeError crash
+- **Fixed worker_id=0 being ignored**: Falsy value handling error
+- **Fixed port collision bug**: Worker port assignment error
+
+#### Feature Bugs
+- **Fixed pagination reset issue**: Auto-reset to page 1 when filter changes
+- **Fixed proxy configuration issue**: socks5 → socks5h (DNS resolution through proxy)
+- **Fixed Session file corruption**: Added file lock protection
+
+### 🔒 Security Improvements
+- **APIKeyAuth middleware**: Support API key authentication
+- **Unified exception handling**: Prevent exposure of internal error details
+- **Input validation**: Prevent SQL injection and XSS attacks
+
+### 📦 Deployment Improvements
+- **Systemd services**: Support multi-Worker independent services
+- **Nginx configuration**: Load balancing configuration
+- **Auto-deployment**: One-click deployment script
+
+### 📝 Multi-Worker Deployment Guide
+
+#### Auto Deployment (Recommended)
+
+```bash
+cd backend/workers
+sudo bash deploy-auto.sh 2 3  # 2 API Workers, 3 Monitor Workers
+```
+
+#### Manual Deployment
+
+```bash
+# 1. Edit configuration
+vim backend/workers/config.json
+
+# 2. Install services
+sudo cp backend/workers/tgmonitor-api-*.service /etc/systemd/system/
+sudo cp backend/workers/tgmonitor-monitor-*.service /etc/systemd/system/
+sudo systemctl daemon-reload
+
+# 3. Start services
+sudo systemctl start tgmonitor-api-0 tgmonitor-api-1
+sudo systemctl start tgmonitor-monitor-0 tgmonitor-monitor-1 tgmonitor-monitor-2
+
+# 4. Enable auto-start
+sudo systemctl enable tgmonitor-api-* tgmonitor-monitor-*
+```
+
+#### Configuration Example
+
+```json
+{
+  "api_workers": 2,
+  "monitor_workers": 3,
+  "accounts_per_worker": 5,
+  "worker_ports": {
+    "api": [8000, 8001],
+    "monitor": [8010, 8011, 8012]
+  }
+}
+```
+
+### 📊 Performance Comparison
+
+| Metric | v1.x | v2.0 | Improvement |
+|--------|------|------|-------------|
+| Dashboard load time | 15s | 0.24s | 62x |
+| Single API response | 3-11s | 0.2ms | 5000x |
+| Concurrent handling | 1 Worker | N Workers | Linear scaling |
+| Fault isolation | None | Single Worker failure doesn't affect others | Significant |