Hi, Thanks for looking into golang-x-tools.
Salsa CI does not yet have built-in reverse deps check, but you can see an experimental one we tested in https://salsa.debian.org/go-team/packages/golang-golang-x-net/-/merge_requests/1 to while planning to update golang-x-net. Running ratt manually is also always and option. Probably the best strategy is to run the reverse builds to map out how many packages have issues, and then prepare to upload golang-x-tools to experimental first, and quickly follow-up with fixes/updates on the broken packages, and once all works upload everything to unstable.
