fix(governance): mark priority readback projection source
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Successful in 58s
CD Pipeline / post-deploy-checks (push) Has been cancelled
CD Pipeline / build-and-deploy (push) Has been cancelled

This commit is contained in:
Your Name
2026-07-03 10:57:58 +08:00
parent f69e056bab
commit aed26bae84
3 changed files with 20 additions and 0 deletions

View File

@@ -54159,6 +54159,7 @@ production browser smoke:
**完成內容**
- `awoooi-priority-work-order-readback` 已在 source 層補齊 P0-006 active blocker count、primary blocker、current phase、ETA / wait reason 與 next safe action projection第一次 main push `12af61a58` 已進 Gitea main但 CD `#4559` 被後續 metadata-only commit 取代production readback 尚未出現新增欄位。
- 本段以最小 API source touch 固定 `active_p0_live_active_blocker_count` 以 live blocker list 為 canonical避免 stale top-level count 遮蔽 priority work order 的下一步欄位,並重新觸發 production build/deploy。
- 第二輪補上 `active_p0_projection_source=reboot_auto_recovery_slo_scorecard`,讓 production readback 可直接證明 active P0 欄位來自 reboot SLO scorecard projection。
**本地驗證結果**
- `DATABASE_URL=postgresql+asyncpg://test:test@localhost/test PYTHONPATH=apps/api python3.11 -m pytest apps/api/tests/test_awoooi_priority_work_order_readback_api.py apps/api/tests/test_reboot_auto_recovery_slo_scorecard_api.py -q -p no:cacheprovider``38 passed`