diff --git a/docs/LOGBOOK.md b/docs/LOGBOOK.md
index 5f00de9b..33522e80 100644
--- a/docs/LOGBOOK.md
+++ b/docs/LOGBOOK.md
@@ -6456,3 +6456,52 @@ DATABASE_URL='postgresql+asyncpg://awoooi:awoooi_test_2026@localhost:5432/awoooi
 
 - 推 Gitea main，等待 CD 部署。
 - production rollback smoke：呼叫 `record_mcp_call()`，確認同一 transaction 內同時可見 legacy `mcp_audit_log` 與 `awooop_mcp_gateway_audit` bridge row，rollback 後不污染 production。
+
+**production deploy / smoke 追加（完成）**：
+
+```text
+Gitea:
+1921 CD Pipeline 94d006ea -> success
+  tests -> success
+  build-and-deploy -> success
+  post-deploy-checks -> success
+1922 Code Review 94d006ea -> success
+
+K8s image:
+awoooi-api    192.168.0.110:5000/awoooi/api:94d006eac88fd65f6efca817eb392a103ec10d3f
+awoooi-worker 192.168.0.110:5000/awoooi/api:94d006eac88fd65f6efca817eb392a103ec10d3f
+awoooi-web    192.168.0.110:5000/awoooi/web:94d006eac88fd65f6efca817eb392a103ec10d3f
+
+rollout:
+deployment "awoooi-api" successfully rolled out
+
+health:
+http://192.168.0.125:32334/api/v1/health -> 200 healthy
+```
+
+**T2 bridge rollback smoke**：
+
+```text
+legacy_visible_in_tx=1
+bridge_visible_in_tx=1
+bridge_tool_name=legacy:ssh_host:ssh_get_docker_logs
+bridge_result_status=success
+bridge_policy_enforced=false
+bridge_not_used_reason=legacy direct provider path; bridge audit only
+bridge_legacy_mcp_server=ssh_host
+rollback_triggered=true
+legacy_persisted_after_rollback=0
+bridge_persisted_after_rollback=0
+```
+
+**live 注意事項**：
+
+- 部署後觀察窗口內沒有自然發生新的 legacy MCP call：
+
+```text
+legacy_mcp_15m=0 legacy_mcp_5m=0 latest=2026-05-12 15:34:40+00:00
+gateway_audit_total=0 last_15m=0 bridge_total=0
+```
+
+- 因此目前只能宣稱「T2 bridge 寫入能力已部署並經 rollback smoke 驗證」。
+- 尚不能宣稱「所有 MCP / 自建 MCP 都已完全經 AwoooP Gateway 強制治理」；下一段要讓下一個真實 incident / MCP 呼叫自然產生 durable bridge row，或把高頻 caller 改成 first-class `McpGateway`。
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 bc3c1251..15f6a18c 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
@@ -1879,8 +1879,12 @@ Phase 6 完成後
 - MCP gateway / audit 聚焦測試 7 passed。
 - PreDecision / PostExecution / Callback / Approval MCP audit 相鄰流程測試 90 passed。
 
+**production 追加**：
+- T2 bridge image `94d006ea` 已部署，CD run `1921` success，health 200。
+- rollback smoke 證明 `record_mcp_call()` 在同一 transaction 內會同時寫 legacy `mcp_audit_log` 與 `awooop_mcp_gateway_audit` bridge row，且 bridge row 標示 `policy_enforced=false` / `not_used_reason=legacy direct provider path; bridge audit only`；rollback 後兩邊皆未污染 production。
+- 部署後短觀察窗內沒有自然新 legacy MCP call（`legacy_mcp_15m=0`），所以 live `awooop_mcp_gateway_audit` total 仍是 0。T2 bridge capability 已上線，但 T2 全退出條件仍需下一個真實 MCP 呼叫產生 durable row，或把高頻 caller 改成 first-class Gateway path。
+
 **仍未宣稱完成**：
-- T2 API image 尚需部署後 production rollback smoke。
 - 這只是 legacy bridge，不是把所有呼叫強制改經 AwoooP Gateway；T2 後續仍要把新 MCP caller 收斂到 first-class Gateway path。
 
 ---