feat: add payment-aware client runtime - #170
Closed
parvahuja wants to merge 16 commits into
Closed
Conversation
parvahuja
force-pushed
the
parv/agent-payment-runtime
branch
2 times, most recently
from
July 7, 2026 18:22
0e4bad5 to
945682b
Compare
parvahuja
changed the base branch from
parv/fix-mcp-challenge-core-metadata
to
main
July 7, 2026 18:23
parvahuja
force-pushed
the
parv/agent-payment-runtime
branch
from
July 21, 2026 00:37
945682b to
25e5c19
Compare
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This was referenced Jul 21, 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.
Superseded by the reviewable payment-aware stack
This draft has been split into independently testable PRs using GitHub Stacks. Review and merge bottom-up:
PaymentRuntimeThe retained stack preserves the intended global payment-aware HTTP behavior while keeping each release boundary independently working.
Removed from this stack
The MCP dependency cap in #195 is compatibility-only: a clean optional install otherwise selects MCP 2.x and breaks pympp's existing MCP imports. It adds no MCP runtime behavior.
Verified end state
Closing this draft so review continues on the smaller PRs above.