Repository navigation
Converge reciprocal service-link decisions and enforce current authority - #125
Merged
Merged
Conversation
This was referenced Oct 6, 2026
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.
Simultaneous administrator cancellation could leave prepared peers indefinitely in doubt, and independent unlink requests could reject each other. Preserve each participant request in the protected operation journal, converge on the coordinator’s immutable decision, and acknowledge a peer unlink without replacing the local tombstone. Existing undecided companion records retain their original request and replay identity.
Managed connections now use current issuer/link settings and private-network permission at every request and socket fallback. Disabling linking stops cached business access; removing private-network permission stops old clients, and IPv6 instance-metadata addresses remain denied. Manual provider settings retain their established behavior.
Consent forms reset confirmation after grant edits and fence stale routes/responses. Credential actions retain the exact once-only reveal until its own saved-secret acknowledgment, hold their busy boundary, and discard late secret responses after disposal.
Validation: complete 14-project solution build passed with zero errors and the 21 existing warnings. The full solution suite passed 1,975 cases, zero failed, and the exact six pre-existing skips (1,981 total); all 45 added cases passed and every original beta.10 outcome remains. All 24 initially affected fixture cases now pass using production options/configuration and the Blazor query supplier. Local full-suite receipt:
rateldesk-convergence-full2-receipt.json. The final independently reviewed source has 29 changed/new paths and prospective treebc5e85ee66da991659ecd2f1ed7a94527385aa2d. Focused actual execution: 114 passed, zero failed/skipped, including all 24 affected existing fixture cases. Shared contracts, deployed migrations and workflows remain byte-identical. Hosted validation and published two-product acceptance remain required.Refs #124; companion to BostonTechnologies/netratel#164 and BostonTechnologies/netratel#141. Intended companion version:
0.1.1-beta.11; NetRatel’s requested version remains0.1.1-beta.1. Published companion beta.9/beta.10 assets/tags and stable image channels were freshly verified unchanged.