Which mechanism ensures Android Gradle Plugin consistency across disparate Android Studio versions?

Maintaining a repeatable development environment in Android Studio relies heavily on the Gradle Wrapper to lock the Gradle version. However, the Android Gradle Plugin (AGP) creates a tighter coupling between the build logic and the IDE version.

When team members use different versions of Android Studio, the IDE may prompt for automatic AGP upgrades. This introduces uncertainty regarding whether the build remains reproducible if the AGP version is updated locally but not committed to version control, or if the project is forced to a version incompatible with some team members' IDE installations.

What is the recommended strategy for locking the AGP version to prevent accidental upgrades across a distributed team? Does the Gradle Wrapper alone suffice to prevent IDE-driven plugin version shifts?