docs(governance): record t21 verifier coverage rollout

This commit is contained in:
Your Name
2026-05-14 20:39:56 +08:00
parent b1893395f0
commit dd269b195c
2 changed files with 56 additions and 0 deletions

View File

@@ -2151,6 +2151,15 @@ Phase 6 完成後
- Production evidenceAPI / Worker / Web image 均為 `809bc9670b9fde034bc1fc0cd6bc5575c1bea8f0``/api/v1/ai/slo``overall_status=partial``overall_compliance=1.0`、三個 ratio SLO `skipped_low_volume``km_growth_rate=ok,value=24``/zh-TW/governance` 200。
- 目前進度更新Alertmanager 低風險自動修復主線約 96%;完整 AI 自動化管理產品化約 84%。下一段補 verifier coverage / post-execution verification freshness讓 decision accuracy 有自動執行事件時能快速產生可評估樣本。
**T21 Post-execution verifier coverage 前端化2026-05-14 台北)**
- 觸發T20 已能呈現 Prometheus SLO 的低樣本語意,但 Operator 仍無法直接看出近 24h 自動修復是否都有 `incident_evidence.verification_result`、是否有未驗證 backlog、以及驗證結果是否多數為 degraded/failed/timeout。
- 修正:`adr100_slo_status_service.py` 追加 read-only PostgreSQL coverage read model`/api/v1/ai/slo``adr100.verification_coverage` 回傳 `total_auto / verified_auto / unverified_auto / verified_success / verified_non_success / coverage_rate / verification_success_rate / last_verified_auto_at / recent_unverified`
- UI`/governance` SLO tab 新增「驗證覆蓋率」面板,顯示自動修復、已驗證、待驗證、覆蓋率、成功驗證率與原因;`zh-TW` / `en` i18n 已補齊。
- 驗證py_compile pass`pytest tests/test_adr100_slo_status_service.py tests/test_adr100_slo_metrics_service.py tests/test_governance_agent.py tests/test_ai_governance_endpoints.py -q` 53 passedruff F/E9 passweb typecheck / target lint / production build passi18n JSON parse / diff check passPlaywright production render check console error = 0。
- Production deploy`485c58d0 feat(governance): surface verification coverage` 已推 Gitea mainCode Review run `2169` successCD run `2168` tests / build-and-deploy / post-deploy-checks successdeploy marker `b1893395 chore(cd): deploy 485c58d [skip ci]`
- Production evidenceAPI / Worker / Web image 均為 `485c58d0852dd308f15da9259ae453d3dbf0b28e``/api/v1/ai/slo``adr100.overall_status=warning``overall_compliance=1.0``verification_coverage.status=warning``reason=non_success_verification_present``total_auto=14``verified_auto=14``unverified_auto=0``verified_success=5``verified_non_success=9``coverage_rate=1.0``/zh-TW/governance` 200。
- 目前進度更新Alertmanager 低風險自動修復主線約 96%;完整 AI 自動化管理產品化約 86%。下一段 T22 應拆解 9 筆 non-success verification 的根因,讓 degraded/failed/timeout 進入工作鏈路、Ticket、PlayBook/KM 修復項,而不是只停在 warning。
---
### 2026-04-20 晚 (台北) — C1-C4 全流程串接 — Playbook 鏈路保護commit de2d34d