Packaging and submission

English reading guide. The complete Chinese specification remains the authoritative source for exact fields, examples, implementation status, and historical details. This page is a concise guide, not a full translation.

Prepare a reproducible review candidate

• Keep Manifest, package.json, and submission identity versions aligned. Stable appId and contribution IDs must survive renames and localization.

• Run independent validation, tests, type checks, builds, contract tests, and packaging using the plugin's existing commands and frozen dependencies.

• Before each review submission, write user-facing release notes from real changes and verification evidence. Keep retries of the same version and payload traceable.

• Source review, signing, platform approval, public release, and Host installation are separate states. Never reuse an old approval for changed bytes or bypass a rejection.

Continue reading

• Complete Chinese specification
• Documentation overview
• Plugin development
• API reference
• Packaging and submission

Source: docs/plugin-submission-v1.md.