nordisk/holger

holger-znippy-docker-repository — crate card

Reverse-engineered (from source — verify, don't trust the name)

• One-line pitch: znippy-archive-backed OCI / Docker registry (read path) implementing the Registry HTTP API V2.
• Does: DockerRepoZnippy implements RepositoryBackendTrait serving GET /v2/ (version probe), /v2/{name}/tags/list, /v2/{name}/manifests/{reference}, and /v2/{name}/blobs/{digest}. Content stored in the archive under the on-wire layout v2/{name}/manifests/{ref} and v2/{name}/blobs/{digest}. Read-only serve from an immutable archive (with_archive/with_reader).
• Key deps: traits, znippy-common, anyhow.
• Shape: lib, single lib.rs. Shared znippy-backend pattern.
• Observed role in the workspace: Registered in server-lib as repository-znippy-docker. The writable/push OCI counterpart is the disk-backed holger-file-oci-repository.

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: