Repository navigation
test(mdm): inspect logical restore activation guard - #32
Merged
Merged
Conversation
This was referenced Oct 28, 2026
grove
marked this pull request as ready for review
October 28, 2026 10:08
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.
Problem
The logical restore regression stops at the known React state-loss assertion before inspecting the restored activation guard. Compare the complete retained MDM and adapter history, verify the copied binding remains ineligible, and run two restricted managed cycles before that assertion. The complete state comparison remains mandatory and still fails until logical recovery is repaired.
Validation
ad2597f72ee657cb946c5bbd7ae5eb2bfd1ac1b3, pg-tricklec7e257e551d6f6bacb84ecfe6f5daf7637c53673, and React source6eb4a2c09e5d0fff6846d9b41467de500d83a900; the test script was bind-mounted from this branch. It is an ARM64 diagnostic image, not the earlier x86 CI artifact. Image and library identities and complete logs are in the local archive described on v0.49.0: Complete managed bounded escalation #11 and v0.49.0: Qualify escalation safety, recovery and operating limits #12.git diff --checkpassed. The first compile attempt exited 1 because Python tried to write to a sandbox-protected cache; rerunning with a temporary cache exited 0.This is a test-only draft. It does not repair logical restore, prove activation and bounded resumption with restored work, or qualify a release. The logical mode is intentionally failing and is not added as a nonblocking CI check.