Repository navigation
ci(mdm): qualify merged activation repair - #31
Merged
Merged
Conversation
This was referenced Oct 28, 2026
grove
marked this pull request as ready for review
October 28, 2026 08:49
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.
Select the merged MDM activation repair in the joint-stack candidate workflow so new evidence is built from the actual merge commit rather than its pre-merge head. The original-pin and earlier compatibility evidence remain separate, and the pg-trickle source and archive checksum are unchanged.
MDM merge
ad2597f72ee657cb946c5bbd7ae5eb2bfd1ac1b3and previously tested heade8b1dff81f7375bc0c5a5d4eb1db311bce1c7043both have treedbf14d8c362551eb6eb53379b2e029e58cc8f924. The merged commit Git archive SHA-256 isd5ef46335ac1e3a1c8255548f388e3b6949dbe8bfb7377fa8c790788754544aa. Identical trees do not qualify the newly built artifacts: the workflow records the actual sources, archives, image and library hashes, commands, exits and observations and runs the existing focused repetitions and full audit.Local validation: workflow identity audit and whitespace checks passed. Exact-current-head CI is required. Logical restore remains unrepaired; outage, mixed-workload and paired performance qualification, signed operating limits and independent review remain open. No release or production activation is implied.
Refs #11 and #12.