docs(i18n): add zh-CN translations for developing modules (C2)#2505
Merged
senamakel merged 3 commits intoMay 22, 2026
Merged
Conversation
Translates 9 developer-facing module documents into Simplified Chinese: - architecture/frontend.md (frontend architecture, 2302 lines) - architecture/tauri-shell.md (Tauri shell) - architecture/agent-harness.md (Agent Harness) - architecture/desktop-companion.md (Desktop Companion) - agent-observability.md (E2E observability) - cef.md (Chromium Embedded Framework) - mcp-server.md (MCP Server) - release-policy.md (release policy) - integrations/polymarket.md (Polymarket integration) Links localized where .zh-CN.md target exists. Opening fences use ```text, closing fences use ```. Technical terms follow terminology-zh-CN.md: Agent Harness, Desktop Companion, Tauri Shell, CEF retained in English; MCP Server -> MCP 服务器.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThis PR adds nine Chinese documentation pages describing agent lifecycle and observability, frontend and desktop companion architecture, Tauri shell and CEF runtime integration, MCP server protocol, Polymarket integration, and desktop release policy. ChangesAgent Architecture & Desktop Operations Documentation
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 12
🧹 Nitpick comments (1)
gitbooks/developing/architecture/agent-harness.zh-CN.md (1)
65-65: 💤 Low valueOptional: Consider Chinese adverb form for smoother reading.
LanguageTool suggests using the adverb marker "地" in two locations:
- Line 65: "精确的提供商" → "精确地提供"
- Line 310: "具体的提供商" → "具体地提供"
This is a minor stylistic improvement for more idiomatic Chinese grammar.
Also applies to: 310-310
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@gitbooks/developing/architecture/agent-harness.zh-CN.md` at line 65, Replace the two noun-phrases with adverbial forms for smoother Chinese: change the phrase "精确的提供商" in the sentence starting with "恢复会话转录" to "精确地提供" and similarly change "具体的提供商" (around line 310) to "具体地提供" so the verbs are modified by the adverbial "地" for more idiomatic grammar.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@gitbooks/developing/agent-observability.zh-CN.md`:
- Around line 20-36: The fenced code block showing the artifact directory
listing is missing a language identifier; update the opening fence (the triple
backticks that begin the block containing
"app/test/e2e/artifacts/<ISO-timestamp>-agent-review/...") to include a language
specifier such as "text" (i.e., change ``` to ```text) so GitBook renders it
correctly.
In `@gitbooks/developing/architecture/agent-harness.zh-CN.md`:
- Around line 212-221: The fenced code block containing the trigger
classification diagram (the block starting with the diagram lines including
"TriggerEnvelope", "run_triage", "TriageDecision", and "apply_decision") needs a
language identifier on the opening fence; update the opening ``` to include a
language tag such as ```text (or another appropriate tag) so GitBook renders it
correctly, leaving the diagram content unchanged.
- Around line 77-88: The fenced code block that starts with "```" and contains
the pseudo-code beginning "loop {" needs a language identifier added for proper
GitBook rendering; update the opening fence from "```" to "```text" (or another
appropriate language) so the block rendering is correct while leaving the
pseudo-code (lines including "loop {", steps 1–8, and closing "```") unchanged.
- Around line 17-49: The fenced ASCII diagram block in agent-harness.zh-CN.md
lacks a language identifier; update the opening fence for that diagram (the
triple-backtick before the ASCII art) to include a language specifier such as
text (e.g., change ``` to ```text) so GitBook will render it correctly; locate
the diagram block near the Agent::turn() ASCII flow and modify its opening fence
only.
In `@gitbooks/developing/architecture/desktop-companion.zh-CN.md`:
- Around line 23-24: The fenced code blocks in the document are missing language
identifiers; update the two code fences that contain the module path
"src/openhuman/desktop_companion/" and the state-machine line "Idle -> Listening
-> Thinking -> Speaking -> Pointing -> Idle" to include the language tag text
(i.e., change ``` to ```text) so the modules layout and state-machine diagram
render/access correctly.
In `@gitbooks/developing/architecture/frontend.zh-CN.md`:
- Around line 35-36: The fenced code block that contains the directory tree
"app/src/" (and other fenced blocks showing directory trees/architecture/route
diagrams) lacks a language identifier; update those fenced code blocks by adding
the "text" language tag to the opening fence (e.g., change ``` to ```text) for
the block containing "app/src/" and for the other similar diagram blocks so they
are marked as plain text for accessibility and proper rendering.
In `@gitbooks/developing/architecture/tauri-shell.zh-CN.md`:
- Around line 41-42: The fenced code blocks that contain the directory and
diagram snippets (the lines with "app/src-tauri/src/" and "React (invoke)") lack
a language identifier; update those three backticks to include the language
token "text" (i.e., change ``` to ```text for the fenced blocks containing those
snippets) so the blocks render/accessibility correctly.
- Line 13: The internal link [Commands](`#commands`) is broken because there is no
matching "`#commands`" heading; update the link to point to the actual heading
anchor (e.g., the "Tauri IPC 命令 (`app/src-tauri`)" section) or add an explicit
anchor/HTML id to the target heading (for example add an HTML anchor like <a
id="tauri-ipc-commands-app-src-tauri"></a> before the heading); also verify and
correct the other anchors referenced (`#tauri-ipc-commands-app-src-tauri`,
`#core-bridge-helpers-app-src-tauri`) to match the rendered GitBook anchors or
make them explicit so links resolve correctly.
In `@gitbooks/developing/integrations/polymarket.zh-CN.md`:
- Line 1: Add YAML frontmatter to the top of the Polymarket Chinese translation
file to enable GitBook multi-language rendering by inserting a frontmatter block
that specifies lang: zh-CN (e.g., a top-of-file block with lang: zh-CN and any
existing required keys); ensure the frontmatter appears before the existing
markdown header "# Polymarket 集成（读取 + 交易）" so GitBook recognizes the file as
Chinese.
In `@gitbooks/developing/mcp-server.zh-CN.md`:
- Around line 83-86: The fenced code block that shows the JSON-RPC responses is
missing a language identifier (triggering markdownlint MD040); update the block
that contains the two JSON lines (the example responses with
{"jsonrpc":"2.0","id":1,...} and {"jsonrpc":"2.0","id":2,...}) to use a JSON
language fence by changing ``` to ```json so syntax highlighting and
accessibility are enabled.
- Around line 1-4: Add the missing frontmatter field by inserting lang: zh-CN
into the YAML frontmatter block at the top of the document (the existing block
containing description and icon), so the frontmatter becomes something like ---
description: ... icon: ... lang: zh-CN --- ensuring the new lang field is on its
own line and preserves the YAML structure for proper GitBook multi-language
rendering.
In `@gitbooks/developing/release-policy.zh-CN.md`:
- Around line 1-4: The frontmatter block at the top of the file is missing the
required lang field; add a line "lang: zh-CN" inside the existing YAML
frontmatter (between the leading and trailing '---') so the document includes
the language metadata and matches other translated files; ensure the field
appears alongside description and icon entries in the same frontmatter block.
---
Nitpick comments:
In `@gitbooks/developing/architecture/agent-harness.zh-CN.md`:
- Line 65: Replace the two noun-phrases with adverbial forms for smoother
Chinese: change the phrase "精确的提供商" in the sentence starting with "恢复会话转录" to
"精确地提供" and similarly change "具体的提供商" (around line 310) to "具体地提供" so the verbs
are modified by the adverbial "地" for more idiomatic grammar.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 54a0261d-6f30-4fb0-b752-59900ed7412d
📒 Files selected for processing (9)
gitbooks/developing/agent-observability.zh-CN.mdgitbooks/developing/architecture/agent-harness.zh-CN.mdgitbooks/developing/architecture/desktop-companion.zh-CN.mdgitbooks/developing/architecture/frontend.zh-CN.mdgitbooks/developing/architecture/tauri-shell.zh-CN.mdgitbooks/developing/cef.zh-CN.mdgitbooks/developing/integrations/polymarket.zh-CN.mdgitbooks/developing/mcp-server.zh-CN.mdgitbooks/developing/release-policy.zh-CN.md
- 为目录树/架构图/路由图代码块添加 text 语言标识符 (agent-observability, agent-harness x3, desktop-companion x2, frontend x9, tauri-shell x2) - mcp-server: JSON 响应块添加 json 标识符 - 修复 tauri-shell [Commands](#commands) 死链 - 为缺少 frontmatter 的文件添加 lang: zh-CN (polymarket, mcp-server, release-policy) - 跳过 nitpick: 保留精确的提供商消息具体的提供商+模型， 原文为名词性修饰结构，改为精确地提供会改变语义
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (2)
gitbooks/developing/architecture/tauri-shell.zh-CN.md (1)
41-55:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win为图表添加语言标识符。
目录布局（Line 41）和数据流图（Line 61）的围栏代码块缺少语言标识符。添加
text以改善渲染和可访问性。建议的修复
Line 41:
-``` +```text app/src-tauri/src/Line 61:
-``` +```text React (invoke)As per coding guidelines: Markdown fenced code blocks should specify a language identifier for accessibility and proper rendering.
Also applies to: 61-66
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@gitbooks/developing/architecture/tauri-shell.zh-CN.md` around lines 41 - 55, Add the missing Markdown fenced-code language identifiers by changing the two code blocks to include "text": update the directory layout block that begins with "app/src-tauri/src/" (the fenced block shown in the diff) to use ```text and likewise update the data-flow/diagram block that contains "React (invoke)" to start with ```text so both blocks have explicit language identifiers for correct rendering and accessibility.gitbooks/developing/architecture/frontend.zh-CN.md (1)
35-49:⚠️ Potential issue | 🟡 Minor | ⚡ Quick win为结构图添加语言标识符。
文档中的多个围栏代码块（目录树、架构图、路由结构等）缺少语言标识符。添加
text标识符可以改善辅助功能和语法高亮处理。建议的修复
为所有纯文本结构图添加 ```text 标识符：
-``` +```text app/src/对以下行的其他代码块应用相同的修复：73, 94, 109, 396, 877, 1077, 1185, 1297, 1499。
As per coding guidelines: Markdown fenced code blocks should specify a language identifier for accessibility and proper rendering.
Also applies to: 73-82, 94-105, 109-115, 396-407, 877-889, 1077-1086, 1185-1193, 1297-1327, 1499-1519
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@gitbooks/developing/architecture/frontend.zh-CN.md` around lines 35 - 49, Add the missing language identifier "text" to the Markdown fenced code blocks that are pure text diagrams/trees so they render/accessibility correctly; specifically change openings like ``` to ```text for the code block that begins with "app/src/" (the directory tree) and apply the same fix to the other pure-text fences referenced in the review (the blocks starting at the other listed regions such as the directory/tree/diagram blocks around lines 73–82, 94–105, 109–115, 396–407, 877–889, 1077–1086, 1185–1193, 1297–1327, and 1499–1519) so each plain-text structure uses ```text as its opening fence.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@gitbooks/developing/architecture/tauri-shell.zh-CN.md`:
- Line 13: The internal link target `#tauri-ipc-commands-app-src-tauri` in
tauri-shell.zh-CN.md may not reliably resolve because the heading "Tauri IPC 命令
(`app/src-tauri`)" lacks an explicit anchor; update that heading to include an
explicit ID (e.g., add `{`#tauri-ipc-commands-app-src-tauri`}` or an `<a
id="tauri-ipc-commands-app-src-tauri"></a>` immediately before the heading) so
the link resolves deterministically, or alternatively verify and record the
rendered slug produced by GitBook and adjust the link to match that exact
fragment.
---
Duplicate comments:
In `@gitbooks/developing/architecture/frontend.zh-CN.md`:
- Around line 35-49: Add the missing language identifier "text" to the Markdown
fenced code blocks that are pure text diagrams/trees so they
render/accessibility correctly; specifically change openings like ``` to ```text
for the code block that begins with "app/src/" (the directory tree) and apply
the same fix to the other pure-text fences referenced in the review (the blocks
starting at the other listed regions such as the directory/tree/diagram blocks
around lines 73–82, 94–105, 109–115, 396–407, 877–889, 1077–1086, 1185–1193,
1297–1327, and 1499–1519) so each plain-text structure uses ```text as its
opening fence.
In `@gitbooks/developing/architecture/tauri-shell.zh-CN.md`:
- Around line 41-55: Add the missing Markdown fenced-code language identifiers
by changing the two code blocks to include "text": update the directory layout
block that begins with "app/src-tauri/src/" (the fenced block shown in the diff)
to use ```text and likewise update the data-flow/diagram block that contains
"React (invoke)" to start with ```text so both blocks have explicit language
identifiers for correct rendering and accessibility.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 1c2c4a69-47d5-4507-b0d6-fffc3d284459
📒 Files selected for processing (8)
gitbooks/developing/agent-observability.zh-CN.mdgitbooks/developing/architecture/agent-harness.zh-CN.mdgitbooks/developing/architecture/desktop-companion.zh-CN.mdgitbooks/developing/architecture/frontend.zh-CN.mdgitbooks/developing/architecture/tauri-shell.zh-CN.mdgitbooks/developing/integrations/polymarket.zh-CN.mdgitbooks/developing/mcp-server.zh-CN.mdgitbooks/developing/release-policy.zh-CN.md
✅ Files skipped from review due to trivial changes (6)
- gitbooks/developing/architecture/desktop-companion.zh-CN.md
- gitbooks/developing/integrations/polymarket.zh-CN.md
- gitbooks/developing/agent-observability.zh-CN.md
- gitbooks/developing/mcp-server.zh-CN.md
- gitbooks/developing/architecture/agent-harness.zh-CN.md
- gitbooks/developing/release-policy.zh-CN.md
Contributor
Author
|
@senamakel Hi, while working on zh-CN translations I noticed some UI strings in channels/* components are hardcoded in English (auth mode labels, field placeholders, MCP descriptions). I have a branch ready that wraps them with the existing t() i18n system with English fallback. Is this kind of refactoring welcome, or do you prefer to keep hardcoded strings until a larger i18n overhaul? @graycyrus also curious about your take since you reviewed the docs batch. |
Add {#tauri-ipc-commands-app-src-tauri} and {#core-bridge-helpers-app-src-tauri}
to their respective headings so internal links resolve deterministically
in GitBook rendering. Skips duplicate issues already fixed in previous commit:
- frontend.zh-CN.md: 9 diagram blocks already use text
12 tasks
senamakel
pushed a commit
to aqilaziz/openhuman
that referenced
this pull request
May 23, 2026
…umansai#2505) Co-authored-by: agent:skill-master <skill-master@openclaw>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
gitbooks/developing/下 9 个架构子模块与专项文档翻译为简体中文（zh-CN），覆盖前端、Tauri 壳层、Agent Harness、Desktop Companion、CEF、MCP、发布策略等核心实现细节。lang: zh-CN，确保 GitBook 多语言渲染正确识别。architecture/frontend.zh-CN.md→tauri-shell.zh-CN.md/agent-harness.zh-CN.md等），外部无翻译文档保持英文原链。terminology-zh-CN.md），确保Agent Harness、Desktop Companion、Tauri Shell、CEF等技术模块名保留英文，token保留英文不译"令牌"，Skill-wildcard保留英文，preflight/staging/vendored等开发术语保留英文。Problem
OpenHuman 的开发者文档中，关于前端架构、Tauri 壳层 IPC、Agent Harness 多智能体循环、CEF 集成原理、发布策略等核心实现细节目前仅有英文版本。中文贡献者无法以母语深入理解系统各模块的设计与交互，阻碍了从"入门搭建"到"深入贡献"的进阶路径。
Solution
architecture/frontend.zh-CN.md— 前端架构（2302 行，含 Redux、Services、Providers、Routing、Components、Hooks）architecture/tauri-shell.zh-CN.md— Tauri 壳层（IPC 命令、CoreProcessHandle、窗口/托盘）architecture/agent-harness.zh-CN.md— Agent Harness（工具调用循环、子智能体分派、triage、hooks）architecture/desktop-companion.zh-CN.md— Desktop Companion（Clicky 交互循环、状态机、流水线）agent-observability.zh-CN.md— E2E Agent 可观测性（工件捕获层）cef.zh-CN.md— Chromium Embedded Framework（CDP 驱动扫描器、零 JS 注入规则）mcp-server.zh-CN.md— MCP 服务器（stdio MCP 模式、工具注册表）release-policy.zh-CN.md— 发布策略（staging/production 工作流、OAuth 最低版本）integrations/polymarket.zh-CN.md— Polymarket 集成（读取 + 交易、EIP-712 签名）.zh-CN.md（如frontend.zh-CN.md→tauri-shell.zh-CN.md）；指向已翻译 features 文档（如native-tools/README.zh-CN.md）的链接已本地化；指向外部无翻译文档的链接保留英文原版。token统一保留英文（不译"令牌"）；Skill-wildcard保留英文；通用概念尽量中文化。```text/ closing fence```格式正确；验证 frontmatter 完整性；验证无空代码块、无 trailing whitespace。Submission Checklist
diff-cover) meet the gate enforced by.github/workflows/coverage.yml. Runpnpm test:coverageandpnpm test:rustlocally; PRs below 80% on changed lines will not merge.docs/TEST-COVERAGE-MATRIX.mdreflect this change (orN/A: behaviour-only change)## Relateddocs/RELEASE-MANUAL-SMOKE.md)Closes #NNNin the## RelatedsectionImpact
.zh-CN.md翻译文件，未修改任何源代码、构建配置或运行时行为。lang标记渲染对应语言版本。Related
cloud-deploy.md,tool-memory.md,troubleshooting-sign-in.md,privacy-policy.md,terms-of-use.md,README.md,SUMMARY.md.zh-CN.mdAI Authored PR Metadata (required for Codex/Linear PRs)
Linear Issue
Commit & Branch
docs/i18n-batch-c2-developing-modules55b2c4beValidation Run
pnpm --filter openhuman-app format:checkpnpm typecheckValidation Blocked
command:N/Aerror:N/Aimpact:N/ABehavior Changes
Parity Contract
Duplicate / Superseded PR Handling
Summary by CodeRabbit