docs(logbook): record 110 lane blocker readback

docs/LOGBOOK.md

@@ -50673,6 +50673,7 @@ production browser smoke:
 - `awoooi-cd-lane-drain.service` 與 `awoooi-startup-110.sh` 產生的 controlled drain unit 新增 `ConditionPathExists=/home/wooo/awoooi-cd-lane-drain/data/.runner`，避免 service active 但未註冊時假裝可承接 `awoooi-host` queue。
 - `ops/runner/verify-awoooi-non110-cd-closure.py` 的 Harbor 110 no-matching next action 改為先在 110 跑 `check-awoooi-110-controlled-cd-lane-readiness.sh`，通過後再恢復 `awoooi-host` control path 並重讀 queue/closure。
 - `recover-110-control-path-and-harbor-local.sh` 的 `--check` 串入 controlled lane verifier；`deploy-to-110.sh` 同步安裝 `/usr/local/bin/check-awoooi-110-controlled-cd-lane-readiness.sh`，讓 110 local console / root shell recovery 包同時涵蓋 SSH metadata、Harbor watchdog 與 `awoooi-host` lane readiness。
+- 推送後 live readback：`214f4c1e8` 已進 Gitea CD `#4085` running；Harbor repair `#4083` 仍 Waiting，`No matching online runner with label: awoooi-host`；`https://registry.wooo.work/v2/` 仍 502。外部嘗試以 bounded SSH 跑 verifier 失敗，port 22 TCP / banner 正常但 `wooo` publickey 分類為 `publickey_offer_timeout`，root 為 `permission_denied`，node-exporter OK 且 `NODE_LOAD_CLASSIFIER=load_not_high`，下一步仍是 110 local console / root shell 跑 recovery package。
 
 **本地驗證結果**：
 - `pytest ops/runner/test_check_awoooi_110_controlled_cd_lane_readiness.py ops/runner/test_verify_awoooi_non110_cd_closure.py ops/runner/test_cd_controlled_runtime_profile.py ops/runner/test_guard_gitea_runner_pressure.py scripts/reboot-recovery/tests/test_cold_start_monitor_bounded_probes.py -q`：`56 passed`。