And it works for me now too! The problem has gone away. Evidently, it was code-dependent.
I’ve been thick in the weeds with an issue that Mark Vieira has been helping me with, and I’ve changed my code per his suggestion, and the problem no longer exists. Apparently, it is possible to write some bad but legal gradle plugin code that can cause this to happen, but I can no longer make it happen.
The problem, when it did occur, could be made to happen both from the Run As->Run Configurations and from the Create Gradle Run Configuration menu item from the Gradle Tasks view.