Writing and publishing packages

A package is laid out as shared/ is, so one set of rules covers the app and every package, and the compiler checks a package as it checks shared/.

A package lives in its own repository.

The registry at jadpo.dev holds public Jadpo packages of both kinds.

The verifier is jadpo package verify, the same tool authors run, in a container image published with each Jadpo release.

This is the detail behind The package format: exactly how Jadpo reads a package's folder, its names and the lock.

What a package's surface record holds, how its version is worked out, and what jadpo package check and jadpo package show do.

This is the detail behind What a release shows, The changelog, Search and The verifier: what jadpo package check prints above its bar, and what jadpo package verify --json writes.

This is the detail behind Installing and updating from the registry, Yanks, takedowns and advisories, Search and Developing for the registry: what each command does and shows.

What a package action may call, how the app calls one, and how jadpo package recipe copies a recipe into your project.

What a package's own subscribers hear and emit, and how jadpo package check compiles a package's recipes in its sample/ app.

A recording is a provider's answer to one operation with its plain values replaced by placeholders, so its decoding can be checked without calling the provider.