feat: add credential proxy workflows runtime stack#717
Merged
khaliqgant merged 7 commits intomainfrom Apr 22, 2026
Merged
Conversation
…-service-stack # Conflicts: # .trajectories/index.json # package-lock.json
jose@^6 ships only a webapi build that requires globalThis.crypto. Node 18 gates this behind --experimental-global-webcrypto, so the Install Test (Node 18) CI job fails with "crypto is not defined" when the credential-proxy tests mint or verify JWTs. Add a tiny crypto-polyfill module that assigns globalThis.crypto from node:crypto.webcrypto when missing. Import it before jose in both entry points (jwt.ts, router.ts) and the jwt test file so the side effect applies before jose resolves the Web Crypto API. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Provenance
This PR packages the result of running the sales deliverable workflow chain from against the repo in a clean worktree, including the sequential execution of the remaining phases via a master executor script.
Notes
Implementation was validated incrementally during workflow execution, including compile checks, targeted tests, integration tests, and review-driven fixes.