nordisk/znippy

xtask — crate card

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

• One-line pitch: The cargo xtask host — now just the shell for the workspace's single nornir benchmark suite; the old regression gate/runner was removed.
• Does: src/lib.rs is intentionally empty (exports nothing) — it exists only so the package has a lib target the bench/example can build against. The real content is examples/nornir-bench.rs (the release-gate bench runner subprocessed by nornir bench run znippy, emitting one nornir::bench::BenchRun JSON line, driving the osm-katana planet pipeline stage-by-stage) and benches/nornir.rs (cargo bench -p xtask, same suite).
• Key deps (dev): nornir (fixtures-maven), inventory, osm-katana, the zoomies decompressors (lbzip2/lgz/ljar/lzip-parallel/linflate), znippy-zoomies, znippy-common/-compress/-iceberg/-plugin-maven, arrow+parquet 58, memmap2, io-uring.
• Shape: lib (publish = false), src/lib.rs ~16 LOC (doc-only); the weight is the nornir-bench example and nornir bench target.
• Observed role in the workspace: Dev/CI only — the benchmark entry point wired to nornir's release gate and bench_history.jsonl. Not a dependency of any shipping crate.

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: