[Bug]: runtime 0.21.0没有和最新的hermes-agent的0.21.3保持一致，导致state.db-wal存在竞争导致问题

Ekko Studio Version

0.7.21

Agent Runtime and Version (if applicable)

0.21.0

Bug Description

runtime 0.21.0没有和最新的hermes-agent的0.21.3保持一致，导致state.db-wal存在竞争导致问题 会报错 No reply: the turn was stopped because a live Hermes process held a retired state.db-wal generation after its pathname was deleted or replaced. Stop the gateway, dashboard, and cron writers; do not overwrite the current state.db or delete its sidecars. Check the logs for whether Hermes captured the retired generation, then read the adjacent state.db.retired-wal-/manifest.json. If manifest.main.mode is copied, inspect that artifact with hermes sessions recover --source <state.db.retired-wal-*/state.db> --inspect-only before deciding whether its committed frames belong on the current database. A header_only artifact is forensic and does not contain a copied state.db to inspect. Unwritten messages were diverted to sessions/<session_id>.jsonl and, on the gateway, pending_messages/pending-.json.

Steps to Reproduce

1：先启动hermes-agent的一些gateway 2：再启动ekko-stuido 3：升级，或者重启hermes-agent的gateway，会导致state.db-wal存储竞争出现不识别的情况

Expected Behavior

保存runtime和官方一致，或者直接从官方拉取编译最新的runtime，或者直接使用hermes-agent的runtime

Actual Behavior

独立的runtime

Logs / Error Messages

No reply: the turn was stopped because a live Hermes process held a retired state.db-wal generation after its pathname was deleted or replaced. Stop the gateway, dashboard, and cron writers; do not overwrite the current state.db or delete its sidecars. Check the logs for whether Hermes captured the retired generation, then read the adjacent state.db.retired-wal-/manifest.json. If manifest.main.mode is copied, inspect that artifact with hermes sessions recover --source <state.db.retired-wal-*/state.db> --inspect-only before deciding whether its committed frames belong on the current database. A header_only artifact is forensic and does not contain a copied state.db to inspect. Unwritten messages were diverted to sessions/<session_id>.jsonl and, on the gateway, pending_messages/pending-.json.

Environment

macOS

Node Version

No response

Additional Context

No response