From c9a2fa58eb6a6ddc30e5cadc3f24fc96ad3c52d5 Mon Sep 17 00:00:00 2001 From: Timmy Date: Thu, 26 Mar 2026 11:12:11 +0000 Subject: [PATCH] storkit: create 400_bug_whatsapp_and_slack_missing_reset_command_handler --- ...00_bug_whatsapp_and_slack_missing_reset_command_handler.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.storkit/work/1_backlog/400_bug_whatsapp_and_slack_missing_reset_command_handler.md b/.storkit/work/1_backlog/400_bug_whatsapp_and_slack_missing_reset_command_handler.md index 9ea29105..1fbc3a5f 100644 --- a/.storkit/work/1_backlog/400_bug_whatsapp_and_slack_missing_reset_command_handler.md +++ b/.storkit/work/1_backlog/400_bug_whatsapp_and_slack_missing_reset_command_handler.md @@ -12,10 +12,6 @@ The reset command has a fallback handler in chat/commands/mod.rs that returns No The fix must be in the shared command dispatch layer (chat/commands/mod.rs), NOT by adding transport-specific handlers. Study how commands like "rebuild" and "status" already work through the shared dispatch — the reset handler should return a concrete result from try_handle_command so all transports get it for free. We do not want separate mechanisms per transport per command. -## Implementation Note - -Follow the existing code patterns used by commands that already work on WhatsApp and Slack (e.g. "rebuild", "status"). Study how those commands are dispatched and handled, and implement the reset handler in the same way. - ## How to Reproduce 1. Configure bot with transport = "whatsapp" or "slack"\n2. Send "reset" to the bot\n3. Check server logs