@onekeyfe/hwk-keystone-adapter 1.2.3-alpha.4 → 1.2.3-alpha.8

package/dist/index.d.mts

@@ -304,6 +304,7 @@ interface ImportFromQrOptions {
  */
 declare class KeystoneAdapter implements IHardwareWallet {
     readonly vendor: "keystone";
+    readonly cancelCapability: "stops-waiting";
     private readonly urEngine;
     private readonly emitter;
     private readonly _operationRoutes;
@@ -480,6 +481,22 @@ declare class KeystoneAdapter implements IHardwareWallet {
      * and pass through unchanged.
      */
     private _ensureWalletKnown;
+    /**
+     * The operation the running device job belongs to, so a UI request raised
+     * mid-call can name it. A call pinned to an operation queues under its id
+     * (`keystoneQueueKey`); a call without one queues under the wallet id or the
+     * wallet connectId, and the live operation routed to that connection is still
+     * the owner. Only a cold start comes back undefined.
+     */
+    private _activeOperationId;
+    /** Routes are keyed by connectId; a job key may be the bare wallet id. */
+    private _operationRouteForIdentifier;
+    /**
+     * A QR prompt has no transport to interrupt, so an aborted job would sit here
+     * until the QR timeout. Releasing the registry slot on abort is what lets a
+     * cancel reach the wait at all.
+     */
+    private _awaitQrResponse;
     private _requestQrDisplayAndAwaitResponse;
     private _requestQrScanAndAwaitResponse;
     private _callUsbConnector;

package/dist/index.d.ts

@@ -304,6 +304,7 @@ interface ImportFromQrOptions {
  */
 declare class KeystoneAdapter implements IHardwareWallet {
     readonly vendor: "keystone";
+    readonly cancelCapability: "stops-waiting";
     private readonly urEngine;
     private readonly emitter;
     private readonly _operationRoutes;
@@ -480,6 +481,22 @@ declare class KeystoneAdapter implements IHardwareWallet {
      * and pass through unchanged.
      */
     private _ensureWalletKnown;
+    /**
+     * The operation the running device job belongs to, so a UI request raised
+     * mid-call can name it. A call pinned to an operation queues under its id
+     * (`keystoneQueueKey`); a call without one queues under the wallet id or the
+     * wallet connectId, and the live operation routed to that connection is still
+     * the owner. Only a cold start comes back undefined.
+     */
+    private _activeOperationId;
+    /** Routes are keyed by connectId; a job key may be the bare wallet id. */
+    private _operationRouteForIdentifier;
+    /**
+     * A QR prompt has no transport to interrupt, so an aborted job would sit here
+     * until the QR timeout. Releasing the registry slot on abort is what lets a
+     * cancel reach the wait at all.
+     */
+    private _awaitQrResponse;
     private _requestQrDisplayAndAwaitResponse;
     private _requestQrScanAndAwaitResponse;
     private _callUsbConnector;