From fa8e0f39f63f6040a87193383d71b2468c01aded Mon Sep 17 00:00:00 2001 From: Dave Date: Wed, 18 Mar 2026 15:57:14 +0000 Subject: [PATCH] story-kit: create 293_story_register_all_bot_commands_in_the_command_registry --- ...ll_bot_commands_in_the_command_registry.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .story_kit/work/1_backlog/293_story_register_all_bot_commands_in_the_command_registry.md diff --git a/.story_kit/work/1_backlog/293_story_register_all_bot_commands_in_the_command_registry.md b/.story_kit/work/1_backlog/293_story_register_all_bot_commands_in_the_command_registry.md new file mode 100644 index 0000000..63b2eff --- /dev/null +++ b/.story_kit/work/1_backlog/293_story_register_all_bot_commands_in_the_command_registry.md @@ -0,0 +1,22 @@ +--- +name: "Register all bot commands in the command registry" +--- + +# 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