comet-bilingual-docs

Comet bilingual documentation

First read ../comet-github/references/maintainer-contract.md, and limit documentation changes to the scope requested by the user.

Determine source semantics

1. Confirm the authoritative behavior, release scope, or accepted Chinese wording.
2. Update and review the Chinese semantics first. Do not silently change already-confirmed user-visible terminology during translation.
3. When Skill content requires user confirmation, pause after the Chinese version is complete; after confirmation, synchronize the English version.
4. When release synchronization is explicitly requested, keep the user-visible semantics and information architecture consistent across the main Changelog and the Chinese and English website pages.

Synchronize carefully

• Unless the change truly requires it, accurately preserve examples, command names, configuration keys, links, anchors, and code fences.
• Chinese terminology should be natural; do not translate the workflow's "gate" as "门".
• Do not add implementation details the user does not need.
• Treat D:\Project\comet-website-docs as an independent repository. When the user authorizes delivery, commit the website repository first, then update the parent repository gitlink.

Validation and reporting

Run Prettier on the affected files and git diff --check. For website changes, run from the website repository mint validate --disable-openapi, or report the exact fallback/timeout. When the README or repository contract changes, run the available focused repository contract tests.

Report the source language, the scope of synchronized files, validation results, and intentionally deferred translations. Do not commit or push unless the user explicitly requests it; when delivering, use comet-safe-delivery。