fix(web): 統一治理頁公開顯示清理
Some checks failed
Code Review / ai-code-review (push) Successful in 14s
CD Pipeline / tests (push) Successful in 1m39s
CD Pipeline / build-and-deploy (push) Successful in 4m37s
CD Pipeline / post-deploy-checks (push) Successful in 1m40s
Ansible / Reboot Recovery Contract / validate (push) Has been cancelled
Some checks failed
Code Review / ai-code-review (push) Successful in 14s
CD Pipeline / tests (push) Successful in 1m39s
CD Pipeline / build-and-deploy (push) Successful in 4m37s
CD Pipeline / post-deploy-checks (push) Successful in 1m40s
Ansible / Reboot Recovery Contract / validate (push) Has been cancelled
This commit is contained in:
@@ -1,3 +1,31 @@
|
||||
## 2026-06-19|治理頁 snapshot 公開顯示清理層本地完成
|
||||
|
||||
**背景**:`476227d2` 正式部署後,desktop / mobile smoke 已確認 P2-407~P2-411 與 P3-009 主要卡片無目標英文 drift、無水平溢出、無工作視窗片語;但整頁深層 DOM 仍能在舊 committed snapshot 區塊看到 `audit event template`、`event envelope`、`post-write verifier`、`runtime write`、`live write`、`owner response acceptance readback` 等半英文證據字串。這些不是 runtime 事件,而是 evaluation snapshot 的固定證據內容被前端直接投影,對使用者仍不夠專業、也不符合全站繁中要求。
|
||||
|
||||
**完成內容**:
|
||||
- 在 `apps/web/src/app/[locale]/governance/tabs/automation-inventory-tab.tsx` 擴充公開顯示 glossary,將 audit event、event envelope、post-write verifier、runtime write、live write、owner review、dry-run、Gateway queue write、Telegram send、Bot API call、host write、secret read、kubectl action 等常見操作語轉成繁中可讀文案。
|
||||
- 新增 `sanitizePublicSnapshot()` / `settledPublicValue()`,讓 governance automation inventory 的 API snapshot 進入 React state 前先做公開顯示清理。
|
||||
- 保留 `status`、`risk_tier`、`owner_agent`、`schema_version`、`current_task_id`、`next_task_id`、`*_id` 等程式判斷與識別欄位,不把顯示翻譯回寫成資料語意,避免破壞前端狀態邏輯。
|
||||
- `MiniBar`、`SummaryTile`、`FlowStageTile`、`GateMatrixRow` 補第二層顯示端清理,防止未來新增欄位直接把 raw-ish 狀態語漏到頁面。
|
||||
- 未修改 API、snapshot 檔、worker、Telegram、Bot API、Gateway queue、DB、KM、PlayBook、主機、K8s、Nginx 或 workflow。
|
||||
|
||||
**本地驗證**:
|
||||
- `git diff --check` 通過。
|
||||
- `SECURITY_MIRROR_PROGRESS_GUARD_OK`。
|
||||
- `TELEGRAM_ALERT_READABILITY_GUARD_OK tests=10 ai_lanes=6 host_lanes=6 runtime_gate=0`。
|
||||
- `IWOOOS_CONFIG_CONTROL_GUARD_OK`。
|
||||
- `DOC_SECRET_SANITY_OK scanned_files=934`。
|
||||
- `pnpm --filter @awoooi/web typecheck` 在本隔離 worktree 仍因未安裝 `node_modules`、`tsc` 不存在而無法本地執行;此段需由 Gitea code-review / CD 乾淨環境補驗。
|
||||
|
||||
**完成度同步**:
|
||||
- 治理頁 snapshot 公開顯示清理層:本地 `100%`,正式部署 / desktop / mobile readback `0%`。
|
||||
- IwoooS headline:仍維持 `64%`;active runtime gate 仍 `0`。
|
||||
- Owner response accepted、event bus publish、audit DB write、timeline write、KM write、PlayBook trust write、Gateway queue write、Telegram send、Bot API call、worker dispatch、receipt production write、host write、kubectl action、destructive operation:全部仍 `0 / false`。
|
||||
|
||||
**下一步**:跑 guard、正常推送 Gitea main、等待 code-review / CD / post-deploy checks;正式部署後重跑 `/zh-TW/governance?tab=automation-inventory` desktop / mobile,除了主要卡片外,也檢查整頁 `audit event`、`runtime write`、`live write`、`post-write verifier`、工作視窗片語與水平溢出。
|
||||
|
||||
**邊界**:這是前端公開顯示清理,不是改 evidence 真相、不開 runtime remediation、不新增自動修復,也不代表 Wazuh / Kali / Nginx / 主機處置已授權。
|
||||
|
||||
## 2026-06-19|P2-411 治理頁繁中可見文案正式驗證完成
|
||||
|
||||
**背景**:P2-411 Owner Acceptance Event Bus 已完成 production API 讀回;本段補上治理頁可見文案收斂後的正式部署與 desktop / mobile smoke,確認同頁 P2-407~P2-411 與相鄰卡片不再露出舊英文狀態詞,也沒有把工作視窗內容放到前端。
|
||||
|
||||
Reference in New Issue
Block a user