Repository navigation
fix: show the newest turns first on the Memories page - #305
Conversation
Since skill learning, capture stores the host message ID in a memory's metadata.promptId instead of the prompt row ID. The Memories list paired a memory with its prompt only on that field, so no new memory found its prompt. Unpaired items sorted after every pair, and page 1 stopped at the last pair from early November. - Pair on user_prompts.linked_memory_id, with metadata.promptId as a fallback for older rows. - Sort pairs and single items together by time. - Cascade delete of a memory also deletes the prompt linked to it, so newer memories no longer leave their prompt behind.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
What was wrong
Since skill learning, capture stores the host message ID in a memory's
metadata.promptId, not the prompt row ID. The Memories list paired memory and prompt only on that field, so no memory since early November found its prompt. Unpaired items sorted after every pair, so page 1 stopped at 4 November.Fix
user_prompts.linked_memory_id; keepmetadata.promptIdas fallback for older rows.Evidence
tests/memory-timeline-orphan.test.ts; each failed before the fix.bun run ci:localpassed (exit 0).Summary by CodeRabbit