Implement Note History System for Meeting Context Tracking #1799
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement Note History System for Meeting Context Tracking
Summary
This PR implements a note history system that tracks when users write notes relative to meeting transcripts. The system captures note changes with timestamps and categorizes them into three temporal buckets (before/during/after meeting) to provide better context to the AI when generating enhanced notes.
Key Changes:
note_historytable to database schema withsession_id,content,created_at_ms, andtranscript_idfieldsraw_mdchangesdifflibrary to compute diffs between consecutive note snapshotsReview & Testing Checklist for Human
note_historytable - The schema was updated but no migration was created. Existing databases will not have this table and the app will fail when trying to write history entries.High Priority:
lastTranscriptStartas the end boundary for "during meeting", but it should probably use the last transcript'sended_attimestamp. Check if notes written after the last transcript starts but before it ends are categorized correctly.Medium Priority:
raw_mdchange creates a history entry. Test if this creates too many entries during active typing. Consider adding debouncing or rate-limiting.Updates Since Last Revision
noteHistoryfield toTaskArgsMapTransformed['enhance']interface (commit 4484125)Notes