fix(lmux): close M3 and M4 acceptance - #609
Merged
Merged
Conversation
Retry lifecycle-fence contention independently from unrelated transient registry cleanup state. Database cleanup debt remains authoritative after the lifecycle fence has been acquired.\n\nRefs #607
Give an in-flight descriptor close one event-loop turn to settle before rejecting managed Mux admission. Persistent cleanup debt and uncertain fence release remain fail-closed.\n\nRefs #607
Record the source-bound formal campaigns, ARD-004 claim limits, narrow startup contention fix, final gates, and three-perspective review.\n\nRefs #607
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
1 participant
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.
The formal history-restore campaign consistently failed during startup when an unrelated registry database descriptor close briefly overlapped startup fence acquisition. The managed fence now gives that exact transient close one bounded settlement opportunity while preserving the original owner, deadline, unknown-release handling, and fail-closed behavior for persistent cleanup debt.
This also removes a false read-only snapshot race by waiting for the already-authorized lifecycle diagnostic writer, and records the completed M3/M4 acceptance. Fresh uninterrupted first-use and history-restore A/A campaigns both completed 44/44 valid samples and passed; retained managed-mux and history-warm reports were source-bound and reevaluated under accepted ARD-004 without rewriting data or claiming a new performance measurement. The final architecture, lifecycle/security, and Product/acceptance review found no unresolved P0/P1/P2 issue.
Validation:
The performance conclusion remains limited to the accepted ARD-004 contract: no regression above 30% was detected; smaller regressions are not detectable by this gate, and this PR makes no speedup claim.
Closes #607