From 4a24d3e4fcd9bcaf644a7ed2c59a3059dd3dc464 Mon Sep 17 00:00:00 2001
From: Your Name <you@example.com>
Date: Wed, 20 May 2026 10:38:02 +0800
Subject: [PATCH] docs(governance): record t98 archive history rollout [skip
 ci]

---
 docs/LOGBOOK.md                               | 38 ++++++++++++++++++-
 ...-04-15-MASTER-ai-autonomous-flywheel-v2.md |  2 +-
 2 files changed, 38 insertions(+), 2 deletions(-)

diff --git a/docs/LOGBOOK.md b/docs/LOGBOOK.md
index 60a53352..d0258f29 100644
--- a/docs/LOGBOOK.md
+++ b/docs/LOGBOOK.md
@@ -75,7 +75,43 @@ Screenshot:
 **Production deploy / smoke**：
 
 ```text
-Pending：推 Gitea main 後驗證 dedupe API group 已含 archive_history key，並以 production Work Items 確認頁面無 console / page error。
+Code commit:
+  edb6daef feat(governance): attach km archive history to dedupe groups
+
+Deploy marker:
+  e7691a1f chore(cd): deploy edb6dae [skip ci]
+
+Gitea Actions:
+  2567 CD -> tests success / build-and-deploy success / post-deploy-checks success
+  2568 Code Review -> success
+  2569 Type Sync -> success
+
+GET https://awoooi.wooo.work/api/v1/health
+  -> healthy, prod, mock_mode=false
+
+GET /api/v1/ai/governance/km-review-drafts/dedupe?limit=100
+  -> schema_version=km_review_draft_dedupe_v1
+  -> total_review_drafts=100
+  -> event_group_total=47
+  -> duplicate_draft_total=53
+  -> groups=47
+  -> groups_with_archive_history_key=47
+  -> groups_with_non_empty_archive_history=0
+
+Work Items production smoke:
+  -> navVisible=true
+  -> kmPanelVisible=true
+  -> dedupeVisible=true
+  -> historyVisible=true
+  -> emptyVisible=true
+  -> historyRowVisible=false
+  -> consoleErrors=0
+  -> pageErrors=0
+  -> failedResponses=[]
+  -> screenshot=/tmp/awoooi-t98-km-archive-history-group-production.png
+
+Boundary:
+  -> groups_with_non_empty_archive_history=0 / historyRowVisible=false 是目前正確狀態，因為本輪沒有對 production KM 做 owner confirm 封存；只要後續 owner confirm 寫入 archive / recheck dispatch，dedupe group 自己會帶出 history row，不再依賴 queue size=20。
 ```
 
 **目前整體進度**：
diff --git a/docs/superpowers/specs/2026-04-15-MASTER-ai-autonomous-flywheel-v2.md b/docs/superpowers/specs/2026-04-15-MASTER-ai-autonomous-flywheel-v2.md
index 7a01c233..078a0679 100644
--- a/docs/superpowers/specs/2026-04-15-MASTER-ai-autonomous-flywheel-v2.md
+++ b/docs/superpowers/specs/2026-04-15-MASTER-ai-autonomous-flywheel-v2.md
@@ -2365,7 +2365,7 @@ Phase 6 完成後
 - UI：Work Items 前端優先讀 `group.archive_history`；若 API 尚未升級或 group 無 history，再 fallback 到 T97 的 queue item 匹配。這把「封存 / 回測歷史」從旁路分頁猜測改成 dedupe group 自帶證據。
 - 邊界：T98 仍是 read-only read model，不自動寫 KM、不封存 production KM、不改 owner approval / fingerprint guard。
 - Local verification：`py_compile` ok；ruff ok；治理 endpoint 單檔 `39 passed`；治理 endpoint / dispatcher / Hermes worker tests `62 passed`；Work Items Next lint ok；`tsc --noEmit` ok；i18n JSON parse ok；shared-types regenerate 後無 diff；production build 成功產出 90/90 static pages；`git diff --check` pass。Local Playwright live production API bridge 對 dedupe response 注入 1 筆 archive_history row，確認 `Hermes：owner 確認封存` 與 fingerprint 顯示，blockedWrites=0，截圖 `/tmp/awoooi-t98-km-archive-history-row-local.png`。
-- Production：pending，推 Gitea main 後驗證 dedupe API group 已含 archive_history key，並以 production Work Items 確認頁面無 console / page error。
+- Production：`edb6daef feat(governance): attach km archive history to dedupe groups` 已推 Gitea main；deploy marker `e7691a1f chore(cd): deploy edb6dae [skip ci]`；Gitea runs `2567` CD、`2568` Code Review、`2569` Type Sync 全 success。Production health healthy/prod/mock_mode=false。`GET /ai/governance/km-review-drafts/dedupe?limit=100` 回 `total_review_drafts=100`、`event_group_total=47`、`duplicate_draft_total=53`、`groups=47`、`groups_with_archive_history_key=47`、`groups_with_non_empty_archive_history=0`。Work Items production smoke 顯示 nav、KM healthcheck panel、KM 草稿去重視圖、封存 / 回測歷史區塊與 empty state，pageErrors=0 / consoleErrors=0 / failedResponses=[]，截圖 `/tmp/awoooi-t98-km-archive-history-group-production.png`。目前 non-empty history 為 0 是正確狀態，因為本輪沒有對 production KM 做 owner confirm 封存；只要後續 owner confirm 寫入 archive / recheck dispatch，dedupe group 自己會帶出 history row，不再依賴 queue size=20。
 - 目前進度更新：前端 AI 自動化管理介面同步約 98.7%；治理告警可讀性 / 可處置性約 99.0%；AI Agent ownership 可追溯性約 98.2%；KM healthcheck 派工可追蹤性約 99.7%；Hermes KB growth 草稿 / owner review 閉環約 99.6%；完整 AI 自動化管理產品化約 97.5%。
 
 ---