docs(design): complete initial user stories

design/user-stories/us-005-build-and-release.md

@@ -2,7 +2,7 @@
 type: User Story
 title: "US-005: Build and release the plugin"
 description: Give maintainers repeatable Purpur builds, automated verification, and versioned Gitea releases.
-status: in-progress
+status: done
 ---
 
 # US-005: Build and release the plugin
@@ -11,13 +11,13 @@ As a **plugin maintainer**, I want automated builds and releases modeled on Spig
 
 ## Acceptance criteria
 
-- [ ] Gradle compiles against Purpur API `26.2.build.2618-stable` using Java 25.
-- [ ] Compiler lint warnings fail the build and JUnit 5 tests run during `check`.
-- [ ] Gitea Actions verifies pushes and pull requests and stores a development JAR.
-- [ ] Pull requests validate conventional commits.
-- [ ] Main-branch conventional commits drive semantic releases and attach versioned JARs to Gitea releases.
-- [ ] The README documents requirements, recipes, configuration, building, and releases.
-- [ ] `./gradlew clean check jar` succeeds.
+- [x] Gradle compiles against Purpur API `26.2.build.2618-stable` using Java 25.
+- [x] Compiler lint warnings fail the build and JUnit 5 tests run during `check`.
+- [x] Gitea Actions verifies pushes and pull requests and stores a development JAR.
+- [x] Pull requests validate conventional commits.
+- [x] Main-branch conventional commits drive semantic releases and attach versioned JARs to Gitea releases.
+- [x] The README documents requirements, recipes, configuration, building, and releases.
+- [x] `./gradlew clean check jar` succeeds.
 
 ## Related