@visa/cli 5.0.0-rc.401 → 5.0.0-rc.402

package/README.md

@@ -171,8 +171,7 @@ The server now exposes:
 - JSON Schema 2020-12 tool inputs and outputs, `structuredContent`, namespaced result metadata, cache hints, and receipt `resource_link` blocks.
 - Resources for agent status, capabilities, recent activity, and canonical `visa://receipt/{transactionId}` receipts.
 - Prompts for pairing/funding, spend inspection, safe purchasing, and receipt reconciliation, with completion support.
-- 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.
-- 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.
+- No `io.modelcontextprotocol/tasks` extension: it only ever carried the retired card checkout, so `tasks/*` requests answer JSON-RPC `-32601` and a replayed `requestState` continuation answers `-32602`. A wallet `pay` that needs the owner's approval is resumed by calling `pay` again with the same `economicIntentId`.
 - The `io.modelcontextprotocol/ui` Visa Control Center MCP App at `ui://visa/control-center`.
 
 Visa sidebands no longer pollute business JSON. Clients receive keys such as `io.visa/visa-receipt` and `io.visa/update-available` in result `_meta`.
@@ -306,8 +305,7 @@ The rail comes from the target. You never name it:
 discover { "query": "current weather by city" }                  # nothing is spent
 pay      { "target": "<listing-id>", "max": "0.05", ... }        # probe, policy check, sign, settle
 pay      { "target": "https://provider.example/paid", "max": "0.05" }
-history  {}                                                       # this agent's payments
-history  { "id": "<activity-id>" }                                # one receipt, with its proof
+history  {}                                                       # this agent's payments, with their proof
 ```
 
 Owners read spend across every rail in the Console's Activity feed.
@@ -369,7 +367,7 @@ a name that was ever real has to stay readable here.
 | `wallet_directory_pay` | **Removed.** Use `pay` |
 | `wallet_history` | **Removed.** Use `history` |
 | `wallet_fund` | **Removed.** The funding address is in `get_status` |
-| `checkout_merchants` | **Removed.** Use `history` with `merchants: true` |
+| `checkout_merchants` | **Removed.** Card purchases are read with `purchase_retrieve` |
 | `reset` | **Removed.** Use `visa disconnect --all` |
 
 Ground rules the tooling enforces — work with them, not around them:
@@ -528,7 +526,8 @@ Deterministic preconditions always resolve to a specific code:
 | The owner's spending approval for this agent has run out (`pay`, card purchases); nothing was charged, and the owner renews it at the `remedyUrl` limits page with the same limits | `grant_expired` | `platform` |
 | The owner pressed Decline on this exact "Ask me each time" payment (wallet or card); nothing was charged and it is never paid | `owner_declined` | `caller` |
 | Listing is not x402 (`pay`) | `invalid_argument` | `caller` |
-| Activity id not found or not attributable (`history {id}`) | `activity_entry_not_found` | `caller` |
+| Activity id not found or not attributable (`visa://receipt/{id}`) | `activity_entry_not_found` | `caller` |
+| A retired parameter was sent (`history` with `id` or `merchants`) | `invalid_argument` | `caller` |
 | The bundled signer is missing from this install (`agent_enroll`, `pay`) | `native_runtime_signer_not_installed` | `platform` |
 | The bundled signer is present but cannot be made executable | `native_runtime_signer_not_executable` | `platform` |
 | No signer is built for this OS/CPU | `native_runtime_platform_unsupported` | `platform` |