Built-in command setup was split into separate build and register steps.
What's wrong with this entry?
The bundled-command builder no longer constructs and registers a command object inline; registration moved to a dedicated function.
- The old helper now just returns
{ skillRoot, getPromptForCommand }. - A reset helper clears the bundled command lists and the kill-switch-survivor set tracked by
survivesBundledKillSwitch. - A batched file-writing helper with
tolerateExistingand verify-content semantics was added alongside.
survivesBundledKillSwitch
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command