fix(api): expose stockplatform recovery control blocker
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 27s
CD Pipeline / build-and-deploy (push) Failing after 50m32s
CD Pipeline / post-deploy-checks (push) Has been cancelled
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 27s
CD Pipeline / build-and-deploy (push) Failing after 50m32s
CD Pipeline / post-deploy-checks (push) Has been cancelled
This commit is contained in:
@@ -1,3 +1,12 @@
|
||||
## 2026-06-30 — 16:40 P0-006 StockPlatform recovery control-path readback
|
||||
|
||||
**照主線修正的問題**:
|
||||
- Production P0-006 已讀回 `7890778b83`,但 StockPlatform public API 仍是 edge `/healthz=200`、`/api/healthz=502`、freshness `502`、ingestion `502`;這不是資料 freshness 假綠,而是 API upstream/runtime drift。
|
||||
- SSH 到 110 TCP 可連,但 publickey auth 後等待 host 回應 timeout;StockPlatform Gitea workflow 是 manual-only,不能用 push trigger 繞過 110 capacity freeze。
|
||||
- `stockplatform_public_api_runtime_readback` 現在 fail-closed 加入 recovery control-path receipt:缺 target selector、check-mode/dry-run、rollback、post-apply public API verifier、KM/PlayBook/LOG writeback receipt 時,會把 `stockplatform_recovery_control_path_receipt_missing` 與 `stockplatform_controlled_deploy_or_ssh_readback_required` 納入 P0-006 blockers。
|
||||
|
||||
**邊界**:未觸發 StockPlatform deploy workflow,未恢復 push deploy trigger,未 restart Docker daemon / Nginx / K3s / DB / firewall,未 prune / restore / DB write,未讀 secret / token / raw sessions / SQLite / `.env`,未使用 GitHub / `gh` / GitHub API。
|
||||
|
||||
## 2026-06-30 — 10:18 production deploy readback window 擴充
|
||||
|
||||
**照主線修正的問題**:
|
||||
|
||||
Reference in New Issue
Block a user