Summary

Contributors have no single, documented entry point for common local development tasks (setting up their environment, linting, verifying a server is reachable). Setup steps are scattered across a contributing guide and shell scripts, and previously pulled in dependencies unrelated to the task at hand. We want simple, consistent commands for these workflows, used consistently by both contributors and CI.

Motivation

Who is the affected end user?

Contributors to drivers-evergreen-tools, both MongoDB engineers and external contributors.

How does this affect the end user?

They have to piece together multiple manual steps and undocumented scripts to get a working local setup, lint their changes, or confirm a server is actually reachable, which is confusing and inconsistent with what CI does.

How likely is it that this problem or use case will occur?

Every contributor hits this during initial setup and on every PR.

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance and wasted time; no production impact since this is contributor tooling only.

Is this issue urgent?

No fixed timeline.

Is this ticket required by a downstream team?

No, this is internal to drivers-evergreen-tools' own contributor workflow.

Is this ticket only for tests?

No - it has functional impact on the setup/lint/verification workflow and how CI exercises it, not just test coverage.

Acceptance Criteria

• A single command sets up everything needed for local development.
• A single command runs linting.
• A single command verifies connectivity to a running server.
• CI uses these same commands wherever appropriate for consistency with local development.