`This beta release introduces major architectural improvements, focusing on unifying core messaging workflows to eliminate technical debt, adding self-healing diagnostics to the WhatsApp bridge, and hardening overall security and state concurrency.
🛠️ Key Technical Improvements
- Unified Messaging Core (DRY): Centralized HTTP request handling, pacing, and logging into a new shared
scripts/common.pymodule. This eliminates duplicate logic acrosssend.py,files.py,agenda.py, andcontacts.py. - Self-Healing Bridge Patches: Upgraded
bridge_health.pyandpatch_bridge.pyto automatically detect, diagnose, and inject missing API endpoints (/health,/groups,/qr,/typing) into the local agent'sbridge.jswithout manual intervention. - Security & Path Hardening:
- Replaced broad exception handlers with strict
except Exception:captures across all Python scripts. - Secured
setup_portable.pyby applying directory-level extraction filters to mitigate path traversal risks. - Hardened rate limits and updated loop-detection rules inside the system firewall (
guard.py).
- Replaced broad exception handlers with strict
- Atomic Concurrency Control: Standardized file-level locking (
fcntl.flock) during concurrent write operations to ensure inbox queues and configuration assets are protected from file corruption. - Universal Documentation Sync: Synchronized legal notices, multi-language landing assets, and the manual (
SKILL.md) to represent the exact specifications ofv1.0.4-Beta1.
🐛 Testing & Bug Reports
This is a Beta release. Please test these features in your local environment. If you encounter any bugs, errors, or unexpected behavior, please open an issue in the GitHub Issues section so we can address it before the final release.
``