Have the Chinese copy of the seven relaunch pages read by a native speaker

[openipc-ai]

Part of #206 (Phase 0). Depends on nothing; the pages are live.

Why

The seven relaunch pages went live on 2026-08-28 in three languages. The English and Russian copy was written by hand in June. The Chinese was written in August for #123 because no translation API key was available, and both #123 and #124 flagged it as not read by a native speaker. Chinese is one of the site's three languages by the maintainers' decision, and the largest audience the site cannot currently vouch for.

What to change

• Have a native reader go through the home, get_started, low_latency, ecosystem, business, community and donate blocks of config/locales/pages.zh.yml, plus the site-wide strings in config/locales/zh.yml that those pages render (navigation, footer, the donate band, the meta description).
• Land the corrections as one change. Keys stay as they are; only values move, so i18n-tasks missing and unused do not change.
• Record who reviewed it and when in the change description, so the next page knows whom to ask.

Later pages in this epic get the same pass before they are linked from the navigation; this issue establishes the reviewer.

Done means

• A native speaker's corrections are merged, or a native speaker has read the seven pages and found nothing to change, and either fact is written in this issue.
• i18n-tasks missing is clean for zh; bin/rails test is green.

[openipc-ai]

PR #240 adds six Chinese strings that need this issue's read, and Qodo flagged them as a requirement gap against it. Listing them here so the reviewer has the exact set rather than a diff to hunt through.

config/locales/zh.yml, under firmware.installation — rendered in the install wizard's what-next block:

key	value
chat_lede	就这块硬件提问：
chat_blocked_html	Telegram 并非在所有网络下都能打开。如果你的网络打不开，请到<a …>问题追踪器提问。

config/locales/pages.zh.yml, under pages.community — rendered on /zh/community:

key	value
reach_title	如果 Telegram 打不开
reach_lede	Telegram 并非在所有网络下都能打开——在某些国家、某些公司 Wi-Fi、很多酒店网络下都是如此。下面这些方式在任何地方都可用：
reach_issues_html	<a …>问题追踪器——到相关仓库提问。一份好的报告本身就是贡献。
reach_wiki_html	<a …>维基——安装、FPV 和排障指南。

Plus one reworded string, pages.community.help2: 搜索聊天记录或维基；大多数新手问题此前都已有人解答。 (was 搜索聊天记录；… — "search the chat history" is only followable from inside a room a Chinese reader cannot enter, so the wiki was added as an alternative.)

One known problem to settle, visible in the rendered page: the room list uses a spaced em dash (OpenIPC & FPV — 关于基于 OpenIPC 的 FPV 与视频链路的一切。) while the lines directly below it use the doubled dash (把它放上开放墙 ——在网页界面里改一个设置…). Both conventions now appear in the same block. The separator in the room lines is hard-coded in InstallationHelper#chat_door_items; if the doubled form is right for Chinese it needs to become a locale string rather than a literal.

Two notes on intent, since they are easy to "correct" in the wrong direction:

1. The copy deliberately says network, not country — "Telegram 并非在所有网络下都能打开" rather than naming China or Russia. It is equally true of company Wi-Fi and hotel connections, and the site does not know where the reader is sitting.
2. There is deliberately no VPN or proxy advice. Promoting circumvention is restricted in Russia and the project has a Russian mirror to protect, so the page names the blockage and offers routes that work rather than ways around it.

Translations are machine-quality and mine; nobody has read them. Please record the reviewer and date on this issue when it is done.