Repository navigation
Add bounded opt-in API clearance recovery and prepare SDK 0.19.0 - #64
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.
Add
createClearanceFetch()andreadClearanceChallenge()for the version-1 edge API challenge contract. A recognized missing/invalid/insufficient-grade challenge can run an application-provided clearance flow and retry GET/HEAD once. Concurrent reads share recovery; the deadline and AbortSignal stop work cleanly, including response-body cancellation after retry headers return. Mutations, ordinary 403s, revoked/policy-refused sessions, redirects and credential boundaries never start automatic recovery. No global patch or XHR interception.Prepare SDK 0.19.0 across all six packages, workspace lock and release notes. Export the helper in ESM/CJS and the standalone
window.WebDecoyClearancesurface. Document callback ownership, accessible UI obligations, CORS/cookies, cancellation and local observation semantics.Validation: 55 client tests passed, client build/lint passed (25 existing lint warnings). The actual generated IIFE and actual generated Worker passed local Chrome integration using ephemeral signed tokens: concurrent reads share one mint, expired and insufficient-grade reads recover, signed revoked tokens and POST mutations stay refused without minting/replay. App evidence and matching edge contract are coordinated through https://github.com/WebDecoy/app/issues/1572. This is local fixture evidence, not deployed/published-package/live issuer or interactive accessibility acceptance; that issue stays open.