From https://mongodb.slack.com/archives/C05V4F6GZ6J/p1744210498373119

There are some buildscripts targets that don't run in CI (maybe this is the actual problem), but you can end up accidentally breaking them by removing files they list as sources, with no way to know.

Then if you do something like ` bazel test --test_tag_filters=server-programmability //...` locally it will fail.

See linked bug for an example of this.

Initial ideas:

• Just have a nightly build of //...
• Add our own linter check, essentially the inverse of https://github.com/10gen/mongo/blob/master/bazel/wrapper_hook/lint.py#L53. A good starting point might also be `bazel query 'labels(srcs, //buildscripts/...)'`