@visa/cli 4.1.0-rc.274 → 4.1.0-rc.275

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.
Files changed (9) hide show
  1. package/README.md +7 -3
  2. package/dist/cli.js +438 -436
  3. package/dist/mcp-server/index.js +351 -349
  4. package/dist/merchant-ucp-mcp/index.js +3 -3
  5. package/native/bin/win32-arm64/visa-runtime-signer.exe +0 -0
  6. package/native/bin/win32-x64/visa-keychain-win.exe +0 -0
  7. package/native/bin/win32-x64/visa-runtime-signer.exe +0 -0
  8. package/package.json +1 -1
  9. package/server.json +2 -2
package/README.md CHANGED
@@ -403,6 +403,10 @@ handle is deleted only after possession-authenticated protected readback proves
403
403
  that exact prior generation retired; uncertain readback preserves it. Native
404
404
  custody uses the configured OS store or explicit headless KEK descriptor.
405
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.
406
+ `visa agent keychain revoke --agent <name-or-id> --purpose tap` opens an independent
407
+ owner review for the selected native runtime. The protected owner action stops current
408
+ and pending TAP authority, including an interrupted renewal. Local locks or unreadable
409
+ recovery journals do not prevent opening the owner review. The CLI preserves every known
410
+ handle until exact terminal readback, then deletes keys idempotently; `keychain resume`
411
+ retries locked cleanup. A public revoked selection tombstone prevents legacy TAP fallback.
412
+ After cleanup completes, `connect-device` explicitly enrolls a new runtime.