Tazel Plugins stay, built with Gradle and published to Tazel Portal.
The api/ (com.progmasoft.tazel:tazel-api) and gradle-plugin/
(com.progmasoft.tazel.plugin) projects come from Progmasoft/tazel-legacy
with their tests, with these changes:

- tazelPlugin { } holds group, name and version. The descriptor
  META-INF/tazel-plugin.properties records them first, so the JAR says
  who the plugin is; before, ViGet recorded the publisher, name and
  version at push time. The group must be a reversed domain of at least
  two parts (Tazel Portal checks the namespace by the Sonatype rules),
  the name letters, digits and _ . -, and the version a Semantic
  Version. The version of the Gradle project is not the plugin's.
- The API version starts again at 1, so plugins built for the legacy
  Tazel (API 3) are not loaded.
- Documentation no longer speaks of ViGet, Tala targets or
  tazel.tala.run; the site is tazel.net.
- Dependency locking of the legacy build is not carried over, like in
  the rest of this build.

The root build includes both projects, so ./gradlew check runs the
Gradle TestKit tests of the plugin as well.

Tazel restarts as a build system and package manager for C, C++,
Objective-C, Objective-C++ and Zig, with MODULE.kts and BUILD.kts project
files and labels such as //app/:greeter. The earlier Tazel, the build system
of Tala (0.1.0 to 0.4.0.3), is archived as Progmasoft/tazel-legacy, with its
history and releases.

This first commit holds the build of the program only: Gradle 9 with the
Kotlin JVM plugin (JDK 25, warnings as errors), Spotless, JaCoCo, the
Kotlin scripting libraries the project files will need, Mordant, and an
entry point that answers version and help and refuses anything else with
exit code 2. CI runs gradlew check installDist on Linux, Windows and macOS;
CodeQL, zizmor and Dependency Review come from the earlier repository.
The license is MPL-2.0 WITH AdditionRef-Progmasoft-Exception-2.0.