就地升级后worker容器被销毁 || The worker container is destroyed after in-place upgrade

### Bug Description

我在对 HiClaw 执行就地升级之后，发现之前已经创建并正常运行的所有 Worker 容器在 Docker 中都消失了，看起来像是被直接销毁了。同时在 Element 里，这些worker机器人账号也全部显示为不在线，无法正常使用。
升级前一切正常，升级后仅 Manager 服务还在，但所有 Worker 容器丢失，且重启 hiclaw-manager 也没有自动重建恢复 Worker。
有办法找回worker嘛

### Steps to Reproduce

在 Windows PowerShell 中执行 HiClaw 官方就地升级命令：
Set-ExecutionPolicy Bypass -Scope Process -Force; Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://higress.ai/hiclaw/install.ps1'))

### AI Analysis

_No response_

### Relevant Logs

```shell

```

### Component

CoPaw Worker

### Version / Commit

_No response_

---
### Bug Description

After I performed an in-place upgrade of HiClaw, I found that all the Worker containers that had been created and running normally disappeared in Docker and looked like they were directly destroyed. At the same time, in Element, these worker robot accounts are all displayed as offline and cannot be used normally.
Everything was normal before the upgrade. After the upgrade, only the Manager service is still there, but all Worker containers are lost, and restarting hiclaw-manager does not automatically rebuild and restore the Workers.
Is there any way to get the worker back?

### Steps to Reproduce

Execute HiClaw official in-place upgrade command in Windows PowerShell:
Set-ExecutionPolicy Bypass -Scope Process -Force; Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://higress.ai/hiclaw/install.ps1'))

### AI Analysis

_No response_

### Relevant Logs

```shell

```

### Component

CoPaw Worker

### Version/Commit

_No response_