Repository navigation
fix(mdm): gate copied work until recovery activation - #29
Merged
Merged
Conversation
This was referenced Oct 27, 2026
grove
changed the title
8 tasks
grove
marked this pull request as ready for review
October 27, 2026 14:41
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.
A clean physical clone can deliver copied overdue escalation before operator activation. Hold managed work until MDM bindings are reconciled to the current postmaster, and recheck binding identity, roles, policy limits and producer capabilities before activation. Existing request and receipt history remains intact.
This depends on MDM PR #23 at
e8b1dff81f7375bc0c5a5d4eb1db311bce1c7043. The candidate requirespg_mdmpreload, helper reconfiguration after upgrade and explicit reconciliation after each PostgreSQL restart. All managed jobs in an affected database wait while enabled bindings require reconciliation.Candidate CI run 40542347021 passed on PR head
e5bce01e2f0982832d5a8d264a7e2da5e5e28f30and tested mergeeff60ff261e11bca49cedcee065aa3aca133afdc, with MDMe8b1dff81f7375bc0c5a5d4eb1db311bce1c7043and pg-tricklec7e257e551d6f6bacb84ecfe6f5daf7637c53673. Both repetitions of physical clone, direct delivery, claimed-work and autonomous recurrence passed, as did the full audit (51 checks, exit 0). Its explicit decision remainsQUALIFICATION_INCOMPLETE; this is not performance or release acceptance. The workflow artifact retains source archives, image and library hashes, commands, exits and observations.At the requester’s explicit direction, the four old-MDM historical test lanes are now nonblocking and labeled as such. Their original commands, source pins and artifacts remain in place; each test step records its actual exit and outcome, including skipped follow-on tests, and failures emit a warning. Build and evidence-collection failures remain blocking. These historical results do not qualify compatibility or release, and the activation guard is unchanged. The earlier source revisions lack the activation epoch; allowing delivery on them would reopen the confirmed clone defect. Raw candidate and local failures are retained, including an unresolved MDM incremental-qualification deadlock.
React PR #30 separately records unrepaired logical-restore loss. Full joint upgrade and restore, mixed workloads, paired performance, the signed operating envelope and independent review remain open. No release or production activation is claimed.
Refs #11 and #12.