xtask — crate card
Reverse-engineered (from source — verify, don't trust the name)
- One-line pitch: The workspace's Rust build/deploy automation (
cargo xtask <cmd>) — replaces YAML CI entirely with typedstd::processcommands. - Does:
demo-wasmbuilds thefacett-demorelease wasm bundle intodist/(index.html + wasm-bindgen JS glue + .wasm).deploy-pagesruns demo-wasm then publishesdist/to the repo'spagesbranch (single squashed, force-pushed commit) served at nordisk.codeberg.page/facett. Self-checks/bootstraps thewasm32-unknown-unknowntarget and awasm-bindgenCLI matching the Cargo.lock version (the #1 blank-canvas cause). A tiny hand-rolled arg match. - Key deps: None — deliberately dependency-free (std + shelling out to cargo/wasm-bindgen/git), no async, no clap.
publish = false. - Shape: bin, single file (main.rs, ~467 lines).
- Observed role in the workspace: Workspace-level tooling; owns the live web-demo publish pipeline. Runbook in
.nornir/live-demo.md.
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: