Use mapped shortcode commands

After saving a mapping, run help or help COMMAND as the intended user. Confirm the command name, description, syntax, argument rules, access requirement, and owning add-on are accurate.

Run a valid example, an invalid argument, an unknown argument, a denied-user request, and the owner-inactive case. Output should remain bounded and terminal-safe.

Use stable, unique command names that do not shadow core or official add-on commands. If the owning shortcode is removed or renamed, disable the mapping until a reviewed replacement is available.

Clearing the terminal transcript does not delete data or side effects owned by the shortcode provider.