From 825d36c204f19f6a853cf0df238bbc78b79c3033 Mon Sep 17 00:00:00 2001 From: Dave Date: Wed, 18 Mar 2026 10:30:47 +0000 Subject: [PATCH] fix: remove stale 266 from archived (came from 271 branch history) Co-Authored-By: Claude Opus 4.6 (1M context) --- ...rix_bot_structured_conversation_history.md | 21 ------------------- 1 file changed, 21 deletions(-) delete mode 100644 .story_kit/work/6_archived/266_story_matrix_bot_structured_conversation_history.md diff --git a/.story_kit/work/6_archived/266_story_matrix_bot_structured_conversation_history.md b/.story_kit/work/6_archived/266_story_matrix_bot_structured_conversation_history.md deleted file mode 100644 index 7865d38..0000000 --- a/.story_kit/work/6_archived/266_story_matrix_bot_structured_conversation_history.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -name: "Matrix bot structured conversation history" ---- - -# Story 266: Matrix bot structured conversation history - -## User Story - -As a user chatting with the Matrix bot, I want it to remember and own its prior responses naturally, so that conversations feel like talking to one continuous entity rather than a new instance each message. - -## Acceptance Criteria - -- [ ] Conversation history is passed as structured API messages (user/assistant turns) rather than a flattened text prefix -- [ ] Claude recognises its prior responses as its own, maintaining consistent personality across a conversation -- [ ] Per-room history survives server restarts (persisted to disk or database) -- [ ] Rolling window trimming still applies to keep context bounded -- [ ] Multi-user rooms still attribute messages to the correct sender - -## Out of Scope - -- TBD