Make local setup match the pipeline
A local environment that diverges from CI, aligned so a fresh checkout reaches green with one command.
The ticket
Align local development setup with the pipeline so both run the same versions and commands.
Acceptance criteria
- A fresh checkout reaches a green suite with one documented command
- Tool versions are pinned identically for local and CI
- The same commands run in both places
- The setup is verified on a clean machine or container
What lands as proof
A clean-environment run reaching green with one command, which is the only honest test of setup instructions.
Why teams defer it
- Everyone's machine already works, so the gap is only felt by whoever joins next.
- Verifying it needs a clean environment, which is a step people skip.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: align local development setup with the pipeline so both run the same versions and commands. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means a fresh checkout reaches green with a single command, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.