From 42fd9827f5b5ea2ac264cf2eac2da1655c94ad3f Mon Sep 17 00:00:00 2001 From: Your Name Date: Sun, 31 May 2026 14:47:07 +0800 Subject: [PATCH] docs(logbook): update ansible check-mode production counts [skip ci] --- docs/LOGBOOK.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/LOGBOOK.md b/docs/LOGBOOK.md index cd07f380..5b5fae34 100644 --- a/docs/LOGBOOK.md +++ b/docs/LOGBOOK.md @@ -45,8 +45,14 @@ truth-chain summary: DB / worker evidence: ansible_candidate_matched dry_run=166 - ansible_check_mode_executed failed=8 - latest 2 rows: + ansible_check_mode_executed success=1, failed=9 + truth-chain execution_backend_summary: + ansible_check_mode_total=10 + ansible_apply_total=0 + ansible_pending_check_mode_total=2 + latest rows: + INC-20260530-B4A7BD -> ssh_mcp, ansible:110-devops, check_mode_executed=true, apply_executed=false, rc=0 + INC-20260530-0DD83C -> ssh_mcp, ansible:188-ai-web, check_mode_executed=true, apply_executed=false, rc=2 INC-20260530-0E5C5C -> ssh_mcp, ansible:188-ai-web, check_mode_executed=true, apply_executed=false, rc=2 INC-20260530-B37FB4 -> ssh_mcp, ansible:188-ai-web, check_mode_executed=true, apply_executed=false, rc=2 failure reason: @@ -56,7 +62,7 @@ DB / worker evidence: **判讀 / 下一步**： - 這不是 auto-repair 完成；apply 仍鎖住，`ansible_apply_total=0`，production full auto-repair claim 仍為 false。 -- 已完成的是「AwoooP 能把 AI 候選修復接到 Ansible check-mode 並寫入 DB 證據」；下一個真 blocker 是 188 的受控 sudo / become 策略。 +- 已完成的是「AwoooP 能把 AI 候選修復接到 Ansible check-mode 並寫入 DB 證據」；110 已有成功 check-mode，下一個真 blocker 是 188 的受控 sudo / become 策略。 - 不建議直接給 `ollama` 無限制 NOPASSWD；下一步應二選一： - 建立專用 Ansible check-mode 帳號與最小 sudoers，只允許 catalog 需要的 read/check 操作。 - 或拆出 188 read-only check-mode playbook，無 sudo 先覆蓋 Docker / app 層觀測，root-owned drift 仍轉人工審批。