From 96b1ce373b2b2013612a347b2ab7f2b8ce5852cc Mon Sep 17 00:00:00 2001 From: Timmy Date: Thu, 26 Mar 2026 11:12:16 +0000 Subject: [PATCH] storkit: create 403_bug_whatsapp_and_slack_missing_rmtree_command_handler --- ...3_bug_whatsapp_and_slack_missing_rmtree_command_handler.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md b/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md index d955af06..7e00099e 100644 --- a/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md +++ b/.storkit/work/1_backlog/403_bug_whatsapp_and_slack_missing_rmtree_command_handler.md @@ -12,10 +12,6 @@ The rmtree command has a fallback handler in chat/commands/mod.rs that returns N 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 rmtree 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 rmtree handler in the same way. - ## How to Reproduce 1. Configure bot with transport = "whatsapp" or "slack"\n2. Send "rmtree " to the bot\n3. Check server logs