test(config): verify runtime persistence safety

design/user-stories/us-006-configure-and-persist-leaf.md

@@ -2,7 +2,7 @@
 type: User Story
 title: "US-006: Configure and persist Leaf"
 description: Provide validated configuration and durable, defensive storage for Leaf behavior.
-status: in-progress
+status: done
 ---
 
 # US-006: Configure and persist Leaf
@@ -13,13 +13,13 @@ As a **server operator**, I want Leaf settings and player state to be validated
 
 - [x] Configuration supports the global enabled state, Resistance strength, leaf prefix, onboarding duration, and player-facing messages.
 - [x] Resistance strength defaults to level I and accepts only Minecraft Resistance levels I through V.
-- [ ] Runtime changes made through `/leaf enabled` and `/leaf strength` are persisted for subsequent restarts.
+- [x] Runtime changes made through `/leaf enabled` and `/leaf strength` are persisted for subsequent restarts.
 - [x] UUID-keyed player state persists the latest known name, saved opt-in choice, administrative lock, and first-join timestamp.
 - [x] Date-times use RFC 3339 UTC notation with a `Z` suffix.
 - [x] State is saved safely so that a failed write does not replace valid persisted state with a partial document.
 - [x] Invalid required configuration prevents partial plugin initialization and produces a clear server log message.
 - [x] Corrupt or invalid player records are handled defensively and cannot silently grant protection or privileges.
-- [ ] Removing Leaf-managed Resistance does not remove a distinct Resistance effect that Leaf does not own when the API provides enough information to distinguish it.
+- [x] Removing Leaf-managed Resistance does not remove a distinct Resistance effect that Leaf does not own when the API provides enough information to distinguish it.
 - [x] Unknown forward-compatible configuration and player-state fields are preserved where practical.
 
 ## Related