@settlemint/dalp-cli 3.1.33-main.43546076392 → 3.1.33-main.43556327932

package/dist/{openapi-surface-x2t52hz7.json → openapi-surface-7r6m91cj.json}

@@ -17889,8 +17889,8 @@
       "method": "POST",
       "url": "/api/v2/users/me/custody-account-requests/{requestId}/approval",
       "summary": "Approve a custody account lifecycle request",
-      "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
-      "help": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+      "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: approving a signing-key change always needs the caller's wallet verification, also when an external signer submits its artifact. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "help": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: approving a signing-key change always needs the caller's wallet verification, also when an external signer submits its artifact. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
       "tags": [
         "Users"
       ],
@@ -17934,7 +17934,7 @@
       ],
       "requestBodyDescription": null,
       "hasRequestBody": true,
-      "bodyIsComplex": false,
+      "bodyIsComplex": true,
       "bodyFields": [
         {
           "name": "existingSignerCustodyAccountId",
@@ -17972,7 +17972,7 @@
       ],
       "examples": [
         {
-          "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+          "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: approving a signing-key change always needs the caller's wallet verification, also when an external signer submits its artifact. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
           "path": {
             "requestId": "<requestId>"
           }
@@ -17984,8 +17984,8 @@
       "method": "POST",
       "url": "/api/v2/users/me/custody-accounts/managed",
       "summary": "Create a managed custody account",
-      "description": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
-      "help": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "description": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified, with one exception: a caller who has no wallet verification method yet (no transaction PIN, transaction code, recovery codes or authenticator) may create the participant's first signing key without sending one, when the participant holds no signing key that is not archived (a revoked key counts) and no key is being created or changed for it, on any provider, organization or network. The platform decides this itself, under a lock on the participant, so of two concurrent first-key creates only one goes through without verification. Every other create needs the wallet verification, as does a create with `purpose` `deposit`, a create that carries `walletVerification`, and any create once the caller has a verification method; without it the request is refused with `WALLET_VERIFICATION_REQUIRED`, or with `USER_MISSING_2FA` when the caller has no method to verify with. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "help": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified, with one exception: a caller who has no wallet verification method yet (no transaction PIN, transaction code, recovery codes or authenticator) may create the participant's first signing key without sending one, when the participant holds no signing key that is not archived (a revoked key counts) and no key is being created or changed for it, on any provider, organization or network. The platform decides this itself, under a lock on the participant, so of two concurrent first-key creates only one goes through without verification. Every other create needs the wallet verification, as does a create with `purpose` `deposit`, a create that carries `walletVerification`, and any create once the caller has a verification method; without it the request is refused with `WALLET_VERIFICATION_REQUIRED`, or with `USER_MISSING_2FA` when the caller has no method to verify with. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
       "tags": [
         "Users"
       ],
@@ -18680,8 +18680,8 @@
       "method": "POST",
       "url": "/api/v2/users/me/custody-accounts/{custodyAccountId}/managed-lifecycle",
       "summary": "Start managed custody account revocation or archival",
-      "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
-      "help": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+      "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: revoking or archiving a signing key always needs the caller's wallet verification. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "help": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: revoking or archiving a signing key always needs the caller's wallet verification. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
       "tags": [
         "Users"
       ],
@@ -18725,7 +18725,7 @@
       ],
       "requestBodyDescription": null,
       "hasRequestBody": true,
-      "bodyIsComplex": false,
+      "bodyIsComplex": true,
       "bodyFields": [
         {
           "name": "operation",
@@ -18758,7 +18758,7 @@
       ],
       "examples": [
         {
-          "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+          "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: revoking or archiving a signing key always needs the caller's wallet verification. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
           "path": {
             "custodyAccountId": "<custodyAccountId>"
           }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@settlemint/dalp-cli",
-  "version": "3.1.33-main.43546076392",
+  "version": "3.1.33-main.43556327932",
   "private": false,
   "description": "CLI for the Digital Asset Lifecycle Platform — manage tokens, identities, compliance, and more from the command line.",
   "homepage": "https://settlemint.com",
@@ -50,14 +50,14 @@
   },
   "dependencies": {
     "@modelcontextprotocol/server": "2.4.0",
-    "@settlemint/dalp-sdk": "3.1.33-main.43546076392",
+    "@settlemint/dalp-sdk": "3.1.33-main.43556327932",
     "incur": "0.7.1",
     "zod": "4.6.7"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "0.18.5",
-    "@testkit/effect-bun-test": "3.1.33-main.43546076392",
-    "@tools/typescript-config": "3.1.33-main.43546076392",
+    "@testkit/effect-bun-test": "3.1.33-main.43556327932",
+    "@tools/typescript-config": "3.1.33-main.43556327932",
     "@types/bun": "1.4.4",
     "publint": "0.3.25"
   },

package/src/generated/openapi-surface.json

@@ -17889,8 +17889,8 @@
       "method": "POST",
       "url": "/api/v2/users/me/custody-account-requests/{requestId}/approval",
       "summary": "Approve a custody account lifecycle request",
-      "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
-      "help": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+      "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: approving a signing-key change always needs the caller's wallet verification, also when an external signer submits its artifact. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "help": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: approving a signing-key change always needs the caller's wallet verification, also when an external signer submits its artifact. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
       "tags": [
         "Users"
       ],
@@ -17934,7 +17934,7 @@
       ],
       "requestBodyDescription": null,
       "hasRequestBody": true,
-      "bodyIsComplex": false,
+      "bodyIsComplex": true,
       "bodyFields": [
         {
           "name": "existingSignerCustodyAccountId",
@@ -17972,7 +17972,7 @@
       ],
       "examples": [
         {
-          "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+          "description": "Approves with the selected existing account. Omit artifact for a managed signer. An external signer must submit the signature artifact over the prepared message. Send `participantId` when the request was started for a pending participant other than the one the session acts as. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: approving a signing-key change always needs the caller's wallet verification, also when an external signer submits its artifact. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
           "path": {
             "requestId": "<requestId>"
           }
@@ -17984,8 +17984,8 @@
       "method": "POST",
       "url": "/api/v2/users/me/custody-accounts/managed",
       "summary": "Create a managed custody account",
-      "description": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
-      "help": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "description": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified, with one exception: a caller who has no wallet verification method yet (no transaction PIN, transaction code, recovery codes or authenticator) may create the participant's first signing key without sending one, when the participant holds no signing key that is not archived (a revoked key counts) and no key is being created or changed for it, on any provider, organization or network. The platform decides this itself, under a lock on the participant, so of two concurrent first-key creates only one goes through without verification. Every other create needs the wallet verification, as does a create with `purpose` `deposit`, a create that carries `walletVerification`, and any create once the caller has a verification method; without it the request is refused with `WALLET_VERIFICATION_REQUIRED`, or with `USER_MISSING_2FA` when the caller has no method to verify with. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "help": "Creates an account with the selected enabled managed provider configuration and links it through the durable account lifecycle. By default the platform accepts the request and answers the lifecycle handle with its status URL under status 202. A caller that sends Prefer: wait=<seconds> waits for the lifecycle to settle and receives the settled result. The request is wallet-verified, with one exception: a caller who has no wallet verification method yet (no transaction PIN, transaction code, recovery codes or authenticator) may create the participant's first signing key without sending one, when the participant holds no signing key that is not archived (a revoked key counts) and no key is being created or changed for it, on any provider, organization or network. The platform decides this itself, under a lock on the participant, so of two concurrent first-key creates only one goes through without verification. Every other create needs the wallet verification, as does a create with `purpose` `deposit`, a create that carries `walletVerification`, and any create once the caller has a verification method; without it the request is refused with `WALLET_VERIFICATION_REQUIRED`, or with `USER_MISSING_2FA` when the caller has no method to verify with. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
       "tags": [
         "Users"
       ],
@@ -18680,8 +18680,8 @@
       "method": "POST",
       "url": "/api/v2/users/me/custody-accounts/{custodyAccountId}/managed-lifecycle",
       "summary": "Start managed custody account revocation or archival",
-      "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
-      "help": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+      "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: revoking or archiving a signing key always needs the caller's wallet verification. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
+      "help": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: revoking or archiving a signing key always needs the caller's wallet verification. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
       "tags": [
         "Users"
       ],
@@ -18725,7 +18725,7 @@
       ],
       "requestBodyDescription": null,
       "hasRequestBody": true,
-      "bodyIsComplex": false,
+      "bodyIsComplex": true,
       "bodyFields": [
         {
           "name": "operation",
@@ -18758,7 +18758,7 @@
       ],
       "examples": [
         {
-          "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles.",
+          "description": "Starts an exact managed-account lifecycle operation with a server-created provider attestation. External accounts must use the control preparation and signed lifecycle start operations. A request whose reconciliation is still running answers the 202 lifecycle handle unless Prefer: wait=<seconds> holds the request until it settles. The request is wallet-verified: revoking or archiving a signing key always needs the caller's wallet verification. A session caller also sends the `X-Step-Up-Challenge` header, issued by `POST /api/v2/step-up-challenges` for this operation, target, and body; the challenge is single-use.",
           "path": {
             "custodyAccountId": "<custodyAccountId>"
           }