Repository navigation
Tighten full-batch delivery and abrupt-recovery verification - #8
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
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.
Full-batch verification exposed two gaps in the delivery auditor: changed overview PNGs could still pass, and hidden native commit evidence was not checked. Reject image changes by default and bind every native commit artifact to already verified package/source hashes. Identical long-CSV rows avoid redundant recursive normalization; differing rows retain the same strict checks.
The benchmark freezes code/input identity at startup and records CPU, stages, and the final durable checkpoint even on real os._exit(99). Scientific runtime source is unchanged from main.
Validation: 45 focused tests, Ruff, diff checks, and all eight PR CI jobs passed. The complete real 121-frame first run took 10713.05 s. A real external process exit 99 interrupted full-result validation after 1026.41 s; the complete post-crash reuse took 1130.32 s, restored all 121 frames and refitted zero. Full reuse and post-crash recovery share this one complete observation. All 2156 published file versions and the commit marker were retained; the final independent full SHA/CRC/content audit is running in parallel with closeout. Cold-start mid-computation recovery without a published native bundle remains unverified. Private data and local evidence are excluded from Git.