{{ message }}
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Issue for this PR
No linked issue.
Type of change
What does this PR do?
Adds timeline-backed session history. Forks reference a frozen prefix, committed undo selects a new timeline, and reads use indexed message ranges. Shared history survives deletion of its originating session. Active forks omit unfinished messages and materialize only the necessary settled suffix.
The transactional migration gives every existing session a root timeline and rebuilds the session/message tables while preserving their data and dependent rows. V1 imports create timelines directly; the temporary
opencode-next.dbimporter is removed.Clients keep flat session message lists. Undo handling uses message order rather than lexical IDs, and snapshot imports handle shared-ID collisions. Public API/event schemas and event versions are unchanged; settled-message selection happens inside the fork projection transaction.
How did you verify your code works?
v2because of existingSchema.Anyusage.Screenshots / recordings
Not applicable.
Checklist