feat(api): expose mainline priority order readback
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 1s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Successful in 29s
CD Pipeline / post-deploy-checks (push) Has been cancelled
CD Pipeline / build-and-deploy (push) Has been cancelled
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 1s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Successful in 29s
CD Pipeline / post-deploy-checks (push) Has been cancelled
CD Pipeline / build-and-deploy (push) Has been cancelled
This commit is contained in:
@@ -1,3 +1,14 @@
|
||||
## 2026-06-30 — 08:55 P0 mainline priority-order production readback
|
||||
|
||||
**照主線完成的實作**:
|
||||
- Gitea CD `#4012` 對 `88ac9c33d fix(ci): include deploy readback test in narrow cd profile` 已轉 `Success`;Gitea main 已有 deploy marker `b7bedc996 chore(cd): deploy 88ac9c3 [skip ci]`。
|
||||
- Production `/api/v1/agents/delivery-closure-workbench` 已讀回 `production_deploy_runtime_build_commit_short_sha=88ac9c33da`、`production_deploy_desired_main_api_image_tag_short_sha=88ac9c33da`、`production_deploy_desired_main_api_image_tag_readback_status=ok`、`production_deploy_image_tag_matches_main=true`。
|
||||
- Production `/api/v1/agents/gitea-workflow-runner-owner-attestation-request` 回 `200`,`/api/v1/agents/agent-log-controlled-writeback-consumer-readback` 回 `200 controlled_writeback_consumer_readback_ready`。
|
||||
- 新增 GET `/api/v1/agents/awoooi-priority-work-order-readback`,把 P0/P1 主線排序從本機 snapshot 提升為 production 可讀回 API;loader 會用 committed Delivery Workbench / P0-004 / P0-006 loaders 動態補齊目前狀態,避免舊 CD run 或舊 snapshot 重新打亂優先順序。
|
||||
- 目前 active P0 仍是 `P0-006`;P0-003 / P0-005 closed,P0-004 apply gate / template receipt / runtime enablement ready。P0-006 只剩 fresh all-host reboot event 或另行 break-glass reboot drill authorization,不得把一般「繼續」當成重啟授權。
|
||||
|
||||
**邊界**:未 workflow_dispatch,未重啟主機,未 restart Docker / K3s / Nginx / DB / firewall,未寫 K8s / DB,未讀 secret / token / raw sessions / SQLite / `.env`,未使用 GitHub / `gh` / GitHub API。
|
||||
|
||||
## 2026-06-30 — 08:19 API bootstrap controlled startup unblock
|
||||
|
||||
**照主線完成的實作**:
|
||||
@@ -50030,6 +50041,7 @@ production browser smoke:
|
||||
**狀態**:
|
||||
- Gitea `main` 已有 `49c02e5b3` API / Workbench source 與 `6083cb71a` CD deploy marker,但 production 兩個新 API route 仍回 404,公開 Gitea Actions 顯示 CD #4003 `Failure`。
|
||||
- 既有 production deploy readback 只用 runtime `AWOOOI_BUILD_COMMIT_SHA` 覆寫 source/main 欄位,可能讓舊 production image 自稱 `production_image_tag_matches_main=true`。
|
||||
- 補充:CD #4010 在 deploy marker 前失敗;根因是新測試檔 `apps/api/tests/test_awoooi_production_deploy_readback_blocker.py` 未納入 controlled-runtime 白名單,導致窄發布掉入 full/B5。已補白名單與 focused pytest 清單。
|
||||
|
||||
**完成內容**:
|
||||
- `awoooi_production_deploy_readback_blocker` 改為比對 runtime `AWOOOI_BUILD_COMMIT_SHA` 與 GitOps desired env `AWOOOI_DESIRED_API_IMAGE_TAG`;缺少 desired env 或不一致時 fail-closed 成 blocker。
|
||||
|
||||
Reference in New Issue
Block a user