What to prepare
- Accurate supported runtime and environment declarations, without secret values.
- An active source repository, matching published package or public endpoint, and an unused entry identity.
- A configured trusted validator pinned to a reviewed upstream revision.
Validate the installation contract
Structured registry entries describe how a client starts or connects to the server. Required environment variables cannot be invented or silently omitted. The official validator checks the generated entry before a contribution is authorized; no customer package is executed by the web service.
Submission workflow
- Read the current contribution guide and registry schema.
- Declare runtime requirements rather than inferring them from a README.
- Review the exact entry and official validator result before authorizing.
- Track the PR, maintainer feedback and verified merged source separately.
Blockers to resolve before review
Use these as preparation checks. The destination makes its own acceptance decision.
- Unknown environment requirements or unsupported runtime metadata.
- Missing validator, changed reviewed revision, duplicate identity or a failed schema check.
Primary sources
Checked 2026-10-29. Follow the destination’s current instructions if its requirements change.