docs(logbook): record non110 runtime reenable [skip ci]

docs/LOGBOOK.md

@@ -1,3 +1,16 @@
+## 2026-07-01 — 09:18 non-110 runner runtime re-enable / queue no-matching cleared
+
+**照主線修正的問題**：
+- 推送 `eaa6cf4df docs(logbook): record harbor non110 readback [skip ci]` 後，public Gitea queue 短暫反彈為 `controlled_profile_no_matching_runner_label_count=12`，`harbor-110-local-repair.yaml` / `cd.yaml` 均顯示 `awoooi-non110-*` no-matching。
+- 188 metadata readback 顯示 `awoooi-non110-runner.service`、`awoooi-non110-runner-keepalive.timer` 均為 `inactive / disabled`，但 config / binary / `.runner` metadata 仍存在、`active_action_containers=0`、host load 正常，符合低爆炸半徑 controlled apply。
+- 對 188 執行 `AWOOOI_NON110_ENABLE=1 bash -s -- --enable < ops/runner/install-awoooi-non110-runner-user-service.sh`，讀回 `SERVICE_ENABLE_PERFORMED=1`、`SERVICE_START_PERFORMED=1`、`KEEPALIVE_TIMER_ENABLE_PERFORMED=1`、`runner_token_read=false`、`raw_runner_registration_read=false`。
+
+**驗證**：
+- 188 verifier 回 `AWOOOI_NON110_RUNNER_READY=1`、`BLOCKER_COUNT=0`、`READY_ACTIVE_SERVICE_COUNT=1`、`READY_KEEPALIVE_TIMER_COUNT=1`，service / keepalive timer 均為 `ActiveState=active`、`UnitFileState=enabled`。
+- live public queue 回 `workflow_no_matching={}`、`controlled_profile_no_matching_runner_label_count=0`、`latest_visible_harbor_110_repair_no_matching_runner_label=""`；目前狀態前進為 `harbor_110_repair_jobs_stale_or_mismatched`，不再是 runner label no-matching。
+
+**邊界**：未讀 token / secret / `.env` / raw sessions / SQLite / auth，未讀 `.runner` 內容，未使用 GitHub / `gh` / GitHub API，未 workflow_dispatch，未重啟主機、未 restart Docker / Nginx / K3s / DB / firewall；本輪 runtime 寫入限於 188 user-level runner service enable / start 與 keepalive timer enable。
+
 ## 2026-07-01 — 09:14 non-110 runner controlled apply / Harbor remote control-channel / B5 Docker socket fail-fast
 
 **照主線修正的問題**：