Conversation
Validate history claims before inclusive canonical pagination and capture snapshot history identity with the artifact lease. Preserve existing HTTP and WebSocket behavior for the coordinated consumer cutover. Cover recovery replacement, coherent reads, rebuilt history bases, deep backlogs, and lease metadata. Record the accepted snapshot-to-tip workflow and remaining API work.
Use one current application sequence with mandatory offsets and atomic recovery suffix replacement. Publish complete era baselines and derive immutable batch snapshot acceptance directly from L1 facts. Serve restorable HTTP archives and require versioned canonical WS claims. Update SDK, recovery exports, watchdog metadata, tests, and architecture documentation.
Exercise nonempty HTTP restore, concurrent catch-up, live replication, and recovery rebootstrap through the consumer API. Preserve Lua module paths in doctor and correct benchmark fee defaults uncovered during validation. Record pinned emulator 0.20 canonical-machine gates and an exact-revision ABBA latency comparison. Native engine conformance and deployment latency remain separate integration gates.
GCdePaula
force-pushed
the
feature/track3-history-read-foundation
branch
from
September 17, 2026 13:05
4fc010c to
7f3229f
Compare
GCdePaula
changed the base branch from
main
to
feature/application-c-bridge
September 17, 2026 13:05
Member
Author
|
Rebased on |
GCdePaula
added this pull request to stack #40
September 17, 2026 14:00
stephenctw
previously approved these changes
Sep 19, 2026
GCdePaula
force-pushed
the
feature/track3-history-read-foundation
branch
from
September 19, 2026 16:54
4a12a00 to
7f3229f
Compare
stephenctw
approved these changes
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.
Subscribers can now restore an application snapshot, replay its backlog, follow the optimistic tip, and rebootstrap after recovery invalidates their history.
Changes
/latest_snapshotand accepted recovery archives through/finalized_snapshot, with history identity and count tied to the artifact lease. Preserve the watchdog comparison routes.era_id,recovery_generation, andnext_inputon WebSocket subscriptions. Replay inclusively into live delivery; refuse incompatible history and positions ahead of the head. Update the Rust SDK and consumer documentation.Validation
Local validation at
7f3229f: 712 host tests, 62 watchdog tests, workspace checks, strict Clippy, formatting, and external C archive/downstream-consumer smoke checks passed. Five end-to-end scenarios passed against a freshly built emulator 0.20 image, covering cold replication, ordinary execution, stale recovery, and reconstruction from an exported checkpoint.The complete bootstrap/recovery journey through the C host, private DEX qualification, and representative deployment latency remain follow-up integration work.