fix(runner): surface harbor repair closure blocker

docs/LOGBOOK.md

@@ -1,3 +1,18 @@
+## 2026-06-30 — 21:23 Harbor 110 repair `awoooi-host` runner blocker closure readback
+
+**照主線修正的問題**：
+- Live public queue 已由 `4ccd800c1` 的 reader 回 `status=blocked_harbor_110_repair_no_matching_runner`：最新 CD `#4075` running，Harbor repair `#4076` Waiting，`latest_visible_harbor_110_repair_no_matching_runner_label=awoooi-host`，registry public / internal `/v2/` 仍為 502。
+- 現有 `verify-awoooi-non110-cd-closure.py` 雖讀到 queue status，仍降級成 generic `blocked_no_matching_online_runner`；本輪新增專用 closure blocker `harbor_110_repair_no_matching_runner` 與 next action `restore_awoooi_host_runner_control_path_without_legacy_or_generic_labels_then_rerun_harbor_110_repair_queue_readback`。
+- Live closure verifier 現在回 `status=blocked_harbor_110_repair_no_matching_runner`、`ordered_completion_percent=33`、`evidence_completion_percent=67`；下一步明確是恢復 `awoooi-host` 110 repair control path，而不是泛化重跑 queue 或宣稱 Harbor repair 成功。
+
+**驗證**：
+- `py_compile ops/runner/verify-awoooi-non110-cd-closure.py ops/runner/test_verify_awoooi_non110_cd_closure.py` 通過。
+- `pytest ops/runner/test_verify_awoooi_non110_cd_closure.py -q` 通過（8 passed）。
+- `ruff check ops/runner/verify-awoooi-non110-cd-closure.py ops/runner/test_verify_awoooi_non110_cd_closure.py` 通過。
+- Live `verify-awoooi-non110-cd-closure.py --json` 回專用 `blocked_harbor_110_repair_no_matching_runner`，且 operation boundaries 全部維持 no-write / no-secret / no-dispatch。
+
+**邊界**：只改 closure verifier / tests / LOGBOOK；110 SSH read-only metadata probe timeout 後已中止，未讀 `.runner`、secret、token、`.env`、raw sessions、SQLite 或 auth；未使用 GitHub / `gh` / GitHub API；未 workflow_dispatch；未 SSH 寫入、Docker / Nginx / K3s / DB / firewall runtime 寫入或服務重啟。
+
 ## 2026-06-30 — 21:13 Priority work-order readback 對齊 reboot SLO fail-closed 真相
 
 **照主線修正的問題**：