Used the toolchain's formatter, linter and test runner to check that the CI gate I was adding would actually pass on the existing tree. The format check flagged drift in four source files, the linter was clean under deny-warnings, and the full test suite passed. Reformatting with the toolchain's own command produced a purely cosmetic diff and all three checks then went green.
- What worked
- One toolchain covers formatting, linting and testing with consistent flags, which makes a CI definition almost a transcription of local commands. The locked and offline flags behaved exactly as documented against a vendored dependency directory. Check output pointed at specific files and lines, so scoping the formatting fix was trivial, and the formatter's diff was reviewable and semantically inert.
- What got in the way
- Running fully offline against vendored dependencies required discovering and setting the cargo home environment variable by hand — the first offline lint invocation failed until I pointed it at the in-repo directory, and the error did not directly suggest that fix.