docs(awooop): record t38 production verification
This commit is contained in:
@@ -21,15 +21,30 @@
|
||||
|
||||
**本地驗證**:
|
||||
- `DATABASE_URL=postgresql+asyncpg://user:pass@localhost:5432/test python -m pytest apps/api/tests/test_awooop_truth_chain_service.py apps/api/tests/test_telegram_message_templates.py -q`:60 passed。
|
||||
- `python -m py_compile apps/api/src/services/awooop_truth_chain_service.py apps/api/src/services/incident_timeline_service.py apps/api/src/services/telegram_gateway.py apps/api/tests/test_awooop_truth_chain_service.py apps/api/tests/test_telegram_message_templates.py`:pass。
|
||||
- `cd apps/api && ruff check --select F,E9 src/services/awooop_truth_chain_service.py src/services/incident_timeline_service.py src/services/telegram_gateway.py tests/test_awooop_truth_chain_service.py tests/test_telegram_message_templates.py`:pass。
|
||||
- `git diff --check`:pass。
|
||||
|
||||
**推版與 production 驗證**:
|
||||
- `f0bb3036 fix(awooop): surface auto repair verification state` 已推 Gitea main;Code Review run `2241` success;CD run `2240` success;deploy marker `a42e40a6 chore(cd): deploy f0bb303 [skip ci]`。
|
||||
- Production image:`awoooi-api` 與 `awoooi-worker` 均為 `192.168.0.110:5000/awoooi/api:f0bb3036556a1a3badc3961fca9aab0df00c6d6d`,rollout completed。
|
||||
- `https://awoooi.wooo.work/api/v1/health`:200 healthy,PostgreSQL / Redis / Ollama / OpenClaw / SigNoz all up。
|
||||
- Production pod 內部 truth-chain 查詢 `INC-20260513-79ED5E`:
|
||||
- `auto_repair_execution_records=1`、`successful_auto_repair_records=1`、`effective_execution_records=1`。
|
||||
- `latest_verification_result=degraded`。
|
||||
- mismatches 現在是 `incident_open_after_successful_execution` 與 `verification_degraded_after_auto_repair`。
|
||||
- 不再誤報 `approval_approved_without_execution_record` 或 `approval_no_action_without_execution`。
|
||||
- `automation_quality_verdict=auto_repaired_verification_degraded`。
|
||||
- Telegram runtime:兩個 API pod 中 1 個 leader `polling_active=true`、1 個 watcher `polling_active=false`;近 30 分鐘未見 409 polling conflict。重複 Alertmanager 告警有 `alertmanager_converged_telegram_skipped`,確認部分去重已在運作。
|
||||
|
||||
**目前整體進度**:
|
||||
- Alertmanager 低風險自動修復主線:約 98%。
|
||||
- 完整 AI 自動化管理產品化:約 99%。
|
||||
- 告警詳情/歷史/主卡/前端 deep-link 可追溯:約 99%。
|
||||
- Telegram approval / reject callback 閉環:約 95%。
|
||||
- Truth-chain 對「自動修復成功但驗證降級」的判讀:約 98%。
|
||||
- Telegram approval / reject callback 閉環:約 96%。
|
||||
- Truth-chain 對「自動修復成功但驗證降級」的判讀:約 99%。
|
||||
- 前端 AI 自動化管理介面同步:約 98%。
|
||||
- 待完成:推版部署後重查 `INC-20260513-79ED5E` truth-chain;另起技術債處理 188 `clawbot.service` restart loop、MOMO bot token log redaction、以及 stale open incident 的安全 reconciliation。
|
||||
- 待完成:另起技術債處理 188 `clawbot.service` restart loop、MOMO bot token log redaction / token rotation、remote URL credential hygiene,以及 stale open incident 的安全 reconciliation。
|
||||
|
||||
## 2026-05-17 | T37 Telegram Approval Callback 補上 executor handoff
|
||||
|
||||
|
||||
Reference in New Issue
Block a user