nordisk/holger

xtask — crate card

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

• One-line pitch: The workspace's cargo xtask helper — proto codegen plus a local test/bench runner for solo dev.
• Does: Verb dispatch in main.rs. gen-proto is the ONLY place proto codegen happens: gen_proto.rs uses protox (pure-Rust protobuf parse, no protoc binary/subprocess) to turn proto/holger.proto into a FileDescriptorSet, then tonic-build::compile_fds emits the committed server/lib/src/generated/holger.v1.rs — so a normal cargo build compiles only checked-in generated code. Any other args fall through to the local test flow (workspace tests, tar.zst integration test, znippy throughput bench, --heavy). The regression gate moved to nornir's warehouse; examples/nornir-bench.rs is the release-gate-equivalent bench.
• Key deps: protox, tonic-build, prost-types (codegen); dev: nornir, nornir-testmatrix, holger-bench-scenarios[nexus,artifactory], tokio, blake3.
• Shape: bin (xtask, publish=false), main.rs + gen_proto.rs, plus examples/nornir-bench.rs.
• Observed role in the workspace: Dev tooling. The proto-regeneration entrypoint and the local bench harness feeding nornir bench run holger.

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: