[Feature] Auto review 的拒绝理由恒为英文，界面中文时读不懂为何被拒 / Rejection reason stays English even when the UI is Chinese

[Void-LifeStream]

中文摘要：开启「自动授权审查」后，工具调用被拒绝时，界面只本地化了前缀「Auto review 拒绝了此调用：」，而后面那段解释「为什么被拒」的推理始终是英文 —— 而这恰恰是唯一一条用来解释拒绝原因的消息。源码注释里写着 The audited reason is English; the prompt text is localized，所以看起来是有意为之，而非漏翻。建议：显示层本地化、审计日志保留英文原文（两者面向不同读者，不是取舍），或提供一个配置开关。

---

Hi — first, thanks for auto-review; splitting what gets audited from what gets localized is a sensible design, and the source comment says so explicitly.

What I observed

With the UI in Chinese, when Auto review rejects a tool call, only the prefix is localized:

Auto review 拒绝了此调用：<a long paragraph of English reasoning follows>

The prefix is Chinese, but the part that actually explains why is English. The source comment states the intent — The audited reason is English; the prompt text is localized — so this looks deliberate rather than a missing translation.

Why it matters

The prefix alone carries no information. The only message whose entire purpose is to explain a refusal ends up unreadable to a Chinese-speaking user, and what to fix has to be inferred from a wall of English reasoning.

Suggested fix (either one keeps the audit trail intact)

1. Localize the displayed reason, keep the English original in the audit log — these serve two different audiences, so it is not a trade-off; or
2. Add a config switch (e.g. reasonLanguage: ui | en) so operators can choose per deployment.

Environment

• DSH desktop on Windows 11 (profile desktop)
• @deepseek-ai/dsh-experimental-auto-review v0.2.0-rc.2 (experimental), component id auto-review
• Its Config schema is absent — there is no setting to change this today; the change would live in REVIEW_POLICY inside the asar.

One more lead (lower confidence, reported as a pointer only)

The regular approval dialog (ask mode — e.g. a call to univer_worktree) also surfaces an English reason / detail, while the dialog chrome itself is localized (等待审批 / 拒绝 / 允许一次 are all Chinese). I have not yet located where that text originates — it appears to come through the conversation.approval.detail slot, but I did not confirm the source.

---

If this belongs in another category, please move it or tell me and I will re-file it there. 如果发错板块请告知，我会重发。