engine: safely recover serial frontier staging attempts - #84
Closed
rbtr wants to merge 2 commits into
Closed
Conversation
Owner
Author
|
This PR used the wrong delivery plan. The existing PR stack will receive the required changes. |
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.
Summary
PRD alignment
This is the first implementation slice for
docs/frontier-prd.md: deterministic serial recovery, durable active-candidate metadata, and safe invalidation across a restart. It does not add speculative fan-out, a Postgres schema change, or deployment-specific behavior.Validation
make lint test buildgit diff --checkand public-copy scrub