Is there any guidance on whether included projects used for build-logic should include the gradle wrapper?

I symlink the wrapper all the way down... But I think that fails spectacularly on windows

Fwiw, Gradle doesn't include the wrapper in their build-logic included builds: https://github.com/gradle/gradle

The idomatic gradle project doesn't include it either: https://github.com/jjohannes/idiomatic-gradle I am also able to run

./gradlew

subcommands from included builds and also open it in the IDE without the wrapper files present.

You can call tasks into the included build (from the including build): https://github.com/gradle/gradle/blob/f7fc6802260dd7fb49b3b567275f4001ccb0bfd0/CONTRIBUTING.md#debugging-gradle (not sure if that requires the included build to at least assemble without error or not)

To be verified, but iirc the wrapper properties fine might be important, the rest not so much, and that even if you do not open the project separately in the IDE, but also when opening the including project. Unless something changed afair at least IJ sometimes does not use the Gradle version of the including build, but something else, maybe the IJ built-in version, in some situations. I don't remember which, maybe during sync, or when executing a task in the included project directly. So it might be necessary in that case to tell the IDE the correct version to be used.

Good point; I wouldn't be too surprised if executing a task of the included project didn't go through the including project. I personally rarely execute tasks right from the IDE, which could explain that I never had that problem.