feat(admin): add game lifecycle controls

design/log.md

@@ -6,6 +6,17 @@ description: Chronological record of material decisions affecting the Spigot Tyr
 
 # Spigot Tyrant Design Log
 
+## 2026-08-14 — Administrative lifecycle completed
+
+- Completed US-001 with permission-gated `/tyrantadmin` start, status, pause, resume, and confirmed reset operations.
+- Initial Vigilantes may be assigned explicitly or selected among eligible recently active players, with offline selections persisted as pending confirmations.
+- Pause/resume preserves progression and assignments, shifts every cooldown, participation, inactivity, and pending-selection deadline, and invokes managed effect suppression/restoration.
+- Added detailed operator status output and verified lifecycle, timer shifting, permissions, confirmation safety, candidate filtering, metadata, and effect hooks with the Gradle suite.
+
+## 2026-08-14 — Administrative lifecycle implementation started
+
+- US-001 begins with test-first game start, pause/resume deadline freezing, permission-gated administration, inspection, and confirmed reset behavior.
+
 ## 2026-08-14 — Tyrant class assignment completed
 
 - Completed US-004 with `/tyrant assign <class> <player>`, purchased-class authorization, UUID state, one holder per class, and one Tyrant-side class per player.

design/user-stories/us-001-start-pause-and-administer.md

@@ -2,7 +2,7 @@
 type: User Story
 title: "US-001: Start, pause, and administer the game"
 description: Give server operators safe control over the Tyrant game's lifecycle and state.
-status: backlog
+status: done
 ---
 
 # US-001: Start, pause, and administer the game
@@ -11,14 +11,14 @@ As a **server operator**, I want to start, pause, resume, and inspect the game s
 
 ## Acceptance criteria
 
-- [ ] An administrator can start the first game by assigning the initial Tyrant.
-- [ ] The administrator may assign the first Vigilante or allow random selection from eligible recently active players.
-- [ ] An administrator can pause and resume the game without deleting game state.
-- [ ] Pausing freezes progression, cooldowns, daily-use timers, inactivity checks, and pending-selection deadlines.
-- [ ] Role and class effects are suppressed while paused and restored when play resumes.
-- [ ] Administrative commands require the `spigottyrant.admin` permission, granted to server operators by default.
-- [ ] Administrators can inspect lifecycle state, roles, classes, Followers, purchases, levels, cooldowns, participation, and pending selections.
-- [ ] Destructive administrative operations require explicit confirmation.
+- [x] An administrator can start the first game by assigning the initial Tyrant.
+- [x] The administrator may assign the first Vigilante or allow random selection from eligible recently active players.
+- [x] An administrator can pause and resume the game without deleting game state.
+- [x] Pausing freezes progression, cooldowns, daily-use timers, inactivity checks, and pending-selection deadlines.
+- [x] Role and class effects are suppressed while paused and restored when play resumes.
+- [x] Administrative commands require the `spigottyrant.admin` permission, granted to server operators by default.
+- [x] Administrators can inspect lifecycle state, roles, classes, Followers, purchases, levels, cooldowns, participation, and pending selections.
+- [x] Destructive administrative operations require explicit confirmation.
 
 ## Related