docs(logbook): record ansible dry-run Runs smoke [skip ci]

docs/LOGBOOK.md

@@ -19,6 +19,7 @@
 - Production health：`/api/v1/health` 回 `healthy / prod / mock_mode=false`。
 - Production status-chain readback：`/api/v1/platform/status-chain?project_id=awoooi&incident_id=INC-20260625-977E5F` 回 `verdict=ansible_check_mode_only`、`repair_state=ansible_check_mode_only`、`next_step=owner_review_apply_gate_or_create_verifier_plan`、`operator_outcome.state=dry_run_only_owner_review_required`、`completion_status=dry_run_completed_no_apply`、`command_status=check_mode_succeeded`、`repair_status=not_executed`、`ansible_dry_run_only=true`、`check_mode_total=1`、`apply_total=0`。
 - Production control readback：`INC-20260625-66086A` 仍維持 `manual_required_no_action`、`repair_state=manual_required`、`operation_total=0`，未被本段誤標成 dry-run 或已修復。
+- Production Runs metrics smoke：`/zh-TW/awooop/runs?project_id=awoooi&_v=420b0b18-ansible-dry-run-prod-desktop` 與 mobile URL 均載入 `AwoooP` / `Runs`；console error `0`、HTTP failed response `0`、`horizontalOverflow=0`。本輪 screenshot 因 Playwright 等待字型載入逾時，僅採 metrics-only smoke，不宣稱有截圖證據。
 
 **完成度同步**：
 - Ansible check-mode truth-chain 語意修正：`100%`。