docs(build): complete Leaf delivery stories

design/index.md

@@ -1,4 +1,7 @@
 ---
+type: Index
+title: Leaf Design
+description: Progressive entry point for the Leaf OKF knowledge bundle.
 okf_version: "0.1"
 ---
 

design/log.md

@@ -1,3 +1,9 @@
+---
+type: Log
+title: Leaf Design Log
+description: Chronological decisions and implementation verification for Leaf.
+---
+
 # Leaf Design Log
 
 ## 2026-08-10
@@ -72,3 +78,10 @@
 - Leaf records only effects it successfully installs, removes them only while the visible fingerprint matches, and preserves distinct Resistance effects; Spigot's identical-effect ownership limitation is documented.
 - Durable player state now retains prior names in addition to the required UUID, latest name, choice, lock, and RFC 3339 first-join timestamp.
 - Verified settings failure safety, durable aliases, existing defensive YAML behavior, strict compilation, and the full build with `./gradlew clean check jar`.
+
+### US-007 build and release completed
+
+- Verified dedicated conventional implementation commits for protection, identity, combat, onboarding, administration, configuration verification, and logout cleanup in addition to the existing build foundation.
+- Added missing OKF type metadata to the reserved bundle indexes and design log.
+- Verified all user stories are done, all acceptance criteria are checked, the repository has no remote, and no push was performed.
+- Final verification passed with `./gradlew clean check jar` and local OKF v0.1 structural and link validation.

design/user-stories/index.md

@@ -1,3 +1,9 @@
+---
+type: Index
+title: Leaf User Stories
+description: Catalog of approved Leaf behavior and delivery stories.
+---
+
 # Leaf User Stories
 
 1. [US-001: Opt into Leaf protection](us-001-opt-into-leaf-protection.md)

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

@@ -2,7 +2,7 @@
 type: User Story
 title: "US-007: Build and release Leaf"
 description: Give maintainers repeatable Spigot builds, automated verification, and versioned Gitea releases.
-status: in-progress
+status: done
 ---
 
 # US-007: Build and release Leaf
@@ -21,7 +21,7 @@ As a **plugin maintainer**, I want automated builds and releases modeled on Spig
 - [x] A successful release builds a versioned Leaf 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 Leaf names and identifiers.
 - [x] The initial approved user-story bundle is kept in one documentation commit.
-- [ ] Subsequent implementation work is organized into a separate conventional commit for each implemented user story.
+- [x] Subsequent implementation work is organized into a separate conventional commit for each implemented user story.
 - [x] No remote push is performed until the maintainer confirms that the Gitea repository and release token secret are ready.
 
 ## Related