@settlemint/dalp-cli 3.1.33-main.43236641077 → 3.1.33-main.43247098428

package/dist/{openapi-surface-3q0zashj.json → openapi-surface-kbttkqwt.json}

@@ -24270,8 +24270,8 @@
       "method": "POST",
       "url": "/api/v2/participants/{participantId}/wallets/{walletId}/removal",
       "summary": "Remove an account participant wallet",
-      "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs its own unregistration; on a chain whose registry predates self-removal, the organization's system key executes it. Nothing is submitted when the wallet still holds a token balance in an organization, still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
-      "help": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs its own unregistration; on a chain whose registry predates self-removal, the organization's system key executes it. Nothing is submitted when the wallet still holds a token balance in an organization, still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
+      "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs only the removal of a registration that is still pending. An approved registration is removed by the organization's managed signer, which must hold the identity manager role on the organization's system; when the organization has no managed signer on that chain, or its signer lacks that role, the removal is refused with `data.reason` `organization-signer-missing`. Before the organization's signer submits, the wallet's balance of every token on the system is read again at the chain head, and the removal is refused with `data.reason` `holder-locked` while the holder's identity has a lock-up holder lock on any token of the system that has not reached its unlock time. Nothing is submitted when the wallet still holds a token balance in an organization (`holds-balance`), still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
+      "help": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs only the removal of a registration that is still pending. An approved registration is removed by the organization's managed signer, which must hold the identity manager role on the organization's system; when the organization has no managed signer on that chain, or its signer lacks that role, the removal is refused with `data.reason` `organization-signer-missing`. Before the organization's signer submits, the wallet's balance of every token on the system is read again at the chain head, and the removal is refused with `data.reason` `holder-locked` while the holder's identity has a lock-up holder lock on any token of the system that has not reached its unlock time. Nothing is submitted when the wallet still holds a token balance in an organization (`holds-balance`), still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
       "tags": [
         "Participants"
       ],
@@ -24330,7 +24330,7 @@
       "bodyFields": [],
       "examples": [
         {
-          "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs its own unregistration; on a chain whose registry predates self-removal, the organization's system key executes it. Nothing is submitted when the wallet still holds a token balance in an organization, still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
+          "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs only the removal of a registration that is still pending. An approved registration is removed by the organization's managed signer, which must hold the identity manager role on the organization's system; when the organization has no managed signer on that chain, or its signer lacks that role, the removal is refused with `data.reason` `organization-signer-missing`. Before the organization's signer submits, the wallet's balance of every token on the system is read again at the chain head, and the removal is refused with `data.reason` `holder-locked` while the holder's identity has a lock-up holder lock on any token of the system that has not reached its unlock time. Nothing is submitted when the wallet still holds a token balance in an organization (`holds-balance`), still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
           "path": {
             "participantId": "<participantId>",
             "walletId": "<walletId>"
@@ -63262,6 +63262,17 @@
               "examples": [],
               "fields": []
             },
+            {
+              "name": "structureRole",
+              "in": "query",
+              "required": false,
+              "description": "A structure member, as `<structureId>:<role>`: the tokens issued in that role of the structure. The `structureRole` facet counts them the same way.",
+              "type": "string",
+              "enum": null,
+              "pattern": null,
+              "examples": [],
+              "fields": []
+            },
             {
               "name": "status",
               "in": "query",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@settlemint/dalp-cli",
-  "version": "3.1.33-main.43236641077",
+  "version": "3.1.33-main.43247098428",
   "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.43236641077",
+    "@settlemint/dalp-sdk": "3.1.33-main.43247098428",
     "incur": "0.7.1",
     "zod": "4.6.7"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "0.18.5",
-    "@testkit/effect-bun-test": "3.1.33-main.43236641077",
-    "@tools/typescript-config": "3.1.33-main.43236641077",
+    "@testkit/effect-bun-test": "3.1.33-main.43247098428",
+    "@tools/typescript-config": "3.1.33-main.43247098428",
     "@types/bun": "1.4.4",
     "publint": "0.3.25"
   },

package/src/generated/openapi-surface.json

@@ -24270,8 +24270,8 @@
       "method": "POST",
       "url": "/api/v2/participants/{participantId}/wallets/{walletId}/removal",
       "summary": "Remove an account participant wallet",
-      "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs its own unregistration; on a chain whose registry predates self-removal, the organization's system key executes it. Nothing is submitted when the wallet still holds a token balance in an organization, still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
-      "help": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs its own unregistration; on a chain whose registry predates self-removal, the organization's system key executes it. Nothing is submitted when the wallet still holds a token balance in an organization, still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
+      "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs only the removal of a registration that is still pending. An approved registration is removed by the organization's managed signer, which must hold the identity manager role on the organization's system; when the organization has no managed signer on that chain, or its signer lacks that role, the removal is refused with `data.reason` `organization-signer-missing`. Before the organization's signer submits, the wallet's balance of every token on the system is read again at the chain head, and the removal is refused with `data.reason` `holder-locked` while the holder's identity has a lock-up holder lock on any token of the system that has not reached its unlock time. Nothing is submitted when the wallet still holds a token balance in an organization (`holds-balance`), still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
+      "help": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs only the removal of a registration that is still pending. An approved registration is removed by the organization's managed signer, which must hold the identity manager role on the organization's system; when the organization has no managed signer on that chain, or its signer lacks that role, the removal is refused with `data.reason` `organization-signer-missing`. Before the organization's signer submits, the wallet's balance of every token on the system is read again at the chain head, and the removal is refused with `data.reason` `holder-locked` while the holder's identity has a lock-up holder lock on any token of the system that has not reached its unlock time. Nothing is submitted when the wallet still holds a token balance in an organization (`holds-balance`), still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
       "tags": [
         "Participants"
       ],
@@ -24330,7 +24330,7 @@
       "bodyFields": [],
       "examples": [
         {
-          "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs its own unregistration; on a chain whose registry predates self-removal, the organization's system key executes it. Nothing is submitted when the wallet still holds a token balance in an organization, still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
+          "description": "Unregisters the wallet from every organization and chain it is registered on, then archives it. The wallet signs only the removal of a registration that is still pending. An approved registration is removed by the organization's managed signer, which must hold the identity manager role on the organization's system; when the organization has no managed signer on that chain, or its signer lacks that role, the removal is refused with `data.reason` `organization-signer-missing`. Before the organization's signer submits, the wallet's balance of every token on the system is read again at the chain head, and the removal is refused with `data.reason` `holder-locked` while the holder's identity has a lock-up holder lock on any token of the system that has not reached its unlock time. Nothing is submitted when the wallet still holds a token balance in an organization (`holds-balance`), still signs for a live smart wallet, or is still held by a custody account that is not archived; the answer is then 409 `PARTICIPANT_WALLET_REMOVAL_REFUSED`, and `data.reason` names which. Removing the participant's last wallet on a chain also archives its identity on that chain and its registration requests with the organizations where it then holds no identity; onboarding again creates a new identity. The participant's claims and its other wallets are unaffected. The request is wallet-verified.",
           "path": {
             "participantId": "<participantId>",
             "walletId": "<walletId>"
@@ -63262,6 +63262,17 @@
               "examples": [],
               "fields": []
             },
+            {
+              "name": "structureRole",
+              "in": "query",
+              "required": false,
+              "description": "A structure member, as `<structureId>:<role>`: the tokens issued in that role of the structure. The `structureRole` facet counts them the same way.",
+              "type": "string",
+              "enum": null,
+              "pattern": null,
+              "examples": [],
+              "fields": []
+            },
             {
               "name": "status",
               "in": "query",