Validate an extension before integration
The preflight uses the same SDK contract as the platform to distinguish an invalid extension from a valid extension that is still incomplete for partner review.
Run the preflight
cd cli node src/index.js extension check ../plugins/acme_pay # CI-friendly output node src/index.js extension check ../plugins/acme_pay --output json
Blocking errors
An error in extension.yaml, its runtime projection, a channel, a permission api_in, a config field, or an invalid contribution immediately fails the command. Fix the reported errors, regenerate the relevant files, then run validation again.
Readiness warnings
An extension may be structurally valid but not ready for distribution. The preflight currently flags cases such as missing capabilities, missing channels for an integration, missing contributions, undeclared marketplace metadata, or generated projections that have become stale. In the latter case, run extension generate before validating again. These warnings add no runtime right or requirement.
Mode strict
node src/index.js extension check ../plugins/acme_pay --strict
Strict mode turns readiness warnings into a CLI failure. It is useful in CI when your team has decided that an extension must have progressed beyond the scaffold stage. It does not yet constitute Ormuz certification.