feat(commands): unify settings and admin commands

design/user-stories/us-002-unlock-base-navigation.md

@@ -17,10 +17,8 @@ As a **player with Base I**, I want visual guidance toward my base so that I can
 - [x] While enabled and in the base's world, particles are drawn along the ground to indicate the direction toward the base.
 - [x] Particle generation is bounded to avoid excessive server or client load.
 - [x] A player in another world receives a clear message instead of a misleading particle direction.
-- [x] `/basenavigation` toggles guidance on and off after Base II is unlocked.
-- [x] `/basenavigation on` enables guidance idempotently and `/basenavigation off` disables it idempotently.
-- [x] Invalid navigation arguments show command usage, and `on` and `off` are offered through autocomplete.
-- [x] `/homenavigation` aliases `/basenavigation` with identical behavior and autocomplete.
+- [x] `/basesettings navigation enable` enables guidance idempotently after Base II is unlocked, and `/basesettings navigation disable` disables it idempotently.
+- [x] Invalid navigation arguments show command usage, and `enable` and `disable` are offered through autocomplete.
 - [x] Grass-or-dirt progress after Base II preserves the player's selected navigation preference.
 - [x] The navigation preference persists across reconnects and restarts.
 

design/user-stories/us-004-unlock-and-control-base-flight.md

@@ -24,9 +24,8 @@ As a **player with Base I**, I want to unlock controlled flight around my base s
 - [x] Plugin-granted flight remains active in the warning buffer and displays prominent on-screen notice that the player is leaving the base.
 - [x] Passing beyond the warning buffer removes only flight granted by this plugin.
 - [x] Flight is not granted outside the unlocked vertical range.
-- [x] `/baseflight` toggles the player's unlocked base flight on and off.
-- [x] `/baseflight on` enables flight idempotently and `/baseflight off` disables it idempotently, with `on` and `off` offered through autocomplete.
-- [x] `/homeflight` aliases `/baseflight` with identical behavior and autocomplete.
+- [x] `/basesettings flight enable` enables unlocked flight idempotently, and `/basesettings flight disable` disables it idempotently.
+- [x] Invalid flight arguments show command usage, and `enable` and `disable` are offered through autocomplete.
 - [x] The flight toggle persists across reconnects and restarts.
 - [x] The plugin handles teleportation, world changes, game-mode changes, death, logout, and plugin shutdown without leaving unintended flight enabled.
 

design/user-stories/us-005-unlock-base-teleportation.md

@@ -15,7 +15,7 @@ As a **player with Base II**, I want to earn `/base` so that I can return safely
 - [x] Only placements made in Survival mode and within the base's current horizontal and vertical bounds count.
 - [x] Player-placed blocks and replacement of previously broken blocks may contribute repeatedly.
 - [x] Base III unlocks `/base` with a configurable 30-second warm-up and three-hour cooldown by default.
-- [x] `/home` is an alias for `/base`, including `/home upgrade`.
+- [x] `/home` aliases the teleport-only `/base` command.
 - [x] Looking around without changing block coordinates does not cancel the warm-up.
 - [x] Changing block X, Y, or Z, taking damage, teleporting, changing worlds, dying, disconnecting, or starting a conflicting teleport cancels the warm-up.
 - [x] Cancellation clearly informs the player and does not consume the cooldown.

design/user-stories/us-008-unlock-visitor-access.md

@@ -12,12 +12,11 @@ As a **player with Base III**, I want to open my base to visitors so that other
 ## Acceptance criteria
 
 - [x] Base IV requires Base III and an established base.
-- [x] `/base upgrade` offers the Base IV purchase for a configurable price that defaults to 128 diamonds.
+- [x] `/basesettings upgrade` offers the Base IV purchase for a configurable price that defaults to 128 diamonds, replacing `/base upgrade` and `/home upgrade`.
 - [x] A successful purchase removes the complete price atomically from the player's direct inventory.
 - [x] Insufficient funds, an invalid state, or a failed persistence operation does not consume any diamonds or grant Base IV.
-- [x] `/basevisitors` lets a Base IV owner toggle visitor access on and off.
-- [x] `/basevisitors on` enables access idempotently and `/basevisitors off` disables it idempotently, with `on` and `off` offered through autocomplete.
-- [x] `/homevisitors` aliases `/basevisitors` with identical behavior and autocomplete.
+- [x] `/basesettings visitors allowed` permits visitor access idempotently for a Base IV owner, and `/basesettings visitors blocked` blocks it idempotently.
+- [x] Invalid visitor arguments show command usage, and `allowed` and `blocked` are offered through autocomplete.
 - [x] The visitor-access preference persists across reconnects and restarts.
 - [x] `/gotobase <owner>` autocompletes bases that the requesting player is currently eligible to visit.
 - [x] `/visit <owner>` aliases `/gotobase <owner>` with identical autocomplete, including eligible bases whose owners are offline.

