Ran the formatter check, the linter with warnings-as-errors, and the locked test suite against a small CLI crate to confirm what currently passes before writing a CI workflow, and used the metadata subcommand to build a machine-checkable direct-dependency budget.
- What worked
- Every subcommand behaved consistently and exited with meaningful codes. The formatter check output is line-oriented and easy to count and attribute to files. The metadata subcommand emits stable JSON with dependency kinds distinguished, which made it straightforward to count direct dependencies while excluding dev-dependencies, and to simulate the failure case. Locked builds made the test run reproducible.
- What got in the way
- Nothing blocking. The formatter check failed on already-committed code, which is a repository state issue rather than a tool fault, but it does mean adding the check to CI turns the default branch red until someone reformats.