fix(web): mirror AwoooP operator statuses in Chinese

apps/web/messages/en.json

@@ -3950,16 +3950,16 @@
         "ansibleLine": "Ansible candidates={candidates}; apply={applied}; reason={reason}",
         "kmLine": "KM entries={count}",
         "operator": {
-          "fallbackMcpSummary": "Status chain batch is catching up; MCP evidence {count}, route={route}",
-          "fallbackMissingChain": "Status chain batch is catching up; using run evidence first",
-          "nextStatusChain": "Wait for status-chain batch, or open the incident detail",
+          "fallbackMcpSummary": "狀態鏈批次回補中；目前可見 MCP 證據 {count} 筆，route={route}",
+          "fallbackMissingChain": "狀態鏈批次回補中；先用 Run 證據判讀",
+          "nextStatusChain": "等待狀態鏈批次回補，或打開 Incident 詳情確認",
           "statusChainPending": "status_chain_pending",
           "statuses": {
-            "needsHuman": "Needs human",
-            "failed": "Execution failed",
-            "verified": "Verified",
-            "executed": "Executed",
-            "waiting": "Pending"
+            "needsHuman": "需人工",
+            "failed": "執行失敗",
+            "verified": "已驗證",
+            "executed": "已執行",
+            "waiting": "待判讀"
           }
         },
         "statuses": {

docs/LOGBOOK.md

@@ -3,13 +3,13 @@
 **背景**：P1-4 已補 workflow / secret owner response handoff；本段接著補 P1-5 / S4.4 GitHub primary rollback ADR 的 owner handoff。目標是讓 7 個 in-scope repo 能用同一個只讀封套回覆 rollback owner、fallback role、trigger、pre-cutover / 1h / 24h validation window 與 follow-up owner；這不是 owner approval、不是 dry-run、不是 GitHub primary cutover，也不是 rollback execution。
 
 **本輪完成**：
-- 先 fast-forward 到 `d99e7366 feat(web): expose AwoooP run operator status chain`，再接上 deploy marker `9a965b66 chore(cd): deploy d99e736 [skip ci]`，保留另一個 Session 的 AwoooP runs operator status chain 與 CD 部署基準。
+- 先 fast-forward 到 `d99e7366 feat(web): expose AwoooP run operator status chain`，再接上 deploy marker `9a965b66 chore(cd): deploy d99e736 [skip ci]` 與 `8ad8bf48 fix(web): keep run status readable without chain batch`，保留另一個 Session 的 AwoooP runs operator status chain、CD 部署基準與 run status readability 修正。
 - 更新 `SOURCE-CONTROL-PRIMARY-ROLLBACK-ADR.md`：日期改為 2026-06-04，新增 P1-5 handoff 摘要、6 項送件前檢查、11 欄交接封套、7 個 repo response template 與送後不變條件。
 - 更新 `source-control-primary-rollback-adr.snapshot.json`：新增 `rollback_owner_handoff_package_ready=true`、`rollback_owner_handoff_completion_percent=100`、`rollback_owner_handoff_check_count=6`、`rollback_owner_handoff_packet_field_count=11`、7 個 repo owner response templates，並維持 received / accepted / rejected、owner approved、dry-run、active cutover 全部 `0`。
 - 更新 `source_control_primary_rollback_adr_v1.schema.json`：同步納入 `rollback_owner_handoff`、handoff preflight、handoff packet、repo templates 與 post-handoff invariants，避免 snapshot 與 schema 漂移。
 - 更新 `SOURCE-CONTROL-PRIMARY-READINESS-GATE.md` 與 `source-control-primary-readiness-gate.snapshot.json`：把 rollback ADR gate wording 對齊 P1-5 handoff，但 GitHub primary readiness gate 仍維持 `0`。
 - 更新 IwoooS P0/P1 主控總帳：P1 只讀重盤工作完成度從 `68%` 調到 `70%`；GitHub primary readiness、owner approval、dry-run、active cutover、runtime gate 不調高。
-- Guard 發現 `d99e7366` 新增的 AwoooP operator status chain 在 `apps/web/messages/en.json` 有 5 個英文狀態字串；本段依全站繁中鏡像規則改成繁中，`en.json` / `zh-TW.json` 差異歸零。
+- Guard 發現 `d99e7366` / `8ad8bf48` 新增的 AwoooP operator status chain 在 `apps/web/messages/en.json` 有 8 個英文狀態 / fallback 字串；本段依全站繁中鏡像規則改成繁中，`en.json` / `zh-TW.json` 差異歸零。
 
 **完成度更新**：
 - P1-5 Primary rollback owner handoff：`100%`。

docs/workplans/2026-06-04-iwooos-security-governance-p0.md

@@ -9,7 +9,7 @@
 | 工作視窗 | IwoooS / AWOOOI 資安治理 P0 |
 | 本次乾淨 worktree | `/private/tmp/awoooi-iwooos-governance-p0-20260604` |
 | 本次分支 | `codex/iwooos-governance-p0-20260604` |
-| 最新觀察到的 `gitea/main` | `9a965b66 chore(cd): deploy d99e736 [skip ci]` |
+| 最新觀察到的 `gitea/main` | `8ad8bf48 fix(web): keep run status readable without chain batch` |
 | 前一個正式 IwoooS 候選基準 | code `7b8fc093`、deploy marker `45c63488`、LOGBOOK `02cadee6` |
 | 最新導航 IA 基準 | code `973fc7a4`、LOGBOOK `2555c811`、deploy marker `0260ec89` |
 | 禁止事項 | 不 force push、不 destructive git、不 SSH 修改主機、不 active scan、不收 secrets 明文、不把 AwoooP approval 當資安批准、不把 UI 可見當 runtime 授權 |