operations
The engineering loop
Fast local feedback and deep scheduled evidence are separate tool profiles, not one bloated default installation.
- Question
- Which proof belongs at edit, commit, CI, security, and performance time?
- Binding decision
- Stable rustfmt, strict Clippy, rust-analyzer, Nextest, doctests, mise, Task, and prek form the baseline.
- Owner input
- Product-specific property, model, fuzz, chaos, and benchmark owners activate with the runtime slice they prove.
- 01Providerquota / outagepause bounded work
- 02QuestDBcommit laghold durable watermark
- 03Redisloss / trimquery authority or resync
- 04Ownerlease expiryfence and reacquire
- 05Viewerqueue pressureshed, resync, or close
Essentials stay fast
The base profile pins Rust 1.97, rustfmt, Clippy, rust-analyzer, rust-src, Task, prek, jq, and Nextest. CI adds coverage and sccache. Security adds cargo-deny and cargo-audit. Developer, debug, and performance profiles activate only for their owning investigation.
- Bacon watches the edit loop; cargo-expand inspects macros.
- Hyperfine measures process paths; Samply and flamegraph explain profiles.
- cargo-testdox communicates behavior; cargo-mutants challenges meaningful suites.
Evidencedocs/dev/testing.md and mise profile files.
Specialists need activation evidence
Proptest, fuzzing, Loom or Shuttle, Turmoil or Madsim, testcontainers, wiremock, Criterion or Divan, and iai-callgrind attach to a named risk. syn, autocfg, valuable, nom, Steel, and Lurk remain explicitly rejected from the baseline until their narrow triggers exist.
- A tool names its problem, owner, command, CI placement, cost, and removal condition.
- Coverage is diagnostic rather than a vanity threshold.
- Benchmark changes require a representative release workload.
Evidencedocs/dev/invariants.md and docs/dev/rust-rule-map.md.
mise x -- task verifyPinned tools, formatting, architecture, prompt, lint, tests, state, and diff integrity pass.