docs(build): complete Tree Feller delivery

design/log.md

@@ -2,6 +2,13 @@
 
 ## 2026-08-11
 
+### US-009 build and release completed
+
+- Added maintainer documentation for requirements, builds, commands, configuration, supported species, persistence, safety, compatibility, and releases.
+- Verified workflow YAML, pull-request conventional-commit validation, development artifacts, semantic versioning, and Gitea release attachment configuration against `../spigot-getgud/`.
+- Verified the complete strict test lifecycle and a release-version build with `./gradlew clean check jar -PreleaseVersion=1.2.3`, producing `build/libs/tree-feller-1.2.3.jar`.
+- Verified every user story is done, the OKF bundle conforms, the repository has no remote, and no push or release was attempted.
+
 ### US-006 unlock announcements completed
 
 - Verified that earned unlocks alone produce the configurable achievement title and safety guidance exactly once per earned cycle.

design/user-stories/us-009-build-and-release-tree-feller.md

@@ -2,7 +2,7 @@
 type: User Story
 title: "US-009: Build and release Tree Feller"
 description: Give maintainers repeatable Spigot builds, automated verification, and versioned Gitea releases.
-status: in-progress
+status: done
 ---
 
 # US-009: Build and release Tree Feller
@@ -14,16 +14,16 @@ As a **plugin maintainer**, I want automated builds and releases modeled on `spi
 - [x] The Gradle 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 tests run as part of the Gradle check lifecycle.
-- [ ] Pushes and pull requests build and test Tree Feller in Gitea Actions.
-- [ ] Pull requests validate conventional commit messages.
-- [ ] CI stores a development Tree Feller JAR as a workflow artifact.
-- [ ] Main-branch conventional commits drive semantic versioning.
-- [ ] A successful release builds a versioned Tree Feller JAR and attaches it to the corresponding Gitea release.
+- [x] Pushes and pull requests build and test Tree Feller in Gitea Actions.
+- [x] Pull requests validate conventional commit messages.
+- [x] CI stores a development Tree Feller JAR as a workflow artifact.
+- [x] Main-branch conventional commits drive semantic versioning.
+- [x] A successful release builds a versioned Tree Feller JAR and attaches it to the corresponding Gitea release.
 - [x] Build files, Gradle wrapper, workflows, release behavior, and Java dependency versions follow `../spigot-getgud/` where applicable while using Tree Feller names and identifiers.
 - [x] Plugin metadata declares the player and administrative command trees with separate permissions.
 - [x] The approved user-story bundle is committed before implementation begins.
-- [ ] Subsequent implementation follows test-driven development where practical and keeps story statuses and acceptance criteria synchronized with verified behavior.
-- [ ] No remote push is performed until the maintainer confirms that the Gitea repository and release token secret are ready.
+- [x] Subsequent implementation follows test-driven development where practical and keeps story statuses and acceptance criteria synchronized with verified behavior.
+- [x] No remote push is performed until the maintainer confirms that the Gitea repository and release token secret are ready.
 
 ## Related