Repository navigation
Qualify settled Study recovery across stopped restore - #118
Merged
MrScripty merged 1 commit intoOct 21, 2026
Merged
Conversation
Preserve the original reservation and conservative charge alongside the recovered publication Ref through raw current-version transfer and cold SDK/CLI collection. Retain independently qualified evidence without compute replay.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
MrScripty
changed the base branch from
integration/interrupted-retention-restore-20261021
to
main
October 21, 2026 02:52
MrScripty
marked this pull request as ready for review
October 21, 2026 03:00
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.
This extends the existing real Study publication-recovery test through one clean stopped current-version transfer and cold SDK/CLI consumption. It preserves a populated settled reservation and exact conservative charge together with the original interrupted Run, publication fault and recovered result Ref. No production repair was needed.
Dependency PR117 merged normally as
f5d63e155c8a9df6676b9936ab536877c93191cbwith the exact reviewed tree. This PR is retargeted to main with head unchanged. Actual published commit bytes were hash-verified and imported locally;git merge-baseconfirms common ancestor0134a753, andgit merge-tree --write-treeover current main and this head yields exactly the qualified tree57f8344f55e557cbe8ee9fda9d5a742ec64cc10d. Current main and that common ancestor have identical trees. At retarget, GitHub still exposed its old test-merge reference; that is not claimed as regenerated. No source change or workflow rerun was launched. Before merge, required current-head hosted checks passed and fresh main/head/tree verification matched the reviewed candidate. Both source branches and unrelated work are preserved.The affected case passed author reproduction in 15.550 seconds unittest / 15.582514518 seconds wrapper and independent reproduction in 15.924 seconds unittest / 15.951664041 seconds wrapper, each with zero failures, errors or skips. All 43 raw tables, sequences and preactivation file hashes/POSIX modes survived; one Run, grant, consumption and settled reservation retained the exact original charged envelope. Current authenticated SDK and separate CLI collected the exact Ref bytes. One actual attempt launch and zero restore/consumer replay calls were observed. Exact owned schema/database cleanup was independently queried; PostgreSQL is stopped.
Acceptance report and sealed raw evidence.
Published head:
b132ee87bbf1ed66d2afc0597344d5f95ed345d2, parent0134a753a1ae54702af8dd0a559c6b0756e20ca1, tree57f8344f55e557cbe8ee9fda9d5a742ec64cc10d. The GitHub app assigns new commit metadata while preserving the exact reviewed local tree at36ba52a. Qualified test SHA256 remainse08eb764056b209aead37b6491cbced9f9adb9cea7813ec05ccc4ea3c147c8f3, reproduced at frozen55fe1c6. Independent source/reproduction review is clear; final report/tree-binding review SHA256 is60bd1b9f1e1ca659527c06f1f73d37bbb1746ffa0ba50d299694b233d79a755f. Published-head lifecycle CI completed successfully at exact headb132ee87bbf1ed66d2afc0597344d5f95ed345d2. Fresh check-runs and CodeRabbit status are successful, with no blocking submitted reviews. Fresh current-main/head checks and localgit merge-treeagain confirmed the exact qualified tree; GitHub reported a clean merge state before the normal merge.This changes only the existing Study recovery test, existing plan/ledger and scoped evidence relative to PR117. Its interruption test and evidence remain unchanged. No app/schema/README/workflow change, benchmark rerun, cache, runtime mutation, training or automatic migration is introduced. Older project owners migrate themselves once; current-version correctness and integrity remain required.
Limits: one clean Study transfer, with original Project roots available. PR117 separately owns controlled interruption/retry evidence; no new host-crash/power-loss/torn-payload/durability, root-removal, general performance or full-plan acceptance is claimed. PUB-1 still needs its original real failed Run/custody/profile/output inventory; SCI-1 still needs the real comparison pair, criterion authority and environment.
Merged normally as
133d53c0e2985a6559ba9cebd7d4a9f530051f06; actual tree57f8344f55e557cbe8ee9fda9d5a742ec64cc10dmatches the reviewed candidate, with both source branches preserved. All five automatic post-merge workflows completed successfully at that exact main commit: lifecycle, captured CPU, workspace UI, catalog, SDK. Post-merge lifecycle on PR117's mergef5d63e15also completed successfully. These results qualify the scoped slices and do not supply PUB-1, SCI-1, actual installed-runtime mutation or full product acceptance.