Create, amend, reword, split, squash, or prepare libcrafter commits with the repository's Conventional Commits policy and scoped staging discipline.
Add or run deterministic libcrafter packet behavior validation through oracle specs, reference backends, offline checks, pcap checks, probe plans, and artifacts.
Open, update, title, review, or prepare libcrafter pull requests so commits are ready for rebase-and-fast-forward landing and required validation is documented.
Use ignored .scratch workspaces for experiments, disposable prototypes, network probes, hardware exploration, generated code, and any task where the user asks for work that should not be committed until promoted.
Create, rename, check out, or prepare libcrafter branches and worktrees with typed branch names such as feature/slug or fix/slug instead of bare task names.
Publish the libcrafter crafter crate to crates.io only after the local release gate, cargo publish dry-run, package summary, ask-tool confirmation, and crates.io/docs.rs verification.