build: scaffold Spigot plugin project

design/log.md

@@ -20,3 +20,9 @@ description: Chronological record of significant Trigger Spawn design decisions.
 - Remind players with incomplete progression that remaining unique boss kills permanently reduce the `/spawn` cooldown.
 - Clear the active cooldown immediately after each newly credited unique boss kill.
 - When cooldown prevents `/spawn`, explicitly report that it is unavailable and show the remaining wait in a friendly format.
+
+## 2026-08-08 — Build and release foundation
+
+- Added the Java 17 Gradle project targeting Spigot API 26.2, with JUnit 5 verification and versioned resource processing.
+- Added Gitea CI and semantic-release workflows modeled on `spigot-event-producer`.
+- Documented local builds, public releases, and the required `RELEASE_TOKEN` repository secret.

design/user-stories/us-007-build-and-release-plugin.md

@@ -2,7 +2,7 @@
 type: User Story
 title: "US-007: Build and release the plugin"
 description: Give maintainers repeatable Spigot 26.2 builds, automated verification, and versioned Gitea releases.
-status: backlog
+status: done
 ---
 
 # US-007: Build and release the plugin
@@ -11,14 +11,14 @@ As a **plugin maintainer**, I want automated builds and releases so that tested,
 
 ## Acceptance criteria
 
-- [ ] The Gradle project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
-- [ ] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
-- [ ] Pushes and pull requests build and test the plugin in Gitea Actions.
-- [ ] Pull requests validate conventional commit messages.
-- [ ] CI stores a development JAR as a workflow artifact.
-- [ ] Main-branch conventional commits drive semantic versioning.
-- [ ] A successful release builds a versioned JAR and attaches it to the corresponding Gitea release.
-- [ ] The build and release workflow follows the established `spigot-event-producer` project pattern where applicable.
+- [x] The Gradle project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
+- [x] Automated JUnit 5 tests run as part of the Gradle check lifecycle.
+- [x] Pushes and pull requests build and test the plugin in Gitea Actions.
+- [x] Pull requests validate conventional commit messages.
+- [x] CI stores a development JAR as a workflow artifact.
+- [x] Main-branch conventional commits drive semantic versioning.
+- [x] A successful release builds a versioned JAR and attaches it to the corresponding Gitea release.
+- [x] The build and release workflow follows the established `spigot-event-producer` project pattern where applicable.
 
 ## Related