storkit: done 399_story_cli_port_flag_with_project_toml_persistence

2026-03-26 20:46:59 +00:00
parent f22a2666b8
commit 85e37e03a8
2 changed files with 31 additions and 35 deletions
@@ -1,35 +0,0 @@
---
-name: "WhatsApp and Slack missing start command handler"
---
-
-# Bug 401: WhatsApp and Slack missing start command handler
-
-## Description
-
-The start command has a fallback handler in chat/commands/mod.rs that returns None. Only Matrix has pre-dispatch handling for this command. On WhatsApp and Slack, the command falls through to the LLM path.
-
-## Implementation Note
-
-Follow the **rebuild pattern** established in story 402.
-
- `extract_start_command` and `handle_start` already exist in `server/src/chat/transport/matrix/start.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::start::extract_start_command` to detect the command, then `crate::chat::transport::matrix::start::handle_start` to execute it
- The fallback handler in `chat/commands/mod.rs` (`handle_start_fallback`) stays as-is — it exists only so `help` lists the command
-
-## How to Reproduce
-
-1. Configure bot with transport = "whatsapp" or "slack"\n2. Send "start <story_id>" to the bot\n3. Check server logs
-
-## Actual Result
-
-Command falls through to LLM instead of starting an agent.
-
-## Expected Result
-
-The bot starts an agent for the specified story and replies with confirmation.
-
-## Acceptance Criteria
-
- [ ] WhatsApp transport handles start command: starts agent and replies with confirmation
- [ ] Slack transport handles start command: starts agent and replies with confirmation