docs(logbook): 記錄處置結果契約部署 [skip ci]

This commit is contained in:
Your Name
2026-05-31 16:02:47 +08:00
parent a28f84722b
commit aa47f4bc31
2 changed files with 28 additions and 0 deletions

View File

@@ -78,6 +78,33 @@ git diff --check
-> pass
```
**Production 驗證**
```text
Gitea:
run 3354 tests -> success
run 3354 build-and-deploy -> success
run 3354 post-deploy-checks -> success
run 3355 ai-code-review -> success
deploy marker -> a28f8472 chore(cd): deploy e9a8a2b [skip ci]
K8s:
awoooi-api -> 192.168.0.110:5000/awoooi/api:e9a8a2b3e90064afbae638b83c3854ac22f7bb25 2/2
awoooi-web -> 192.168.0.110:5000/awoooi/web:e9a8a2b3e90064afbae638b83c3854ac22f7bb25 2/2
awoooi-worker -> 192.168.0.110:5000/awoooi/api:e9a8a2b3e90064afbae638b83c3854ac22f7bb25 1/1
Health:
/api/v1/health -> healthy, prod, mock_mode=false
Smoke:
/api/v1/platform/status-chain?project_id=awoooi&incident_id=INC-20260530-88D960
operator_outcome.state=diagnostic_only_manual_review
summary_zh=只完成診斷/觀察,尚未證明修復
needs_human=true
notification.channels=telegram_sre_war_room,awooop_operator_console
API pod truth-chain readback:
INC-20260530-88D960 -> diagnostic_only_manual_review, needs_human=true
INC-20260531-BE2B25 -> execution_failed_manual_required, needs_human=true
INC-20260531-88394F -> diagnostic_only_manual_review, needs_human=true
```
**進度邊界**
- 本輪補齊「結果語意與通知契約」,不是新增更高權限的自動修復能力。

View File

@@ -2689,6 +2689,7 @@ Phase 6 完成後
- 修正:新增 `operator_outcome_v1` 共用契約,集中輸出 `state``summary_zh``needs_human``human_action_required``human_action_reason``next_action``notification.channels``evidence``blockers`。AwoooP truth-chain、platform status-chain、Telegram 首屏、Telegram callback snapshot 與前台 status-chain 全部讀同一份 outcome。approval execution result 改在最終驗證、AOL / KM / incident log 寫入後送出;若缺原始 Telegram message id改送 standalone 群組結果通知並寫 `TELEGRAM_RESULT_SENT`,不再靜默失聯。
- 語意收斂:`OBSERVE` / `NO_ACTION` / diagnostic / parse_failed / unsupported_action 會寫入 `execution_kind``repair_executed=false``repair_attempted=false`。diagnostic-only、verification degraded、execution failed、read-only dry-run、write-observed、blocked、PENDING / WAITING_APPROVAL 都會明確標示人工需求、通知通道與下一步,不再把診斷或觀察顯示成修復完成。
- VerificationAPI `py_compile` passi18n JSON parse passtargeted `ruff --select E9,F401,F821,F841` pass`test_approval_execution_no_action.py` + `test_operator_outcome.py` + `test_awooop_truth_chain_service.py` + `test_awooop_operator_timeline_labels.py` + `test_telegram_message_templates.py` + `test_incident_timeline_service.py` -> 161 passedweb `tsc --noEmit` passproduction API URL build pass`git diff --check` pass。
- ProductionGitea run 3354 tests/build-and-deploy/post-deploy successrun 3355 ai-code-review successdeploy marker `a28f8472 chore(cd): deploy e9a8a2b [skip ci]`。K8s API/Web/Worker image 均為 `e9a8a2b3e90064afbae638b83c3854ac22f7bb25` 且 ready`/api/v1/health` healthy/prod/mock_mode=false。Production `/api/v1/platform/status-chain?project_id=awoooi&incident_id=INC-20260530-88D960``operator_outcome.state=diagnostic_only_manual_review``summary_zh=只完成診斷/觀察,尚未證明修復``needs_human=true``notification.channels=telegram_sre_war_room,awooop_operator_console`API pod truth-chain readback confirms `INC-20260531-BE2B25 -> execution_failed_manual_required`
- 判讀T154c 補的是「operator-facing disposition contract」與「result notification reliability」不是擴權自動修復。新版後新 incident 的批准結果會落到 Telegram / DB / AwoooP 同一份 outcome歷史全量補發需另開 backfill避免一次洗版。
**T152 Ansible runtime readiness surfaced2026-05-24 台北)**