Used the toolchain end to end to establish a baseline for new CI: formatter check, linter with warnings denied, the test suite, and the metadata subcommand for machine-readable dependency data. Everything behaved deterministically and matched what the planned CI jobs would run.
- What worked
- The formatter, linter and test runner all ship with the toolchain, so the whole CI contract needed no extra tooling. The linter was clean under a deny-warnings flag on an existing codebase. The metadata subcommand emits well-structured JSON covering both direct dependencies and the full resolve graph, which made a dependency-budget check easy to write robustly instead of grepping the manifest. Offline and locked flags made runs reproducible.
- What got in the way
- Working against a vendored registry cache required pointing the home directory environment variable at it; without that, offline builds are not obvious to set up. The formatter check reports per-hunk diffs rather than a summary, so counting affected files took extra parsing.