docs(logbook): record telegram outbound mirror deploy [skip ci]

This commit is contained in:
Your Name
2026-05-07 00:31:16 +08:00
parent cf0b6be695
commit 7b98f71393

View File

@@ -4417,3 +4417,28 @@ DATABASE_URL='postgresql+asyncpg://test:test@localhost:5432/test' \
### 判讀
這一步是 mirror-first不改 Telegram 實際發送、不切 Channel Hub 主路徑。下一步要補的是 direct Bot API caller 收斂與 firing alert fingerprint 聚合,讓戰情室只接收需要人注意的摘要,完整時間線回到 AwoooP。
### 00:30 生產驗證
```text
Gitea workflows:
1831 / 1832 @ 9365bdab -> completed success
awoooi-api image:
192.168.0.110:5000/awoooi/api:9365bdab932444ec969bb67490b6ff374d5e5883
awoooi-web image:
192.168.0.110:5000/awoooi/web:9365bdab932444ec969bb67490b6ff374d5e5883
K8s rollout:
awoooi-api -> successfully rolled out
awoooi-web -> successfully rolled out
HTTP:
/api/v1/health -> 200
/zh-TW/awooop -> 200, no Application error
/zh-TW/awooop/runs -> 200, no Application error
/zh-TW/awooop/approvals -> 200, no Application error
```
判讀legacy Telegram 出站訊息鏡像已部署到正式 API。若後續仍有 Telegram 洗版,優先查 direct Bot API caller 是否繞過 `TelegramGateway._send_request()`,以及同一 firing alert 的 fingerprint 聚合是否尚未收斂。