Return WebFetch pairing links before the task deadline - #74
Merged
Merged
Conversation
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.
When a portal console is watching a device, first-time pairing waits up to 60 seconds. A WebFetch task can time out before that decision, returning EOF/unknown instead of the owner pairing link. This occurred during the production canary rollout of #73.
Delegated sessions now publish the same pairing request without waiting for a decision. They return the owner link immediately, retain the request for later approval, and consume the explicit owner decision on the next connection. Existing CLI pairing behavior and device operation policy are unchanged.
Validation: real TLS regression tests for HTTP and WebSocket devices with an active portal subscriber; owner approval is required and the subsequent command remains subject to device policy. Focused race tests and complete agent/console suites pass. The production canary now returns the pairing link instead of timing out.