docs(blog): explain Runtime Host and Peer Mesh architecture

[M4n5ter]

Summary

Add two source-backed articles in Chinese and English:

• Runtime Host: how clients share execution through single-writer ownership, admission, subscriptions, client capabilities, lifecycle management, and safe handoff.
• Peer Mesh: how identity, membership, reachability, and controlled transit support Maka networking, with future directions for personal work networks, capability discovery, and cross-Host collaboration clearly separated from current behavior.

Both articles use Mermaid diagrams and cite implementation sources.

Verification

• npm run lint and npm run format:check passed during this PR's preparation.
• ASF license-header, protocol-epoch, and Git whitespace checks passed.
• Checked links, footnotes, and bilingual consistency; rendered and visually inspected all 10 Mermaid diagrams.
• Ran the peer-mesh, peer-reachability, and resumable-peer-stream suites while verifying the second article: 42 passed, 0 failed, 0 skipped. This does not establish real-world NAT coverage.
• The CI planner classifies the four Markdown files as documentation-only. Build, typecheck, Knip, and full workspace tests were not rerun for this diff.

AI use

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: OpenAI Codex researched the implementation and drafted, revised, translated, and checked the articles and diagrams. The commits include Generated-by: OpenAI Codex trailers.

Checklist

• Tests cover the change and fail without it — not applicable: documentation only.
• Applicable local checks pass; source references, bilingual consistency, and diagram rendering were checked.

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[jackwener]

APPROVE on d651051fc478f7cfb728cb9a211dcdd2c53fa9af at the explicit direction of M4n5ter. I found no unresolved P0-P2 issue in the documentation change.

The English and Chinese Runtime Host and Peer Mesh articles keep current mechanisms separate from future product directions, and their source references, section structure, diagrams, and local links are consistent. Lint, formatting, ASF headers, and whitespace checks pass. The exact-head hosted test check is terminal green, and the change forms a clean synthetic merge with current main.

This approval is not a merge action; no merge was performed.

---

Automated review notice: This comment was posted by an automated review agent operated by jackwener. It is not an independent human review and does not replace one.