design/user-stories/us-009-view-progression-and-notifications.md

@@ -11,17 +11,20 @@ As a **player**, I want to inspect my progression and receive timely milestone f
 
 ## Acceptance criteria
 
-- [x] `/baseprogress` shows the player's Base, Base Size, Base Flight, Teleport Warm-up, and Teleport Cooldown paths.
+- [x] `/basesettings` and `/basesettings status` show the player's Base, Base Size, Base Flight, Teleport Warm-up, and Teleport Cooldown paths plus current visitor, navigation, flight, and boss-bar settings.
 - [x] Each path identifies earned levels, unmet prerequisites, current progress, the next threshold, and the next reward.
 - [x] Locked secondary paths clearly identify Base I or another sequential level as their prerequisite.
 - [x] Relevant qualifying activity briefly displays a configurable progress boss bar for the active milestone.
 - [x] Boss-bar text and fill accurately represent the current count and threshold and never exceed 100 percent.
 - [x] The automatic boss bar disappears after a configurable number of seconds.
-- [x] `/baseprogress bossbar` toggles automatic progress boss bars on and off.
-- [x] Disabling automatic boss bars does not prevent `/baseprogress` from displaying progress.
+- [x] `/basesettings bossbar enable` enables automatic progress boss bars idempotently, and `/basesettings bossbar disable` disables them idempotently.
+- [x] Invalid boss-bar arguments show command usage, and `enable` and `disable` are offered through autocomplete.
+- [x] Disabling automatic boss bars does not prevent `/basesettings` from displaying progress.
 - [x] The boss-bar preference persists across reconnects and restarts.
 - [x] Each newly unlocked level displays prominent full-screen title and subtitle text describing the reward.
 - [x] Unlock notifications occur once per earned level and do not repeat after reconnecting or restarting.
+- [x] `/homesettings` aliases `/basesettings` with identical behavior and autocomplete.
+- [x] Superseded `/baseprogress`, `/basenavigation`, `/baseflight`, and `/basevisitors` commands and their aliases are no longer registered.
 
 ## Related
 

design/user-stories/us-010-administer-player-progression.md

@@ -14,16 +14,20 @@ As a **server administrator**, I want command-based progression controls so that
 - [x] Administrative commands require `spigotbase.admin`, which server operators receive by default.
 - [x] Administrative player arguments safely resolve online players and previously known offline players.
 - [x] Player state remains keyed by UUID while retaining the latest known name for lookup and display.
-- [x] `/baseadmin progress <player>` displays the player's base, counters, earned path levels, active cooldowns, toggles, and visitor settings.
+- [x] `/baseadmin status <player>` displays the player's base, counters, earned path levels, active cooldowns, toggles, and visitor settings.
 - [x] `/baseadmin setlevel <player> <path> <level>` sets an earned path level while enforcing or explicitly granting required preceding levels.
 - [x] `/baseadmin setprogress <player> <path> <amount>` updates the selected counter and consistently evaluates reached tiers.
-- [x] `/baseadmin reset <player> <path>` resets a selected path without silently leaving benefits that require it.
+- [x] `/baseadmin reset <player> <size|flight|warmup|cooldown>` resets a selected path without silently leaving benefits that require it.
+- [x] `/baseadmin reset <player> base` is rejected and directs the administrator to the confirmed complete-reset command.
 - [x] `/baseadmin reset <player> all` removes the player's base, progression, active cooldowns, and plugin preferences after confirmation.
 - [x] Administrators can clear personal and visitor cooldowns independently.
 - [x] Administrative commands can update configured block requirements, warm-ups, and cooldowns for each level using validated values.
 - [x] Runtime configuration changes are persisted for subsequent restarts.
 - [x] Lowered progression requirements are evaluated for a player on their next relevant action rather than immediately updating every stored player.
 - [x] Every successful mutation reports exactly what changed, and invalid requests make no partial changes.
+- [x] `/homeadmin` aliases `/baseadmin` with identical permission requirements and autocomplete.
+- [x] Permission-aware autocomplete offers subcommands, online and known offline players, progression paths, valid levels, progress counters, cooldown types, reset paths and confirmation, and numeric configuration keys.
+- [x] Invalid and extra arguments show friendly usage without exposing implementation-specific enum errors or modifying state.
 
 ## Related