From a52d1e098ff07aa9fbfa87eb9e21fd18f9175a41 Mon Sep 17 00:00:00 2001 From: dave Date: Thu, 26 Mar 2026 20:05:33 +0000 Subject: [PATCH] storkit: create 403_bug_whatsapp_and_slack_missing_rmtree_command_handler --- ...ug_whatsapp_and_slack_missing_rmtree_command_handler.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) 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 7e00099e..bf606e43 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 @@ -10,7 +10,12 @@ The rmtree command has a fallback handler in chat/commands/mod.rs that returns N ## Implementation Note -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. +Follow the **rebuild pattern** established in story 402. + +- `extract_rmtree_command` and `handle_rmtree` already exist in `server/src/chat/transport/matrix/rmtree.rs` +- Add an async intercept in `server/src/chat/transport/whatsapp.rs` (see rebuild intercept ~line 1107) and `server/src/chat/transport/slack.rs` (see rebuild intercept ~line 845) +- Call `crate::chat::transport::matrix::rmtree::extract_rmtree_command` to detect the command, then `crate::chat::transport::matrix::rmtree::handle_rmtree` to execute it +- The fallback handler in `chat/commands/mod.rs` (`handle_rmtree_fallback`) stays as-is — it exists only so `help` lists the command ## How to Reproduce