fix(agent): prioritize harbor ai loop blocker

This commit is contained in:
Your Name
2026-07-01 12:50:53 +08:00
parent ce5bcab8b5
commit 4b5f8ea537
3 changed files with 63 additions and 5 deletions

View File

@@ -1,3 +1,17 @@
## 2026-07-01 — 12:50 Priority work order AI Loop blocker 優先權修正
**照主線修正的問題**
- Production `/api/v1/agents/awoooi-priority-work-order-readback` 仍把 `p0_006_blocked_stockplatform_public_api_runtime_drift` 當第一訊號,`ai_loop_current_blocker_id=null`;但目前 main/CD 的實際阻塞是 Harbor deploy marker 被 110 SSH / Harbor registry blocker 擋住。
- `apply_ai_loop_current_blocker_execution_queue` 原本只在 `p0_006_blocked_harbor_registry_controlled_recovery_preflight` 之後才 overlay若 StockPlatform live drift 先寫入 statusAI Loop current blocker queue 就不會上到第一訊號。
- 本次改成:當 status 是 `p0_006_blocked_stockplatform_public_api_runtime_drift` 且 AI Loop blocker 以 `harbor_110_` 開頭時,允許 AI Loop current blocker 覆蓋 priority board 的第一訊號StockPlatform evidence 仍保留,但不再蓋住 Harbor/110 deploy blocker。
- 新增測試固定此行為:先套 StockPlatform drift再套 AI Loop executor最後 status 必須是 `p0_006_blocked_ai_loop_current_blocker_execution_queue`next execution order 必須從 AI Loop current blocker 開始。
**驗證**
- `DATABASE_URL=... python3.11 -m pytest apps/api/tests/test_awoooi_priority_work_order_readback_api.py apps/api/tests/test_ai_agent_autonomous_runtime_control.py apps/api/tests/test_ai_agent_log_controlled_writeback_executor_readback_api.py -q``23 passed`
- `git diff --check`:通過。
**邊界**:只改 priority work order overlay 排序邏輯、測試與 LOGBOOK未讀 secret / token / `.env` / raw sessions / SQLite / auth未讀 authorized_keys 內容或 `.runner` 內容;未使用 GitHub / `gh` / GitHub API未 workflow_dispatch未重啟主機、未 restart Docker / Nginx / K3s / DB / firewall未執行 runtime apply。
## 2026-07-01 — 12:38 110 SSH local metadata receipt 擴充
**照主線修正的問題**