@visa/cli 5.0.0-rc.378 → 5.0.0-rc.380

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -171,8 +171,8 @@ The server now exposes:
171
171
  - JSON Schema 2020-12 tool inputs and outputs, `structuredContent`, namespaced result metadata, cache hints, and receipt `resource_link` blocks.
172
172
  - Resources for agent status, capabilities, recent activity, and canonical `visa://receipt/{transactionId}` receipts.
173
173
  - Prompts for pairing/funding, spend inspection, safe purchasing, and receipt reconciliation, with completion support.
174
- - The `io.modelcontextprotocol/tasks` extension. Its presence does not make card payment available: `pay_merchant` refuses before creating approval work.
175
- - Multi-round-trip `input_required` URL elicitation with HMAC-protected, client-bound request state when the client supports URL elicitation but not Tasks.
174
+ - The `io.modelcontextprotocol/tasks` extension for retrieving, updating, and cancelling existing durable tasks. New `pay` calls use the same search, pricing, and wallet-payment routing regardless of Tasks support; they do not create card tasks.
175
+ - Recovery of existing approval continuations through multi-round-trip `input_required` URL elicitation with HMAC-protected, client-bound request state. New wallet `pay` calls do not start card approval work.
176
176
  - The `io.modelcontextprotocol/ui` Visa Control Center MCP App at `ui://visa/control-center`.
177
177
 
178
178
  Visa sidebands no longer pollute business JSON. Clients receive keys such as `io.visa/visa-receipt` and `io.visa/update-available` in result `_meta`.