Skip to content

Qualify settled Study recovery across stopped restore - #118

Merged
MrScripty merged 1 commit into
mainfrom
integration/study-recovered-result-restore-20261021
Oct 21, 2026
Merged

MrScripty merged 1 commit into
mainfrom
integration/study-recovered-result-restore-20261021

Conversation

@MrScripty

@MrScripty MrScripty commented Oct 21, 2026 •

Copy link
Copy Markdown
Owner

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 f5d63e155c8a9df6676b9936ab536877c93191cb with 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-base confirms common ancestor 0134a753, and git merge-tree --write-tree over current main and this head yields exactly the qualified tree 57f8344f55e557cbe8ee9fda9d5a742ec64cc10d. 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, parent 0134a753a1ae54702af8dd0a559c6b0756e20ca1, tree 57f8344f55e557cbe8ee9fda9d5a742ec64cc10d. The GitHub app assigns new commit metadata while preserving the exact reviewed local tree at 36ba52a. Qualified test SHA256 remains e08eb764056b209aead37b6491cbced9f9adb9cea7813ec05ccc4ea3c147c8f3, reproduced at frozen 55fe1c6. Independent source/reproduction review is clear; final report/tree-binding review SHA256 is 60bd1b9f1e1ca659527c06f1f73d37bbb1746ffa0ba50d299694b233d79a755f. Published-head lifecycle CI completed successfully at exact head b132ee87bbf1ed66d2afc0597344d5f95ed345d2. Fresh check-runs and CodeRabbit status are successful, with no blocking submitted reviews. Fresh current-main/head checks and local git merge-tree again 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 tree 57f8344f55e557cbe8ee9fda9d5a742ec64cc10d matches 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 merge f5d63e15 also completed successfully. These results qualify the scoped slices and do not supply PUB-1, SCI-1, actual installed-runtime mutation or full product acceptance.

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.
@coderabbitai

coderabbitai Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 35a5a7c9-23b6-48fe-9fbf-fe30be99ed49
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@MrScripty
MrScripty changed the base branch from integration/interrupted-retention-restore-20261021 to main October 21, 2026 02:52
@MrScripty
MrScripty marked this pull request as ready for review October 21, 2026 03:00
@MrScripty
MrScripty merged commit 133d53c into main Oct 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant