What probably matters to youSection of the release
What
Command definitions gained a subcommandsBareOnly field. When it is set, a subcommand name only matches if nothing follows it, so typing /foo bar baz runs the parent /foo command with bar baz as its arguments instead of dispatching to the bar subcommand.
Details
Carried through both prompt-backed and file-backed command construction, and added to the allow-list used when commands are serialized.
Dispatch bails out on trailing text: if (e.subcommandsBareOnly && s !== "") return;.
The field did not exist in v2.1.226.
Evidence
if (e.subcommandsBareOnly && s !== "") return;, subcommandsBareOnly
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
