Fix bridge history, profile models, and Windows gateway handling (#845)

* feat: support profile-aware group chat bridge flows

* feat: route cron jobs through hermes cli

* Fix group chat routing and isolate bridge tests

* Add Grok image-to-video media skill

* Default Grok videos to media directory

* Fix bridge profile fallback and cron repeat clearing

* Refine bridge chat and gateway platform handling

* Filter bridge tool-call text deltas

* Preserve structured bridge chat history

* Prepare beta release build artifacts

* Fix Windows run profile resolution

* Fix Windows path compatibility checks

* Fix profile-scoped model page display

* Hide Windows subprocess windows for jobs and updates

* Hide Windows file backend subprocess windows

* Avoid Windows gateway restart lock conflicts

* Treat Windows gateway lock as running on startup

* Force release Windows gateway lock on restart

* Tighten Windows gateway lock cleanup

* Update chat e2e source expectation

* Bump package version to 0.5.30

---------

Co-authored-by: Codex <codex@openai.com>

docs/cli-chat-sessions.md

@@ -417,7 +417,7 @@ bridge 启动失败不会阻止 Web UI 启动，但 Bridge(beta) 会话后续运
 随后创建统一的 chat socket：
 
 ```ts
-chatRunServer = new ChatRunSocket(groupChatServer.getIO(), getGatewayManagerInstance())
+chatRunServer = new ChatRunSocket(groupChatServer.getIO())
 chatRunServer.init()
 ```
 

docs/docker.md

@@ -26,7 +26,7 @@ This compose file runs a single service:
 
 - `hermes-webui` — Web UI dashboard with integrated Hermes Agent runtime (pre-built image or built from source)
 
-The Web UI container is built on the `nousresearch/hermes-agent` base image and internally manages the Hermes Agent gateway lifecycle via `GatewayManager`.
+The Web UI container is built on the `nousresearch/hermes-agent` base image and uses the Hermes CLI / agent bridge runtime for chat execution. It does not start or manage a separate Hermes gateway process.
 
 ## Environment Variables
 
@@ -76,14 +76,14 @@ AUTH_DISABLED=false
 |---|---|
 | `${PORT}` (6060) | Web UI dashboard |
 
-Hermes Agent gateway ports (8642-8670) are used internally within the container and are not exposed to the host.
+No Hermes gateway ports are exposed by this compose setup.
 
 ## Code Runtime Behavior
 
 - Hermes CLI binary comes from `HERMES_BIN` env (`packages/server/src/services/hermes-cli.ts`).
 - If `HERMES_BIN` is not provided, code falls back to `hermes` in `PATH`.
-- Profile switching dynamically resolves upstream URLs via `GatewayManager`.
-- The Web UI automatically starts and manages the Hermes Agent gateway process on startup.
+- Profile-specific chat runs are handled through the Hermes agent bridge.
+- The Web UI does not automatically start or manage a Hermes Agent gateway process on startup.
 
 ## Common Operations