Repository navigation
fix(engine): align remote reconnect and session metadata - #1923
Merged
Merged
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
1 participant
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.
Let the app resume exactly at the current snapshot watermark, including sequence zero, by returning an optional opaque
snapshot_idand accepting it in the resume cursor. A replaced snapshot at the same sequence changes that ID and still forces resync; older clients retain the safe snapshot fallback.Create new message timestamps as RFC3339 and keep undated legacy history unknown. Omit time-only legacy timestamps remotely, and return an empty title for sessions without a prompt or stored title. Update schemas/goldens, the app UI guide and deliberate v1 limits for message IDs, steering, questions, approvals, tool commands, receipts and Unix socket directories.
Validation: workspace check/tests, formatting, protocol contract regeneration, hub regressions, authenticated gateway reconnect/history regression and read-only review. Fix existing context tests to compare role/content rather than two independently created timestamps.
Related to #1917; the final session-list timestamp limit is completed in a documentation follow-up.