dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: accept 283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge

Browse Source
This commit is contained in:
Dave
2026-03-18 16:00:44 +00:00
parent fa8e0f39f6
commit 070d53068e
2 changed files with 0 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
.story_kit/work/1_backlog/293_story_register_all_bot_commands_in_the_command_registry.md
View File

@@ -1,22 +0,0 @@
---
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

0
.story_kit/work/5_done/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md → .story_kit/work/6_archived/283_bug_pipeline_does_not_check_manual_qa_flag_before_advancing_from_qa_to_merge.md
View File