build(project): scaffold plugin delivery

design/log.md

@@ -6,6 +6,16 @@ description: Chronological record of material decisions affecting the Spigot Tyr
 
 # Spigot Tyrant Design Log
 
+## 2026-08-14 — Build and release foundation completed
+
+- Completed US-013 with a Java 17 Gradle build, Spigot 26.2 API, strict compiler linting, JUnit 5 and Mockito dependencies, plugin metadata, and a minimal plugin entrypoint.
+- Added Gitea push and pull-request CI, conventional-commit validation, development artifacts, semantic versioning, and versioned Gitea release assets modeled on `../spigot-base/`.
+- Verified `./gradlew clean check jar`, a release-version `1.2.3` JAR and embedded plugin version, workflow delivery settings, and OKF conformance.
+
+## 2026-08-14 — Build and release implementation started
+
+- Approved implementation begins with US-013 and a test-driven Java 17, Gradle, Spigot, and Gitea Actions foundation modeled on `../spigot-base/`.
+
 ## 2026-08-14 — Initial game design
 
 - The game has one Tyrant and one Vigilante, with Followers aligned to the Vigilante and Assassin, Fixer, and Tamer classes assigned by the Tyrant.

design/user-stories/us-013-build-test-and-release.md

@@ -2,7 +2,7 @@
 type: User Story
 title: "US-013: Build, test, and release the plugin"
 description: Give maintainers repeatable builds, automated verification, and versioned Gitea releases.
-status: backlog
+status: done
 ---
 
 # US-013: Build, test, and release the plugin
@@ -11,15 +11,15 @@ As a **plugin maintainer**, I want automated builds and releases modeled on Spig
 
 ## Acceptance criteria
 
-- [ ] The Gradle Kotlin DSL project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
-- [ ] Compiler lint warnings fail the build.
-- [ ] Automated JUnit 5 and Mockito 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 `spigot-tyrant` 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.
-- [ ] Build files, Gradle wrapper, workflows, and release behavior follow `../spigot-base/` where applicable while using Spigot Tyrant names and identifiers.
+- [x] The Gradle Kotlin DSL project compiles against Spigot API `26.2-R0.1-SNAPSHOT` using a Java 17 toolchain.
+- [x] Compiler lint warnings fail the build.
+- [x] Automated JUnit 5 and Mockito 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 `spigot-tyrant` 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] Build files, Gradle wrapper, workflows, and release behavior follow `../spigot-base/` where applicable while using Spigot Tyrant names and identifiers.
 
 ## Related