znippy-decompress — crate card
Reverse-engineered (from source — verify, don't trust the name)
- One-line pitch: The read path — a thin public façade that reconstructs files from a
.znippyarchive. - Does: Exposes
decompress_archive(full extract, verify on) anddecompress_archive_filtered(selective extract of only the files whose(pkg_type, repo)sub-index matches anIndexFilter). Both delegate straight toznippy_common::decompress_archive*— the actual decompress engine lives in znippy-common. - Key deps:
znippy-common(does all the real work),anyhow. - Shape: lib, tiny (~20 LOC total):
lib.rsre-exports,unpacker.rsholds the two wrapper fns. - Observed role in the workspace: Called by the CLI for the
decompressverb. Exists as the stable public entry point for reading; the heavy lifting is in znippy-common'sdecompress.rs.
Fill in (one line each — only the human knows these)
- Primary consumer(s):
- Why it exists (vs the obvious alternative):
- Hard constraint (airgap / no-C-deps / no-FFI / pure-Rust / etc.):
- Release cadence & independence (rides a parent? own repo someday?):
- Status (production / prototype / experimental / stubbed):
- Must-NOT-change invariant:
- Biggest known gap or TODO:
- Anything a newcomer would get wrong about it: