@visa/cli 4.1.0-rc.327 → 4.1.0-rc.328
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 +8 -7
- package/dist/cli.js +301 -305
- package/dist/mcp-server/index.js +239 -245
- package/dist/merchant-ucp-mcp/index.js +6 -6
- package/native/bin/win32-arm64/visa-runtime-signer.exe +0 -0
- package/native/bin/win32-x64/visa-keychain-win.exe +0 -0
- package/native/bin/win32-x64/visa-runtime-signer.exe +0 -0
- package/package.json +1 -1
- package/server.json +2 -2
package/README.md
CHANGED
|
@@ -12,7 +12,7 @@ The protected product flow has three explicit parts:
|
|
|
12
12
|
1. **Enrollment** — call `agent_enroll` or have the owner run `visa agent enroll`
|
|
13
13
|
and approves the exact device and its limits in the browser. The private key
|
|
14
14
|
stays on the runtime device. Retired setup, pairing, handoff, and per-rail
|
|
15
|
-
grant names
|
|
15
|
+
grant names are not registered at all; they never resume or proxy work.
|
|
16
16
|
2. **Capabilities** — payment methods, spend grants, email and directory
|
|
17
17
|
bindings are configured separately, each with its own human-visible terms.
|
|
18
18
|
3. **Use** — when a separately provisioned capability exists, the wallet and
|
|
@@ -241,18 +241,19 @@ is required so the CLI never guesses which agent can spend.
|
|
|
241
241
|
## MCP tools (v4 surface)
|
|
242
242
|
|
|
243
243
|
Rows marked **Removed** are kept so old transcripts still resolve: the tool is
|
|
244
|
-
no longer in `tools/list`, and a direct call by name
|
|
245
|
-
|
|
246
|
-
`visa agent enroll-protected`.
|
|
244
|
+
no longer in `tools/list`, and a direct call by name is an unknown-tool error.
|
|
245
|
+
The one door for a new agent is `visa agent enroll` / `agent_enroll`.
|
|
247
246
|
|
|
248
247
|
A leftover direct-mode `turnkey.json` is not usable wallet authority.
|
|
249
248
|
`agent_capabilities` reports wallet status `legacy_direct_mode` and unavailable;
|
|
250
249
|
`get_status` directs even an already paired agent to `agent_enroll`. Have the
|
|
251
250
|
owner complete `visa agent enroll` before attempting payment.
|
|
252
251
|
|
|
253
|
-
|
|
254
|
-
|
|
255
|
-
|
|
252
|
+
A deploy that predates the tombstone removal can still answer HTTP 410 with
|
|
253
|
+
`code: route_retired`; the CLI classifies that as `legacy_door_removed`. Once
|
|
254
|
+
the removal is deployed the same paths answer a typed JSON 404
|
|
255
|
+
(`ROUTE_NOT_FOUND`). Either way, follow `agent_enroll` / `visa agent enroll`;
|
|
256
|
+
retrying the retired route does not restore it.
|
|
256
257
|
|
|
257
258
|
|
|
258
259
|
| Tool | Description |
|