本次更新为主 Web 服务新增可选 HTTPS 支持，并在启用 TLS 时通过 HTTP/2 多路复用缓解浏览器对同源 HTTP/1.1 约 6 条并发连接的限制。在 Deep 多代理长时流式（SSE）与大量 API 并行场景下，可避免连接池耗尽导致的页面卡死。配置支持 tls_enabled、tls_cert_path/tls_key_path（生产）及 tls_auto_self_sign（本地自签）；run.sh 默认以 --https 启动，可用 --http 回退明文。启动后请使用 https://127.0.0.1:<端口>/ 访问。
This update adds optional HTTPS for the main web server and negotiates HTTP/2 over TLS to mitigate the browser’s per-origin concurrent connection limit under HTTP/1.1 (~6 connections). That limit often caused UI freezes when long-running Deep agent SSE streams competed with regular API calls. TLS can be enabled via tls_enabled, production PEM paths (tls_cert_path / tls_key_path), or in-memory self-signed certs (tls_auto_self_sign) for local testing. run.sh now defaults to --https (use --http for plain HTTP). After startup, open https://127.0.0.1:/ and accept the self-signed certificate warning once if applicable.