What it is
dev-tools is the convenient one-import entry point for the dev-*
verification suite. Pick the features you need; pull them in with a
single dependency.
The suite gives an AI agent (or a CI gate) machine-readable evidence about a Rust project:
- Did it compile?
- Did tests pass?
- Did performance regress?
- Did async code hang?
- Did the system collapse under load?
- Did failure recovery work?
Quick start
[]
= "0.1"
Default features include fixtures, bench, and the always-on
report schema.
use ;
// Build a report.
let mut r = new
.with_producer;
// Spin up a deterministic temp environment.
let project = new
.with_file
.build
.unwrap;
// Run a benchmark and add the verdict to the report.
let mut b = new;
for _ in 0..1000
let result = b.finish;
r.push;
r.finish;
println!;
Features
| Feature | Default | What it brings in |
|---|---|---|
report |
always | dev-report — schema |
fixtures |
yes | dev-fixtures — test environments |
bench |
yes | dev-bench — performance |
async |
no | dev-async — async validation |
stress |
no | dev-stress — load testing |
chaos |
no | dev-chaos — failure injection |
full |
no | all of the above |
Common feature combinations
Async-heavy project:
= { = "0.1", = ["async"] }
Kitchen sink (CI verification rigs, AI agents):
= { = "0.1", = ["full"] }
Schema-only (lightest possible):
= { = "0.1", = false }
Why a verification suite
AI can generate code quickly. Without verification, AI-generated code can:
- Compile but behave incorrectly
- Pass simple tests but fail under load
- Introduce performance regressions
- Break async shutdown
- Leak memory
- Hide race conditions
- Look clean while being fragile
The dev-* suite gives an AI agent a structured way to validate its
own work before a human has to trust it.
Status
v0.1.x is a name-claim release across all sub-crates. APIs WILL
expand significantly in 0.2.x and beyond. Production use is
discouraged until 1.0.
License
Apache-2.0. See LICENSE.