Context
AGENTS.md has no section on Evergreen CI.
Definition of done
AGENTS.md contains:
- A CI (Evergreen) section covering: .evergreen/config.yml as the single CI entry point, validated with evergreen validate -p mongo-go-driver -f .evergreen/config.yml.
- Both submodules (`.evergreen/drivers-evergreen-tools` (DET) provides every server-provisioning script; `testdata/specifications` provides spec-test fixtures.) being pinned by commit, CI using the pins rather than upstream master, and task init-submodule for local inspection.
- The procedure for adding a server version.
Pitfalls
What should the implementer watch out for? What are the risks?