Merge remote-tracking branch 'gitea/main' into codex/github-private-backup-readback-20260627

This commit is contained in:
Your Name
2026-06-27 12:03:00 +08:00
3 changed files with 21 additions and 0 deletions

View File

@@ -5950,6 +5950,7 @@
},
"statuses": {
"ready_for_owner_review": "可審查",
"controlled_apply_ready": "受控套用 ready",
"blocked_by_runtime_gate": "runtime 阻擋",
"approval_required": "需批准",
"ready_for_review": "可檢視"
@@ -6000,6 +6001,7 @@
"statuses": {
"ready_for_local_smoke": "可本地 smoke",
"ready_for_owner_review": "可審查",
"controlled_apply_ready": "受控套用 ready",
"approval_required": "需批准",
"blocked_by_runtime_gate": "runtime 阻擋",
"ready_for_review": "可檢視"

View File

@@ -5950,6 +5950,7 @@
},
"statuses": {
"ready_for_owner_review": "可審查",
"controlled_apply_ready": "受控套用 ready",
"blocked_by_runtime_gate": "runtime 阻擋",
"approval_required": "需批准",
"ready_for_review": "可檢視"
@@ -6000,6 +6001,7 @@
"statuses": {
"ready_for_local_smoke": "可本地 smoke",
"ready_for_owner_review": "可審查",
"controlled_apply_ready": "受控套用 ready",
"approval_required": "需批准",
"blocked_by_runtime_gate": "runtime 阻擋",
"ready_for_review": "可檢視"

View File

@@ -1,3 +1,20 @@
## 2026-06-27P2-415 正式瀏覽器讀回修補controlled apply i18n 缺字串歸零
**背景**P2-415 已推上正式環境並可由正式 API / 前台讀回,但瀏覽器 console 顯示既有 `controlled_apply_ready` 狀態缺少繁中 message key造成 `reportRuntimeReadiness``reportRuntimeDryRun` 兩段出現 `MISSING_MESSAGE` 雜訊。
**完成內容**
- 補齊 `governance.automationInventory.reportRuntimeReadiness.statuses.controlled_apply_ready`
- 補齊 `governance.automationInventory.reportRuntimeDryRun.statuses.controlled_apply_ready`
- `zh-TW.json``en.json` 依使用者要求維持繁體中文可讀內容。
**驗證結果**
- `python3.11 -m json.tool apps/web/messages/zh-TW.json` / `apps/web/messages/en.json`:通過。
- `pnpm --filter @awoooi/web typecheck`:通過。
**目前真相邊界**
- 本段只修補前端 message catalog不改 executor、Telegram、主機、K8s、runtime gate、secret 或 live apply 權限。
- P2-415 仍維持 controlled executor dispatch / live apply / Telegram send / Bot API / host write / kubectl / destructive operation 全部 `0`
## 2026-06-27P2-415 AI Agent 受控 Executor 交接跑道API / 前台 / 測試完成
**背景**P2-409 已把 high 風險從「人工 owner review」調整為可走 controlled apply queuecritical 仍保留 break-glass 邊界;本段承接 P2-409 / P2-410 / P2-411補上可被產品與正式 API 讀回的受控 executor handoff 跑道,避免只停留在 UI 文案或口頭批准。