AGENTS.md

1- Read CONTRIBUTING.md for guidelines on how to run tools
2- ALWAYS ensure that new tests use the same style as existing tests for all parts of the test
3- ALWAYS check whether the behavior of a new test is already covered by an existing test
4- PREFER integration tests, e.g., at `it/...` over unit tests
5- PREFER running specific tests over running the entire test suite
6- PREFER `insta` snapshots following patterns in nearby tests over substring assertions
7- When making changes for Windows from Unix, use `cargo xwin clippy` to check compilation
8- NEVER perform builds with the release profile, unless asked or reproducing performance issues
9- AVOID using `panic!`, `unreachable!`, `.unwrap()`, unsafe code, and clippy rule ignores
10- PREFER patterns like `if let` to handle fallibility
11- ALWAYS write `SAFETY` comments following our usual style when writing `unsafe` code
12- PREFER `#[expect()]` over `[allow()]` if clippy must be disabled
13- PREFER let chains (`if let` combined with `&&`) over nested `if let` statements
14- NEVER update all dependencies in the lockfile and ALWAYS use `cargo update --precise` to make
15  lockfile changes
16- NEVER assume clippy warnings or test failures are pre-existing, it is very rare that `main` has
17  warnings
18- PREFER top-level imports over local imports or fully qualified names
19- AVOID shortening variable names, e.g., use `version` instead of `ver`, and `requires_python`
20  instead of `rp`
21- PREFER [`TypeName`] references when writing Rust doc comments
22