82f3140847
Complete architecture document set with multi-model review remediation: - Frozen interface contracts, runtime semantics, DB schemas - Event/tool/error/provider registries - Scheduler and main agent state machines - C4 module/code views, solution architecture, baseline V1 - Multi-model review reports and joint assessment - Phase-gate remediation complete (P0/P1/P2/UX resolved) - Implementation plan with T-000A through T-045 - Reference folders kept as placeholders only
2.1 KiB
Executable File
2.1 KiB
Executable File
zh-cn Glossary
Sources
Do Not Translate (Locale Additions)
OpenCode(preserve casing in prose; keepopencodeonly when it is part of commands, package names, paths, or code)OpenCode ZenOpenCode CLICLI,TUI,MCP,OAuthModel Context Protocol(prefer the English expansion when introducingMCP)
Preferred Terms
These are preferred terms for docs/UI prose and may evolve.
| English | Preferred | Notes |
|---|---|---|
| prompt | 提示词 | Keep --prompt unchanged in flags/code |
| session | 会话 | |
| provider | 提供商 | |
| share link / shared URL | 分享链接 | Prefer 分享 for user-facing share actions |
| headless (server) | 无界面 | Docs wording |
| authentication | 认证 | Prefer in auth/OAuth contexts |
| cache | 缓存 | |
| keybind / shortcut | 快捷键 | User-facing docs wording |
| workflow | 工作流 | e.g. GitHub Actions workflow |
Guidance
- Prefer natural, concise phrasing over literal translation
- Keep the tone direct and friendly (PR #13942 consistently moved wording in this direction)
- Preserve technical artifacts exactly: commands, flags, code, inline code, URLs, file paths, model IDs
- Keep enum-like values in English when they are literals (for example,
default,json) - Prefer consistent terminology across pages once a term is chosen (
会话,提供商,提示词, etc.)
Avoid
- Avoid
opencodein prose when referring to the product name; useOpenCode - Avoid mixing alternative terms for the same concept across docs when a preferred term is already established