From dd377de7db68b8d3c4967ff9f6a26f20e58adaa5 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Mar 2026 08:37:47 +0000 Subject: [PATCH] story-kit: done 293_story_register_all_bot_commands_in_the_command_registry --- ...ll_bot_commands_in_the_command_registry.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .story_kit/work/5_done/293_story_register_all_bot_commands_in_the_command_registry.md diff --git a/.story_kit/work/5_done/293_story_register_all_bot_commands_in_the_command_registry.md b/.story_kit/work/5_done/293_story_register_all_bot_commands_in_the_command_registry.md new file mode 100644 index 0000000..165ce90 --- /dev/null +++ b/.story_kit/work/5_done/293_story_register_all_bot_commands_in_the_command_registry.md @@ -0,0 +1,23 @@ +--- +name: "Register all bot commands in the command registry" +review_hold: true +--- + +# Story 293: Register all bot commands in the command registry + +## User Story + +As a user, I want all bot commands (help, status, ambient on/off) to be registered in the command registry in commands.rs, so that the help command lists everything the bot can do and there's one consistent mechanism for handling bot-level commands. + +## Acceptance Criteria + +- [ ] Status command is moved from bot.rs into the command registry in commands.rs +- [ ] Ambient on/off command is moved from bot.rs into the command registry in commands.rs +- [ ] Help command output lists all registered commands including status and ambient +- [ ] No bot-level commands are handled outside of the registry (single mechanism) +- [ ] Existing behavior of all commands is preserved +- [ ] Registry handler functions receive enough context to perform their work (e.g. project_root for status, ambient_rooms for ambient) + +## Out of Scope + +- TBD