nordisk/znippy

znippy-tests — crate card

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

• One-line pitch: The workspace's integration + benchmark suite crate (package name znippy-tests, dir tests/), plus the fstatus bridge into the nornir test matrix.
• Does: src/lib.rs exports fstatus(component, check, ok, detail) — a one-line wrapper over nornir_testmatrix::functional_status that, with the testmatrix feature ON, appends a real matrix row per checked assertion, and with it OFF compiles to an #[inline(always)] no-op (release path). The tests/ dir holds the actual integration tests (integration_test, plugin_integration_test, plugin_read_api_test, plugin_decompress_bomb_test, repro_crate), benches (maven_bench, sign_throughput_bench), and testmatrix_wiring; examples/quality_matrix.rs runs znippy's own quality matrix.
• Key deps: znippy-compress, znippy-common (host-decompressors), znippy-plugin-maven/-python, nornir-testmatrix 0.2 (patched to local sibling), plus fixture builders flate2/tar/bzip2/miniz_oxide, io-uring/libc, walkdir, tempfile.
• Shape: lib (publish = false), tiny src/lib.rs (30 LOC) — the weight is the tests/ and examples/ targets.
• Observed role in the workspace: Not published; the cross-crate test/bench harness. Its sign and testmatrix features pass through to znippy-common/nornir-testmatrix so real check results feed the nornir functional matrix.

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: