docs(awooop): record t127 production readback [skip ci]

This commit is contained in:
Your Name
2026-05-21 14:12:03 +08:00
parent 39f0f7655c
commit e89bb267ea
2 changed files with 70 additions and 0 deletions

View File

@@ -2603,6 +2603,12 @@ Phase 6 完成後
- Verificationmessages JSON parse ok`pnpm --filter @awoooi/web typecheck` passscoped `next lint --file src/app/[locale]/awooop/runs/page.tsx --file src/components/awooop/status-chain.tsx` exit 0runs/page.tsx 既有 literal-string warnings 仍存在);`NEXT_PUBLIC_API_URL=https://awoooi.wooo.work pnpm --filter @awoooi/web build` compiled successfully90/90 static pages generated。Local Browser 已看到 Runs list 新 `來源流程`local CORS proxy 未完成 status-chain fetch因此以 CD 後 production same-origin readback 收斂。`9c966699 feat(awooop): show source flow in runs list` 已推 Gitea maindeploy marker `9206e271 chore(cd): deploy 9c96669 [skip ci]`。Actions #2750 Code Review success#2749 CD tests / build-and-deploy / post-deploy-checks successproduction Runs list row for `INC-20260505-25E744` 顯示 `已驗證``providers=1; d/c/a=1/0/1`
- 目前進度更新AwoooP 告警可觀測鏈約 99.998%Incident-level source correlation 可見性約 98.3%Source correlation apply 狀態鏈可驗證性約 99.72%Source correlation freshness / rolling gate 約 98.2%;前端 AI 自動化管理介面同步約 99.994%;完整 AI 自動化管理產品化約 99.90%。
**T127 Work Items source flow summary2026-05-21 台北)**
- 觸發T126 已把 source flow 拉到 Runs list但 operator 從 Telegram / recurrence 工作項進 `/awooop/work-items` 時,仍只能看到 source refs 與 source review/apply count無法在工作項卡片上直接判斷流程停在哪一段。
- 修正:`apps/web/src/app/[locale]/awooop/work-items/page.tsx` 在重複告警工作項卡片新增 `來源流程 / Source flow` 摘要,分類為 Applied、Review recorded、Awaiting match review、Source evidence found、Provider received、Waiting。資料完全取自既有 recurrence API 欄位:`source_correlation_apply``source_correlation_review``source_ref_total``sentry_ref_total``signoz_ref_total``latest_provider_event_id`;不新增 API、不新增 mock data。`apps/web/messages/en.json` / `zh-TW.json` 補齊 i18nUI 使用 lucide icons不新增 emoji icon。
- Verificationmessages JSON parse ok`git diff --check` pass`pnpm --filter @awoooi/web typecheck` passscoped `next lint --file src/app/[locale]/awooop/work-items/page.tsx` pass`NEXT_PUBLIC_API_URL=https://awoooi.wooo.work pnpm --filter @awoooi/web build` compiled successfully90/90 static pages generated。Local Browser 以 same-origin local proxy + production API 顯示 `來源流程:來源證據已到` 與 refs / Sentry / SignOz / provider event id。`ebb73af1 feat(awooop): show source flow in work items` 已推 Gitea mainActions #2753 Code Review success#2752 CD tests / build-and-deploy / post-deploy-checks successdeploy marker `39f0f765 chore(cd): deploy ebb73af [skip ci]`。Production Browser readback`/zh-TW/awooop/work-items?project_id=awoooi&incident_id=INC-20260521-A02D7D` 顯示 `來源流程:來源證據已到``refs=116; Sentry=0; SignOz=0; event=alertmanager:received:alert-20260521141001:be6a1821f6336fa44b5ec33855b9f23d`,同頁也顯示 DockerContainerMemoryLimitPressure / GiteaMemoryPressure source flow。既有 dashboard SSE snapshot fetch warning 仍存在,列為前端全域技術債,不阻塞 T127。
- 目前進度更新AwoooP 告警可觀測鏈約 99.998%Incident-level source correlation 可見性約 98.5%Source correlation apply 狀態鏈可驗證性約 99.72%Source correlation freshness / rolling gate 約 98.2%;前端 AI 自動化管理介面同步約 99.996%;完整 AI 自動化管理產品化約 99.92%。
---
### 2026-04-20 晚 (台北) — C1-C4 全流程串接 — Playbook 鏈路保護commit de2d34d