wooo/awoooi
1
1
Fork 0
Code Issues 2 Pull Requests 1 Actions 2 Packages Projects Releases Wiki Activity

feat(agent): project ai loop blocker into work order
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
Details
CD Pipeline / cancel-stale-cd (push) Has been skipped
Details
CD Pipeline / tests (push) Successful in 35s
Details
CD Pipeline / post-deploy-checks (push) Has been cancelled
Details
CD Pipeline / build-and-deploy (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Your Name
2026-06-30 22:47:22 +08:00
parent 7be629d733
commit 2736ca9149
4 changed files with 243 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/LOGBOOK.md
View File

@@ -50810,3 +50810,23 @@ production browser smoke:
**下一步**：
- commit / push 後等待 Gitea CD；若 runtime 仍卡 Harbor / 110，P0 主線仍是恢復 110 `awoooi-host` controlled lane 或 110 local recovery package，再重讀 registry `/v2/`、full-stack cold-start、Stock freshness、backup core 與 SLO scorecard。
## 2026-06-30 — 22:46 AI Loop current blocker queue 投影到主線工作順序
**完成內容**：
- `awoooi-priority-work-order-readback` 新增 AI Loop current blocker overlay：當 Harbor / 110 preflight 已成為 P0 blocker，且 `agent-log-controlled-writeback-executor-readback` 有 `current_blocker_execution_queue` 時，主線工作順序會改投影為 `P0-006-AI-LOOP-CURRENT-BLOCKER-EXECUTION-QUEUE`。
- P0 evidence 現在直接帶出 `harbor_110_repair_no_matching_runner`、`awoooi-host`、`publickey_offer_timeout`、`recover-110-control-path-and-harbor-local.sh --check`、`check-awoooi-110-controlled-cd-lane-readiness.sh`、6 個 KM/RAG/MCP/PlayBook/verifier/AI Agent writeback targets、metadata-only / no raw payload boundary。
- `/api/v1/agents/awoooi-priority-work-order-readback` 接上 `load_latest_ai_agent_log_controlled_writeback_executor_readback()`，讓工作順序頁與 AI Loop executor 不再分裂：AI Agent 看得到的 current blocker queue，P0 work-order 也看得到。
**本地驗證結果**：
- `DATABASE_URL=postgresql+asyncpg://test:test@localhost:5432/test PYTHONPATH=apps/api python3.11 -m pytest apps/api/tests/test_awoooi_priority_work_order_readback_api.py apps/api/tests/test_harbor_registry_controlled_recovery_preflight.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_ai_agent_autonomous_runtime_control_api.py ops/runner/test_read_public_gitea_actions_queue.py -q`：`48 passed`。
- `ruff check`、`py_compile`、`ops/runner/guard-gitea-runner-pressure.py --root .`、`scripts/ci/check-gitea-step-env-secrets.js`、`git diff --check`：通過。
- 本地 payload 摘要：`status=p0_006_blocked_ai_loop_current_blocker_execution_queue`、`next_workplan=P0-006-AI-LOOP-CURRENT-BLOCKER-EXECUTION-QUEUE`、`queue_count=1`。
**live truth**：
- Gitea latest CD `#4102` 正在跑 `b474f80c6`；`harbor-110-local-repair` `#4099` 仍 Waiting，no matching label `awoooi-host`。
- `https://registry.wooo.work/v2/` 與 `https://harbor.wooo.work/api/v2.0/health` 仍回 502。
- 本輪未執行 runtime write、workflow dispatch、host restart、Docker / K3s / Nginx reload、secret / runner token 讀取。
**下一步**：
- commit / push 後等待 CD；若仍卡 Harbor / 110，主線下一步不變：恢復 110 `awoooi-host` controlled lane 或在 110 local console / root shell 執行 recovery package check-mode，再重讀 Harbor queue、registry `/v2/`、deploy marker，並把 post-apply verifier receipt 回寫到 AI Loop。