Conversation
Expose era-pinned historical L1 pages and coherent history metadata for application projections. Record preserved-prefix cuts atomically with recovery and expose generation compatibility through HTTP and the Rust SDK. Cover projection restore, historical replay, missed recoveries, and subscription races. Document manual recovery readiness and separate downstream adoption from API merge criteria.
GCdePaula
added this pull request to stack #40
September 18, 2026 11:48
stephenctw
approved these changes
Sep 19, 2026
This was referenced Sep 21, 2026
Member
Author
|
Superseded by #45. |
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.
Expose era-pinned historical L1 pages and coherent history metadata for application projections. Record preserved-prefix cuts atomically with recovery and expose generation compatibility through HTTP and the Rust SDK.
Cover projection restore, historical replay, missed recoveries, and subscription races. Document manual recovery readiness and separate downstream adoption from API merge criteria.