From 7939a19816604c6d3727db7e4e96a2c70510dc96 Mon Sep 17 00:00:00 2001 From: Timmy Date: Thu, 26 Mar 2026 11:09:46 +0000 Subject: [PATCH] storkit: create 401_bug_whatsapp_and_slack_missing_start_command_handler --- ...01_bug_whatsapp_and_slack_missing_start_command_handler.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md b/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md index 2c6c2d69..90fe620b 100644 --- a/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md +++ b/.storkit/work/1_backlog/401_bug_whatsapp_and_slack_missing_start_command_handler.md @@ -10,6 +10,10 @@ The start command has a fallback handler in chat/commands/mod.rs that returns No ## 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 start 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 start handler in the same way. ## How to Reproduce