@visa/cli 4.1.0-rc.273 → 4.1.0-rc.274
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 +26 -0
- package/dist/cli.js +586 -584
- package/dist/mcp-server/index.js +489 -487
- package/dist/merchant-ucp-mcp/index.js +3 -3
- 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
|
@@ -380,3 +380,29 @@ Restart the client or reconnect the MCP server (`/mcp` → `visa-cli` → reconn
|
|
|
380
380
|
## Monorepo context
|
|
381
381
|
|
|
382
382
|
Request routing (MCP vs MPP vs web): [docs/agents/ARCHITECTURE.md](../../docs/agents/ARCHITECTURE.md). Branches and deploy: [docs/agents/PIPELINE.md](../../docs/agents/PIPELINE.md). Contributor workflow: [AGENTS.md](../../AGENTS.md), doc index: [docs/agents/README.md](../../docs/agents/README.md).
|
|
383
|
+
|
|
384
|
+
### Native device TAP lifecycle
|
|
385
|
+
|
|
386
|
+
`visa agent keychain connect-device --agent <name-or-id>` selects this device for
|
|
387
|
+
identity-only TAP signing after the existing browser owner ceremony verifies its
|
|
388
|
+
certificate, delegation, Gate authorization and native key binding. The selected
|
|
389
|
+
native profile serves actual TAP consumers; unavailable custody or invalid selected
|
|
390
|
+
metadata fails closed. Wallet/card keys and payment authority remain separate.
|
|
391
|
+
|
|
392
|
+
`visa agent keychain renew --agent <name-or-id> --purpose tap` creates an independently
|
|
393
|
+
addressed successor for the same runtime and opens the owner review page. Both keys
|
|
394
|
+
survive interruption. `visa agent keychain resume --agent <name-or-id>` resumes the
|
|
395
|
+
exact pending operation, including a locked-keychain cleanup retry. `--no-open`
|
|
396
|
+
prints the owner URL. Expired locators require another owner ceremony using the
|
|
397
|
+
preserved successor key. `keychain status` reports the selected profile and local
|
|
398
|
+
renewal phase; it is a local projection, not a live authority check.
|
|
399
|
+
|
|
400
|
+
Only public certificates/proposals and opaque native handles enter the durable
|
|
401
|
+
renewal journal. Selection changes after verified owner activation. The previous
|
|
402
|
+
handle is deleted only after possession-authenticated protected readback proves
|
|
403
|
+
that exact prior generation retired; uncertain readback preserves it. Native
|
|
404
|
+
custody uses the configured OS store or explicit headless KEK descriptor.
|
|
405
|
+
|
|
406
|
+
Native owner revocation is a separate follow-up; the legacy `keychain revoke`
|
|
407
|
+
command refuses a selected native TAP profile rather than mutating a different
|
|
408
|
+
legacy slot. Renewal retirement and cleanup above are available now.
|