feat: improve payment CLI discovery and browser request binding - #311
Merged
Conversation
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
1 participant
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.
Agents can discover and build all nine invoice modes through the CLI, then request an exact human-wallet transaction with explicit signer, network, expiry, and outcome binding. Add V2 schema/examples and
pay-requests build-v2, preserve the legacy alias, define metadata flag precedence, and infer browser signers from native send/swap messages.The browser contract distinguishes submitted, signed, cancelled, error, and unknown outcomes; unknown results prohibit automatic retry. Uploads share the request deadline and enforce the payload limit. A separate legacy request parser lets the companion frontend preserve installed clients. Callback results explicitly remain unverified and require chain confirmation.
Validation: 188 suites / 3,722 SDK tests; 3 real terminal roundtrip/error tests; ESM/CommonJS builds, import and cycle checks; dependency audit clean. Independent source review findings were fixed and regression-tested. No funded signing/broadcasts performed.
Prepares version 0.45.4. Publish only after review; the companion private frontend/indexer/docs PR must consume that published version before merge. Deploy the compatible frontend before recommending the new versioned browser flow. Follows #309 and #310; no new chain primitives, paused Agent Vault work, or subscription authorization redesign.