Repository navigation
Repair reciprocal discovery, consent recovery and frozen-contract boundaries - #123
Merged
Merged
Conversation
added 4 commits
October 5, 2026 06:08
Expose exact Web discovery, safely resume original browser approval after sign-in, persist outbound operation journals with the existing attempt concurrency check, and show narrowed consent grants. Add provider, Web and browser regressions.
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.
Entering RatelDesk's published Web URL for reciprocal linking returns 404 because its Web API guard blocks the advertised discovery route. Signed-out consent loses the approval page, and concurrent recovery can create competing journals for the same operation. The frozen-contract review also found retries rejected solely for scope order, malformed numeric/null payloads accepted or failing late, token-cache windows extended by HTTP transit, and expired bootstrap escrow retained while linking is disabled.
This change repairs those paths for the next compatible RatelDesk prerelease:
Advance the sole RatelDesk version source to
0.1.1-beta.10. NetRatel's requested release remains0.1.1-beta.1. Frozen contracts, deployed migration history, existing rate limits, deadlines and shipped deployment defaults remain unchanged.Validation: exact SDK 10.0.400 Release build passed (0 errors; 21 existing warnings). The full current solution passed 1,930 tests with zero failures and the same six pre-existing skips (1,936 total; 17m44s). Focused corrected rotation rows passed 4/4 with zero skips. Independent review covers all 43 changed/new files and seals clean commit
335152cf1493105a1582820ba4601ef71add244d, tree92bf6aee9ba3fc057f4b6c362f10f8c2d809a885. The full compiled C# source tree is byte-identical after the five TS driver corrections. The corrected real IMAP/SMTP mailbox lifecycle passed locally (1/1, zero skips; 3.4m); the original failure was reproduced before correction. All seventeen renewed exact-head hosted checks are required before merge; compatible-build publication and NetRatel pairing remain subsequent gates.Refs #121. Supports BostonTechnologies/netratel#164 and BostonTechnologies/netratel#141.