Repository navigation
feat(widget): launch hosted job access with original identity - #17
Merged
Merged
Conversation
Merged
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.
Hosted job access
Adds the identity-enabled widget button and authenticated backend launch bridge for original-principal job access. The original identity session stays server-side. The browser receives a short-lived, origin-bound ticket and submits it by POST to the hosted Gateway flow; explicit consent remains required there. Popup cancellation and typed failures clear transient state without replacing the original identity.
Prepares version 0.4.1-beta.1 with explicit npm beta and GitHub prerelease routing. No tag or publication has occurred. Gateway/CCP counterparts are coordinated in nextlevelbuilder/dewee#1891 for #1479; merge/release must be coordinated with that integration.
Validation: 27 focused launcher/bridge tests, typecheck and build passed. Full widget suite: 239 passed, 26 PHP tests skipped because PHP was unavailable. Release classifier: 4 passed; beta build version verified. Independent source and release reviews found no remaining actionable findings. Real Chromium verified exact Origin and body-only ticket transport from a no-referrer host, safe retry and popup closure under enforced CSP, and successful navigation under report-only CSP. The popup sets strict-origin only in its own blank document and waits for navigation; token nodes are removed immediately. Combined authenticated Gateway end-to-end acceptance remains with the parent integration, including its SameSite continuation fix.
Surface parity: web component plus React/Vue/Astro share the launcher. PHP is anonymous-only and rejects identity mode, so this feature is not applicable. Gateway remains the authority; hosted transport is a child of the canonical dewee identity delegations workflow and creates no grant itself. Trace parity: launcher is transport only; Gateway records mint/consume and authorization activity. No new management MCP operation. Public docs and final CDN pin are coordinated with the parent integration after publication evidence.
CDN packaging now preserves the exact live stable alias and all discoverable served historical assets when adding beta. All inputs are fetched before replacing the deploy tree; the beta must byte-match the published npm artifact. Six focused packaging tests and live preparation passed, with independent review clear. CDN deployment remains coordinated with the parent; npm beta0.4.1-beta.1 is now available and latest remains0.3.0. The original beta tag stays171909f; packaging-only follow-updb9fc4f does not change package bytes.