story-kit: accept 179_story_add_configurable_chat_history_pruning
This commit is contained in:
@@ -1,20 +0,0 @@
|
||||
---
|
||||
name: "Fix chat textarea input lag"
|
||||
---
|
||||
|
||||
# Story 178: Fix chat textarea input lag
|
||||
|
||||
## User Story
|
||||
|
||||
As a user, I want typing in the chat input to feel responsive, so that I can compose messages without frustrating delays.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] Extract ChatInput as a separate component that owns its own input state, only calling parent on submit
|
||||
- [ ] Wrap calculateContextUsage in useMemo so it doesn't recompute on every keystroke
|
||||
- [ ] Extract MessageItem as a React.memo component so individual messages skip re-render on unrelated state changes
|
||||
- [ ] Typing in the textarea does not trigger re-render of the message list
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -1,23 +0,0 @@
|
||||
---
|
||||
name: "Add configurable chat history pruning"
|
||||
---
|
||||
|
||||
# Story 179: Add configurable chat history pruning
|
||||
|
||||
## User Story
|
||||
|
||||
As a user, I want chat history to be automatically pruned to a configurable limit, so that long sessions don't bloat localStorage and degrade performance.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] Default limit of 200 messages is applied when saving to localStorage
|
||||
- [ ] Messages are pruned from the front (oldest removed first) via messages.slice(-limit)
|
||||
- [ ] Limit is configurable via localStorage key storykit-chat-history-limit:{projectPath}
|
||||
- [ ] A limit of 0 means unlimited (no pruning)
|
||||
- [ ] useChatHistory returns maxMessages and setMaxMessages for future UI use
|
||||
- [ ] Existing useChatHistory tests continue to pass
|
||||
- [ ] New tests cover: pruning at limit, custom limit, unlimited mode
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
Reference in New Issue
Block a user