You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Companion to ArcadeAI/monorepo#3731. Enterprise token exchange needs a private, execution-boundary contract for giving a trusted customer-managed Worker the exchanged target token and returning a fixed protected-API outcome without exposing credential material in public tool data.
What
Adds a one-attempt protected API adapter.
Adds the protected_api tool capability declaration.
Carries the private authorization outcome through HTTP and MCP Worker transports.
Keeps the outcome contract fixed to status, reason, and request-count evidence.
Versions the coordinated core, TDK, serve, and MCP server packages.
Verification
The coordinated branch test run completed with 3,745 tests passed and one skipped; changed-package formatting and type checks passed.
Review ask
@wdawson, please review this together with ArcadeAI/monorepo#3731, especially the credential boundary and the decision to keep the target token in the existing private authorization context.
Reopening as a draft now that the companion Gateway implementation has stabilized. Fresh validation on current main: 3,745 tests passed, 1 skipped; pre-commit passed; strict mypy passed for all four changed libraries (arcade-core, arcade-tdk, arcade-serve, and arcade-mcp-server). The companion monorepo work now keeps the Intermediate AS as the Gateway trust boundary and publishes per-Engine managed JWKS for rotation. The only local umbrella-check failure is an unrelated existing NumPy-stub/Python-target mismatch in untouched CLI/evals packages. @wdawson, please take another look when ready; this remains draft pending coordinated review.
This pull request has been automatically marked as stale because it has had no activity for 14 days. It will be closed in 14 days if no further activity occurs. If this is still relevant, please leave a comment or remove the stale label.
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
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.
Why
Companion to ArcadeAI/monorepo#3731. Enterprise token exchange needs a private, execution-boundary contract for giving a trusted customer-managed Worker the exchanged target token and returning a fixed protected-API outcome without exposing credential material in public tool data.
What
Verification
The coordinated branch test run completed with 3,745 tests passed and one skipped; changed-package formatting and type checks passed.
Review ask
@wdawson, please review this together with ArcadeAI/monorepo#3731, especially the credential boundary and the decision to keep the target token in the existing private authorization context.