diff --git a/.storkit/work/5_done/390_bug_whatsapp_missing_async_command_handlers_for_start_rebuild_reset_rmtree_assign.md b/.storkit/work/1_backlog/390_bug_whatsapp_missing_async_command_handlers_for_start_rebuild_reset_rmtree_assign.md
similarity index 100%
rename from .storkit/work/5_done/390_bug_whatsapp_missing_async_command_handlers_for_start_rebuild_reset_rmtree_assign.md
rename to .storkit/work/1_backlog/390_bug_whatsapp_missing_async_command_handlers_for_start_rebuild_reset_rmtree_assign.md
diff --git a/.storkit/work/1_backlog/393_story_pipeline_stage_notifications_for_whatsapp_and_slack_transports.md b/.storkit/work/1_backlog/393_story_pipeline_stage_notifications_for_whatsapp_and_slack_transports.md
deleted file mode 100644
index a78261a7..00000000
--- a/.storkit/work/1_backlog/393_story_pipeline_stage_notifications_for_whatsapp_and_slack_transports.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-name: "Pipeline stage notifications for WhatsApp and Slack transports"
----
-
-# Story 393: Pipeline stage notifications for WhatsApp and Slack transports
-
-## User Story
-
-As a WhatsApp or Slack user, I want to receive pipeline stage transition notifications (e.g. "story moved from Current to QA") just like Matrix users do, so I can track story progress from any transport.
-
-## Acceptance Criteria
-
-- [ ] WhatsApp transport spawns a notification listener at startup using the existing spawn_notification_listener infrastructure
-- [ ] Slack transport spawns a notification listener at startup using the same infrastructure
-- [ ] Notifications are sent to all active ambient senders/channels for the respective transport
-- [ ] Stage transition notifications (story moved between pipeline stages) are delivered
-- [ ] Error notifications (story failures) are delivered
-- [ ] Rate limit warnings are delivered with debouncing
-- [ ] Matrix notification behavior is completely unaffected
-
-## Out of Scope
-
-- TBD
diff --git a/.storkit/work/1_backlog/394_story_whatsapp_and_slack_permission_prompt_forwarding.md b/.storkit/work/1_backlog/394_story_whatsapp_and_slack_permission_prompt_forwarding.md
deleted file mode 100644
index 7fac8bd7..00000000
--- a/.storkit/work/1_backlog/394_story_whatsapp_and_slack_permission_prompt_forwarding.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-name: "WhatsApp and Slack permission prompt forwarding"
----
-
-# Story 394: WhatsApp and Slack permission prompt forwarding
-
-## User Story
-
-As a WhatsApp or Slack user, I want permission requests from Claude Code to be forwarded to my chat so I can approve or deny them, rather than having them silently fail.
-
-## Acceptance Criteria
-
-- [ ] Permission requests are sent as messages to the WhatsApp sender with tool name and input details
-- [ ] User can reply yes/y/approve or no/n/deny to approve or deny the permission
-- [ ] Permission requests time out and auto-deny (fail-closed) if not answered within the configured timeout
-- [ ] Slack receives the same permission forwarding treatment
-- [ ] Reuses the existing permission channel infrastructure (perm_rx, PermissionForward, PermissionDecision)
-- [ ] Matrix permission handling is completely unaffected
-- [ ] handle_llm_message uses a tokio::select! loop (like Matrix bot.rs) to listen for both LLM output and permission requests concurrently
-
-## Out of Scope
-
-- TBD
diff --git a/.storkit/work/1_backlog/395_refactor_fix_npm_deprecated_module_warnings.md b/.storkit/work/1_backlog/395_refactor_fix_npm_deprecated_module_warnings.md
deleted file mode 100644
index 717feb4b..00000000
--- a/.storkit/work/1_backlog/395_refactor_fix_npm_deprecated_module_warnings.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-name: "Fix npm deprecated module warnings"
----
-
-# Refactor 395: Fix npm deprecated module warnings
-
-## Current State
-
-- TBD
-
-## Desired State
-
-Address npm warnings about deprecated modules in the frontend dependencies. Update or replace deprecated packages to eliminate warnings during npm install.
-
-## Acceptance Criteria
-
-- [ ] npm install runs with zero deprecation warnings
-- [ ] All existing frontend tests (npm test) still pass
-- [ ] npm run build succeeds without errors
-- [ ] No functional regressions in the frontend
-
-## Out of Scope
-
-- TBD