Repository navigation
Complete 0.5 example consumers and signed provider qualification - #34
Open
smiggleworth wants to merge 9 commits into
Open
smiggleworth wants to merge 9 commits into
smiggleworth wants to merge 9 commits into
Conversation
Reuse the reviewed private application candidate against the frozen 18-package graph, migrate ordinary locks and repair installed Vite/TypeScript contracts. Add explicit provider CI gates and document the unresolved browser redirect transport boundary. Local source preparation for #29, #30 and #32; provider browser acceptance remains blocked.
| `<form method="${provider === "apple" ? "post" : "get"}" action="${html(transaction.redirect)}">${[...result, ...(provider === "apple" ? [["user", JSON.stringify({ name: { firstName: "Unsigned", lastName: "Display Hint" } })]] : [])].map(([key, value]) => `<input type="hidden" name="${html(key!)}" value="${html(value!)}">`).join("")}<button id="continue" type="submit">Complete ${provider} sign in</button></form>`, | ||
| ); | ||
| } | ||
| response.writeHead(303, { location: `${transaction.redirect}?${result}` }); |
This was referenced Oct 13, 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.
Complete the 0.5.0 example consumers and server-owned provider sessions. In particular, an expired session's private-data 401 now retires the visible private page and cached data, then recovers through login with
next; the previous example retained private state until document reload.Validation on the installed candidate graph:
npm run checkpasses 166 workspace tests, 10 journey contracts, seven archive checks, lint, strict types, OpenAPI and installed-provider checks. All seven applications build. Provider TypeScript 6/7 and all 54 Chromium/Firefox/WebKit cases pass. The live-page expiry regression first failed with a real 401 and a retained private page, then passed after the fix.The earlier independent-stage and downstream consumer receipts are documented in source acceptance. Final integrated-graph replay remains pending, including the newly merged Core #783. These follow-up checks reused installed candidates and do not claim a new clean-install or independent-stage receipt. At head
06cbac9461490f3b0dab55d42943818c94734b6e, all three hosted CI installs fail with E404 for unpublished@askrjs/vite@0.5.0; tests are skipped. CodeQL passes. Hosted integration remains blocked; no branch protection or workflow changes are included in this follow-up.References #29, #30, #32 and askrjs/askr-auth#64. Live-provider qualification stays deferred in askrjs/askr-auth#71; every provider remains documented as pending live qualification. This PR targets
developand does not tag or publish.