docs: add bilingual community entry point

[huangruiteng]

Summary

• add matching English and Chinese community entry-point pages
• route discussion, Discord, Lark, WeChat, six focused issue forms, showcase prompts, and ecosystem evidence from one place
• link the pages from the source and hosted documentation indexes without changing the README first screen or top navigation
• extend the docs governance smoke for the intentional root pages and explicit below-first-screen navigation exception

Validation

• python examples/docs-governance-smoke.py
• python examples/docs-asset-integrity-smoke.py
• relative-link check: 18 local links resolved across both pages
• bilingual entry parity: 10 shared community routes per locale
• ruff check examples/docs-governance-smoke.py
• loopx check over all five changed files: 0 errors; two unrelated pre-existing goal projection warnings
• git diff --check

Boundaries

The pages use only existing public routes and assets. No private community context, credentials, raw agent state, or README first-screen change is included.

[huangruiteng]

Exact-head review for 7e14134e993bf2c3a693b579c3a138ff3f378cee.

Delivery judgment

This is a cohesive, docs-only community entry slice. The English and Chinese pages expose the same 10 public routes: Discussion 2851, Discord, Lark, WeChat, and all six issue forms. They also route showcase contributions and distinguish the maintainer-curated ecosystem catalog from voluntary ADOPTERS entries. The existing docs indexes make the page reachable below the first screen; README first-screen and hosted top navigation are unchanged.

Validation

• docs governance smoke: passed
• docs asset integrity smoke: passed
• 18 relative links across both pages: passed
• 10-route locale parity check: passed
• Ruff on the changed governance smoke: passed
• LoopX public/private scan over all five changed files: 0 errors
• change-quality receipt cqr_9a4a4436ff1d69e85a5a: valid for the exact 5-file fingerprint
• standard premerge gate: 4 direct checks plus 15 selected canaries passed; 0 failures, 0 warnings, 0 manual holds

The first premerge attempt exposed a missing local Node dependency needed by the semantic vocabulary parser. After npm ci --ignore-scripts, the failing smoke and the complete premerge set passed unchanged; no repository workaround or gate reduction was made.

Boundaries and future-facing pass

No private context, credentials, raw runtime state, new channel registry, runtime behavior, permission boundary, or release contract is included. Existing public assets, issue forms, showcase catalog, and adoption catalog remain the single sources. A generator or new configuration owner would add unnecessary indirection; no adjacent refactor is justified.

English verdict: APPROVE — exact head 7e14134e993bf2c3a693b579c3a138ff3f378cee is ready for maintainer merge.