diff --git a/.story_kit/work/1_backlog/321_story_whatsapp_htop_adaptation_for_no_edit_platforms.md b/.story_kit/work/1_backlog/321_story_whatsapp_htop_adaptation_for_no_edit_platforms.md
deleted file mode 100644
index 961b5dd..0000000
--- a/.story_kit/work/1_backlog/321_story_whatsapp_htop_adaptation_for_no_edit_platforms.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-name: "WhatsApp htop adaptation for no-edit platforms"
----
-
-# Story 321: WhatsApp htop adaptation for no-edit platforms
-
-## User Story
-
-As a project owner using WhatsApp, I want the htop command to work even though WhatsApp doesn't support message editing, so that I can monitor system load from any chat platform.
-
-## Acceptance Criteria
-
-- [ ] htop on WhatsApp sends a new message each update instead of editing
-- [ ] Rate-limited to avoid spamming (e.g. one message per 15 seconds instead of every 5)
-- [ ] Each new message replaces the previous one visually (includes a 'last updated' timestamp)
-- [ ] htop stop still works to cancel the loop
-- [ ] ChatTransport trait has a supports_editing() method so htop can adapt its behavior per platform
-
-## Out of Scope
-
-- TBD
diff --git a/.story_kit/work/1_backlog/322_story_whatsapp_24_hour_messaging_window_and_template_support.md b/.story_kit/work/1_backlog/322_story_whatsapp_24_hour_messaging_window_and_template_support.md
deleted file mode 100644
index 9c3f4c3..0000000
--- a/.story_kit/work/1_backlog/322_story_whatsapp_24_hour_messaging_window_and_template_support.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-name: "WhatsApp 24-hour messaging window and template support"
----
-
-# Story 322: WhatsApp 24-hour messaging window and template support
-
-## User Story
-
-As a project owner, I want the bot to handle WhatsApp's 24-hour messaging window correctly, so that proactive notifications (build failures, merge completions) work within Meta's rules.
-
-## Acceptance Criteria
-
-- [ ] Bot tracks the 24-hour window per user — free-form replies only within 24h of last user message
-- [ ] After 24h, bot uses approved message templates for notifications
-- [ ] At least one message template registered with Meta for pipeline notifications (e.g. 'Story {name} has moved to {stage}')
-- [ ] Bot gracefully handles 'outside messaging window' errors from the API without crashing
-- [ ] Template registration documented in setup guide
-
-## Out of Scope
-
-- TBD
diff --git a/.story_kit/work/1_backlog/323_story_whatsapp_llm_passthrough_for_conversational_queries.md b/.story_kit/work/1_backlog/323_story_whatsapp_llm_passthrough_for_conversational_queries.md
deleted file mode 100644
index 5f2546e..0000000
--- a/.story_kit/work/1_backlog/323_story_whatsapp_llm_passthrough_for_conversational_queries.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-name: "WhatsApp LLM passthrough for conversational queries"
----
-
-# Story 323: WhatsApp LLM passthrough for conversational queries
-
-## User Story
-
-As a project owner using WhatsApp, I want messages that aren't bot commands to be forwarded to Claude for conversational responses, so that I can ask questions about the project naturally from WhatsApp just like I do from Matrix.
-
-## Acceptance Criteria
-
-- [ ] Messages that don't match any bot command are forwarded to Claude via the existing LLM pipeline
-- [ ] Responses are sent back as WhatsApp messages
-- [ ] Conversation history is maintained per user (similar to Matrix history_size)
-- [ ] System prompt includes the same project context as Matrix (bot name, pipeline awareness, MCP tools)
-- [ ] Long responses are chunked to fit WhatsApp's message size limits
-
-## Out of Scope
-
-- TBD
diff --git a/.story_kit/work/5_done/314_story_show_token_cost_per_story_in_bot_status_command_output.md b/.story_kit/work/6_archived/314_story_show_token_cost_per_story_in_bot_status_command_output.md
similarity index 100%
rename from .story_kit/work/5_done/314_story_show_token_cost_per_story_in_bot_status_command_output.md
rename to .story_kit/work/6_archived/314_story_show_token_cost_per_story_in_bot_status_command_output.md