docs(logbook): record ai loop remote-control blocker [skip ci]

This commit is contained in:
Your Name
2026-07-01 09:58:12 +08:00
parent 0ed2017a4d
commit 9a1be01ce3

View File

@@ -1,3 +1,21 @@
## 2026-07-01 — 09:52 AI Loop LOG writeback current P0 blocker 對齊
**照主線修正的問題**
- live queue 已前進到 CD `#4218 Failure`、Harbor repair `#4216 Failure``controlled_profile_no_matching_runner_label_count=0`,現行 blocker 不是 no-matching runner而是 `harbor_110_remote_control_channel_unavailable``remote_ssh_reachable=false``bounded_ssh_timeout_seen=true`、Harbor `/v2/``502`
- `docs/operations/ai-agent-log-intelligence-runtime-sample-readback.snapshot.json` 的 P0 runtime sample 改為 `gitea_queue_and_remote_control_classifier_readback`current blocker 對齊 `harbor_110_remote_control_channel_unavailable` / `bounded_ssh_timeout`,保留 metadata-only、no raw log、no secret 邊界。
- `ai_agent_log_controlled_writeback_plan_readback` 將 remote-control-unavailable 納入 110 local-console controlled apply requirement不再只支援舊 `harbor_110_repair_no_matching_runner`
- `ai_agent_log_controlled_writeback_executor_readback` 新增 `remote_control_channel_readback` / `local_console_recovery_output` receipt input並把 `latest_visible_harbor_110_repair_remote_control_channel_unavailable` 納入 queue normalizer contract讓 KM / RAG / PlayBook / MCP / verifier / AI Agent 都學到現行 blocker。
- AwoooP / AI Agent 的 priority work order 與 autonomous runtime tests 已同步期望新的 current P0 blocker避免 Work Items / Runs / Approvals 繼續顯示過期 no-matching runner 終局。
**驗證**
- `DATABASE_URL=... python3.11 -m pytest apps/api/tests/test_ai_agent_log_intelligence_integration_readback_api.py apps/api/tests/test_ai_agent_log_feedback_receipt_dry_run_api.py apps/api/tests/test_ai_agent_log_controlled_writeback_plan_readback_api.py apps/api/tests/test_ai_agent_log_controlled_writeback_executor_readback_api.py apps/api/tests/test_ai_agent_autonomous_runtime_control.py apps/api/tests/test_awoooi_priority_work_order_readback_api.py -q``29 passed`
- `python3.11 -m pytest ops/runner/test_read_public_gitea_actions_queue.py -q``32 passed`
- `DATABASE_URL=... python3.11 -m pytest apps/api/tests/test_harbor_registry_controlled_recovery_receipt.py ops/runner/test_verify_awoooi_non110_cd_closure.py -q``27 passed`
- `py_compile``ruff check`、JSON parse、`ops/runner/guard-gitea-runner-pressure.py --root .``git diff --check`:通過。
- 188 remote verifier 讀回 `AWOOOI_NON110_RUNNER_READY=1``BLOCKER_COUNT=0`public route readback 仍是 `registry.wooo.work/v2=502``harbor.wooo.work/api/v2.0/health=502`、110 SSH timeout。
**邊界**:只改 AI Loop metadata/source-of-truth、API readback、tests 與 runtime sample未讀 secret / token / `.env` / raw sessions / SQLite / auth未讀 `.runner` 內容;未使用 GitHub / `gh` / GitHub API未 workflow_dispatch未重啟主機、未 restart Docker / Nginx / K3s / DB / firewall未執行 KM/RAG/PlayBook/MCP live write。
## 2026-07-01 — 09:47 Harbor remote repair schedule / SSH timeout pressure guard
**照主線修正的問題**