Packaging providers
Providers build as wasm32-wasip2 components. Providers packaged with omnifs are indexed from their embedded manifests.
Local build
Section titled “Local build”Use provider checks while authoring:
just providers-checkjust providers-buildProvider tests compile for wasm32-wasip2, but WASM tests do not execute in the normal host test harness. Use host-compatible unit tests for logic that needs to run locally.
Provider packaging
Section titled “Provider packaging”Providers packaged with omnifs are indexed from their embedded manifests. Use the provider catalogue for documented path surfaces.
The test provider is internal test infrastructure, not a documented provider surface.
Third-party distribution
Section titled “Third-party distribution”Standalone third-party provider packaging and publishing is still stabilizing. Do not assume there is a public npm publishing path for providers yet.
For now, treat provider packaging docs as component build docs. Standalone third-party provider distribution is not a supported public workflow.