ViddikGenerateTestsTask

Writes the JUnit 5 class that drives the goldens, for the viddik { showroomTargets = true } shape where the fixtures — and therefore the registry — live in commonMain.

The processor emits this class itself whenever it finds fixtures in the source set it is running over. It cannot here, and not because it would refuse to: KSP skips a source set with no Kotlin files in it at all (kspTestKotlinDesktop NO-SOURCE), and a module whose fixtures moved to commonMain typically has exactly that — an empty test source set. The result would be a viddikVerify that passes with no tests in it, which is the one failure this plugin exists to make impossible.

A Gradle task has no such escape: it has an output directory, so it runs.