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

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
@@ -410,3 +410,23 @@ recovery journals do not prevent opening the owner review. The CLI preserves eve
410
410
  handle until exact terminal readback, then deletes keys idempotently; `keychain resume`
411
411
  retries locked cleanup. A public revoked selection tombstone prevents legacy TAP fallback.
412
412
  After cleanup completes, `connect-device` explicitly enrolls a new runtime.
413
+
414
+ ### Native Subway owner certificates
415
+
416
+ New `agent keychain renew --purpose subway --advanced` requests keep the Subway
417
+ child key in native custody. Complete the existing offline browser owner certificate
418
+ review and import its response with `--response <file>`. Repeating the response
419
+ command resumes interrupted certification, prior-runtime revocation, or locked-key
420
+ cleanup. An expired unsigned request keeps its native key and produces a fresh
421
+ owner request. `keychain status` reports pending work and the selected native profile.
422
+
423
+ Register the Subway name again after renewal so its peer key matches the selected
424
+ child. WebSocket messages and direct libp2p Noise authentication use structured
425
+ native signing operations. Invalid, expired, revoked, or unavailable native selection
426
+ fails closed. Existing unpaired mesh usage retains its current behavior.
427
+
428
+ The public renewal journal preserves both generations until the runtime service
429
+ confirms revocation of the exact previous child. Only then does cleanup remove its
430
+ native handle or isolated legacy Subway key file. `keychain revoke --purpose subway`
431
+ revokes the selected child before deleting its key; repeat it to retry locked cleanup.
432
+ Wallet and card custody are separate.