fix(web): show Runs incident status-chain focus
Some checks failed
Code Review / ai-code-review (push) Successful in 13s
CD Pipeline / tests (push) Successful in 1m34s
CD Pipeline / build-and-deploy (push) Successful in 3m43s
CD Pipeline / post-deploy-checks (push) Successful in 1m29s
Ansible / Reboot Recovery Contract / validate (push) Has been cancelled

This commit is contained in:
Your Name
2026-06-25 21:57:13 +08:00
parent e5a0aa1345
commit 426ad3d5dd
3 changed files with 40 additions and 4 deletions

View File

@@ -264,6 +264,21 @@ Tenants 目前已讀到:
完成度同步Runs incident drilldown 穩定性 `60% -> 72%`Runs apply-gate 正式頁驗證需下一個 deploy marker 後重跑。
### 2.5.10 Runs incident filter 接入 status-chain 焦點
2026-06-25 `e5a0aa13` 部署後,正式 API 已證明 incident drilldown 不再 502
| 項目 | 結果 |
|---|---|
| Health | `/api/v1/health``healthy / prod / mock_mode=false` |
| Status-chain | `INC-20260625-977E5F``ansible_check_mode_only``automation_handoff.kind=ansible_check_mode_apply_gate``runtime_execution_authorized=false` |
| Runs list | `/api/v1/platform/runs/list?incident_id=INC-20260625-977E5F``200``total=3` |
| 新缺口 | run list 摘要不一定帶 `remediation_summary.incident_ids`,前端只靠 run summary 推導 status-chain 時URL 已帶 incident id 仍可能看不到焦點 handoff |
修正Runs 頁若 URL `incident_id` 符合 `INC-*` 格式,直接把該 id 納入 `useIncidentStatusChains`,保留原本從 run summary 收斂多事故關聯的邏輯。
完成度同步Runs incident drilldown 穩定性 `72% -> 82%`AwoooP Runs apply-gate 正式頁驗證需前端修正 deploy 後重跑。
## 3. 頁面 UI/UX 現況盤點
2026-06-25 對正式站桌機 / mobile 抽查: