Struct Catalog 

pub struct Catalog { /* private fields */ }

A local block catalog rooted at a directory. This type has no opinion about environment variables or home directories — the caller (the CLI) decides where root points.

Implementations

impl Catalog

pub fn open(root: impl Into<PathBuf>) -> Self

Open (without yet creating on disk) a catalog rooted at root.

pub fn add( &self, name_version: &str, artifact_path: &Path, engine: &Engine, ) -> Result<AddOutcome, CatalogError>

Catalog the artifact at artifact_path under name_version.

engine is only used if the artifact turns out to be a wasm block — a bundle’s signature is read straight from its own manifest, never wasm-instantiated (bundle bytes are a custom container, not a wasm module; instantiating them would simply fail to parse).

pub fn list(&self) -> Result<Vec<(String, Entry)>, CatalogError>

List every cataloged entry, in deterministic (sorted-by-name@version) order.

pub fn show(&self, name_version: &str) -> Result<Entry, CatalogError>

Look up one entry’s cached Entry by exact, case-sensitive name@version — a catalog name is an opaque string, like a version is; no case-folding, no normalization.

pub fn read_blob(&self, entry: &Entry) -> Result<Vec<u8>, CatalogError>

Read an entry’s raw bytes back out of the blob store. The catalog’s only way to get from an Entry to actual artifact bytes — blobs/ stays an implementation detail, same as add() already hides write_blob.

pub fn rm(&self, name_version: &str) -> Result<(), CatalogError>

Remove a name@version from the index. The blob it pointed at is left on disk — no garbage collection in v1 (an orphaned blob is wasted space, not a correctness problem; see the design doc).

pub fn resolve( &self, s: &str, context: ResolutionContext, ) -> Result<Resolved, CatalogError>

Resolve one pipeline entry string per the catalog spec’s three-step algorithm: direct path/.wasm/.cfbundle first, then an exact catalog lookup if @version is present, then latest-by-created_at if it’s not and context allows an unqualified name.

A compiled-artifact suffix (.wasm or .cfbundle) is always treated as Direct, even when nothing actually exists at that path — a genuinely missing artifact should fail with a clear “no such file”, not be silently reinterpreted as a catalog name that happens to contain a . in it. Both suffixes get identical treatment here: pipeline::resolve_and_load’s own decision to prefer a joined path for one of these suffixes (even before checking existence) is only correct if this function honors the same suffixes the same way.