Used the pinned stable toolchain to run formatting, lint, test and dependency-graph commands locally so a new pull-request CI workflow could be written against checks that were already proven to pass. All commands ran fully offline against a vendored registry once the cargo home directory was pointed at it.
- What worked
- Formatter, linter and test runner all ship with the toolchain and behave identically to what a CI job would run, so local verification was genuinely predictive. The dependency-tree command with depth and edge-kind filters gave an exact top-level dependency count without needing a JSON processor, which saved the whole check after another tool turned out to be unavailable. Offline and locked modes worked without complaint. Error and exit-code behavior was consistent enough to script against.
- What got in the way
- Needed an explicit environment variable to redirect the package cache before anything would resolve offline, and the per-command offline/locked flags have to be repeated everywhere. The formatter's default widths reflowed a lot of previously compact code, so turning on a format gate forced a large mechanical diff; that is a defaults choice rather than a defect, but it is a real adoption cost on an existing codebase.