Repository navigation
Execute separate frozen H2 fault-injection follow-up - #51
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Closes #50.
The frozen protocol was committed first at
f0d39d568c66175ffba0f023e6eb36c5fbad39e0. Please use a merge commit so that the pre-execution ancestry remains inspectable. This is a separate study; the original PR #33 H2 fixture and failed 63/64 result remain unchanged.The new controls distinguish a primitive with an affected derived node, where injected evaluation failure must raise, from an unaffected primitive update, which must commit without derived evaluation. Results: 320/320 accepted transactions, 64/64 affected injections, 64/64 stale and malformed rejections, 64/64 unaffected updates, 8/8 distinct cycle rejections, and 16/16 connected boundary checks. A mutation check that suppresses the injected exception makes the new conjunction fail. The original H2 result is still reported as failed.
Validation: deterministic replay and byte-for-byte
--check, 2 focused tests, 161/0 original archive verification, PR #33 frozen replay unchanged,git diff --check. No model calls. This is an in-memory algorithm test, not crash durability, concurrency isolation, semantic accuracy or elapsed-time evidence.