Bundle @lua and @help like @chan

Instead of an explosion of similarly named commands, we'll bundle
these topical management commands together as switches.

Author: gtaylor

docs/content/en/docs/concepts/help-system.md

@@ -70,13 +70,13 @@ minimal plain-text format, not a general Markdown-to-ANSI renderer.
 
 ## Reindexing
 
-`@helpreload` (Wizard-only) rebuilds the entire index from scratch - this is
+`@help/reload` (Wizard-only) rebuilds the entire index from scratch - this is
 also what happens once at server startup. Both paths log errors and a
-summary to the server log; `@helpreload` also reports them to the invoking
+summary to the server log; `@help/reload` also reports them to the invoking
 player. Frontmatter is parsed with a vendored `tomlc17`.
 
 ## Configuration
 
 The `help_directory` mudconf directive (God-settable) points at the article
 root, relative to the server's working directory. Changing it does not
-reindex automatically - run `@helpreload` afterward.
+reindex automatically - run `@help/reload` afterward.

docs/content/en/docs/scripting/flows.md

@@ -115,7 +115,7 @@ Only string and number values round-trip; anything else assigned to
 `ctx.flow` (a table, a function, a boolean) is dropped with a logged warning.
 This is a deliberate trade-off: `ctx.flow` is backed by a small store of plain
 values on the descriptor, not a reference into the Lua state, specifically so
-a flow survives `@luareload` rebuilding the entire state out from under it. A
+a flow survives `@lua/reload` rebuilding the entire state out from under it. A
 step that no longer exists after a reload still fails the same way any other
 removed API would.
 

docs/content/en/docs/scripting/global-commands.md

@@ -7,11 +7,11 @@ weight: 20
 
 Global Lua logic modules live under `game/lua/global_logic`. Every
 `.lua` file in that tree is discovered recursively during startup and
-`@luareload`. Files are loaded in lexical relative-path order, so use
+`@lua/reload`. Files are loaded in lexical relative-path order, so use
 domain-oriented paths such as `player/help.lua`, `world/travel.lua`, and
 `wizard/maintenance.lua`. Use numeric prefixes only when deliberate
 cross-domain priority is necessary.
-Use [`@luacheck`](validating-and-reloading/) to validate every Lua module before reloading.
+Use [`@lua/check`](validating-and-reloading/) to validate every Lua module before reloading.
 
 Each global module returns a table containing `commands`:
 

docs/content/en/docs/scripting/overview.md

@@ -9,14 +9,14 @@ LuaJIT modules live under `game/lua` in three separate roots:
 
 ```text
 lua/
-  object_logic/      # @luaparent modules and their private helpers
+  object_logic/      # @lua/parent modules and their private helpers
   global_logic/      # globally matched command and scheduled modules
   packages/          # shared require-only helpers
 ```
 
 ## Object and global logic
 
-Attach a module to an object with the wizard-only `@luaparent
+Attach a module to an object with the wizard-only `@lua/parent
 <object>=<path>.lua`; the path is relative to `object_logic`, and omitting it
 clears the attachment. The closest attachment in the object's ordinary MUX
 parent chain is active. See [Object scripting](scripting-objects/) for the
@@ -49,7 +49,7 @@ five-field UTC cron expressions. Object schedules run once for every object
 that effectively inherits the Lua parent; global schedules run once per
 matching module entry. Scheduled jobs receive deterministic jitter and do not
 replay missed minutes. Inspect active schedules with the wizard-only
-`@luaschedule` command.
+`@lua/schedule` command.
 
 ## Imports
 
@@ -75,8 +75,8 @@ callback has an instruction cap.
 
 ## Validating and reloading
 
-Use the wizard-only `@luacheck` to verify every module before putting
-changes into service, then `@luareload` to atomically rebuild the Lua state
+Use the wizard-only `@lua/check` to verify every module before putting
+changes into service, then `@lua/reload` to atomically rebuild the Lua state
 from every attached module, every global logic module, and their
 dependencies. If a file or dependency fails to load, the current state
 remains active. See [Validating and reloading](validating-and-reloading/).
@@ -88,8 +88,8 @@ it to an object, then enter `hello` while that object is in the normal
 command-match scope:
 
 ```text
-@luaparent #123=example.lua
-@luareload
+@lua/parent #123=example.lua
+@lua/reload
 ```
 
 `game/lua/object_logic/counter.lua` demonstrates durable state. Its `count`
@@ -100,8 +100,8 @@ survives Lua reloads and server restarts.
 replacement:
 
 ```text
-@luaparent #456=events/enter_notice.lua
-@luareload
+@lua/parent #456=events/enter_notice.lua
+@lua/reload
 ```
 
 Its `aenter` function runs whenever the existing action-attribute path would

docs/content/en/docs/scripting/packages/mux.md

@@ -33,7 +33,7 @@ mux.attr_set(ctx.object, "LuaCount", "42")
 ```
 
 `object` must be a valid dbref. Lua cannot use this function to set
-`Luaparent`; use the wizard-only `@luaparent` command instead.
+`Luaparent`; use the wizard-only `@lua/parent` command instead.
 
 ## `mux.notify(object, message)`
 

docs/content/en/docs/scripting/scripting-objects.md

@@ -9,27 +9,27 @@ Object Lua modules live under `game/lua/object_logic`. Attach one to an
 object with the wizard-only command:
 
 ```text
-@luaparent <object>=<path>.lua
+@lua/parent <object>=<path>.lua
 ```
 
 The path is relative to `object_logic`; for example,
-`@luaparent #123=hello.lua` selects
+`@lua/parent #123=hello.lua` selects
 `game/lua/object_logic/hello.lua`. Paths must be relative `.lua` files and
 cannot escape into `global_logic` or `packages`. Omit the path to clear an
 attachment.
 
 The closest `Luaparent` in an object's normal MUX parent chain supplies the
 active module. Reload all attached modules and their dependencies atomically
-with `@luareload`; a failed reload leaves the current Lua state running.
-Use [`@luacheck`](validating-and-reloading/) to validate every Lua module
+with `@lua/reload`; a failed reload leaves the current Lua state running.
+Use [`@lua/check`](validating-and-reloading/) to validate every Lua module
 before reloading.
 
 If an attached file is deleted or otherwise cannot load, startup logs the
 object, configured path, and load error but continues. The attachment remains
 in place; command matching and action events for that object log the load error
 and are treated as handled, so legacy softcode does not run unexpectedly.
-Restore the file or update `Luaparent`, then use `@luareload` to activate the
-repair. `@luareload` itself remains atomic and rejects a missing attachment.
+Restore the file or update `Luaparent`, then use `@lua/reload` to activate the
+repair. `@lua/reload` itself remains atomic and rejects a missing attachment.
 
 ## Module contract
 
@@ -140,5 +140,5 @@ schedules = {
 ```
 
 A shared `Luaparent` runs each matching schedule once for every object that
-inherits it. Use the wizard-only `@luaschedule` command to inspect active
+inherits it. Use the wizard-only `@lua/schedule` command to inspect active
 schedules and their effective objects.

docs/content/en/docs/scripting/validating-and-reloading.md

@@ -12,10 +12,10 @@ You can validate and reload your game's Lua files from within the game without a
 To check your Lua scripts for validity, run the following from in-game with a Wizard character:
 
 ```text
-@luacheck
+@lua/check
 ```
 
-`@luacheck` recursively verifies every `.lua` file below
+`@lua/check` recursively verifies every `.lua` file below
 `game/lua/object_logic`, `game/lua/global_logic`, and
 `game/lua/packages`. It checks module syntax, top-level imports, and the
 module return contract, including cron schedules. Global logic modules must
@@ -31,12 +31,12 @@ move any `mux` calls into a handler or event function before checking it.
 
 ## Reloading Lua at runtime
 
-Use `@luareload` after a successful check to atomically put changed attached
+Use `@lua/reload` after a successful check to atomically put changed attached
 and global logic modules into service.
 
 ## Inspecting schedules
 
-Wizards can use `@luaschedule` to list scheduled object modules with their
+Wizards can use `@lua/schedule` to list scheduled object modules with their
 effective-object counts and scheduled global logic modules. Pass an object to
 show its effective Lua parent, a relative `object_logic` path to show its
 schedules and inheriting objects, or `global_logic/<path>.lua` to inspect one

game/help/wizard_commands/help.md

@@ -0,0 +1,18 @@
++++
+title = "@help"
+description = "Administer the help index"
+keywords = ["@help", "help administration"]
+article_tags = ["wizard_commands"]
+wizard_only = true
+
+show_index_for_article_tags = ["help_switches"]
+index_style = "list_with_description"
++++
+
+# @help
+
+`@help` groups the Wizard-only help administration commands under one command.
+Type `@help` by itself to see a short list of switches, or use one of the forms
+indexed below.
+
+The public `help [topic]` command continues to display help articles.

game/help/wizard_commands/help/reload.md

@@ -0,0 +1,20 @@
++++
+title = "@help/reload"
+description = "Rebuild the help index"
+keywords = ["@help/reload"]
+article_tags = ["help_switches"]
+weight = 10
+wizard_only = true
++++
+
+# @help/reload
+
+Rebuild the complete help index from the configured help directory:
+
+```text
+@help/reload
+```
+
+This performs the same indexing operation used during server startup. Errors,
+duplicate-keyword warnings, and the indexing summary are written to the server
+log and reported to the invoking Wizard.

game/help/wizard_commands/lua.md

@@ -0,0 +1,16 @@
++++
+title = "@lua"
+description = "Administer the Lua scripting runtime"
+keywords = ["@lua", "lua administration"]
+article_tags = ["wizard_commands"]
+wizard_only = true
+
+show_index_for_article_tags = ["lua_switches"]
+index_style = "list_with_description"
++++
+
+# @lua
+
+`@lua` groups the Wizard-only Lua administration commands under one command.
+Type `@lua` by itself to see a short list of switches, or use one of the forms
+indexed below.