@calimero-network/mero-js 18.0.0 → 18.1.1

package/dist/admin-api/admin-client.d.ts

@@ -1,5 +1,5 @@
 import { HttpClient } from '../http-client/index.js';
-import type { HealthStatus, AdminAuthStatus, InstallApplicationRequest, InstallApplicationResponseData, InstallDevApplicationRequest, UninstallApplicationResponseData, ListApplicationsResponseData, GetApplicationResponseData, ApplicationVersionEntry, GetApplicationAbiResponseData, GetLatestVersionResponseData, ListPackagesResponseData, ListVersionsResponseData, CreateContextRequest, CreateContextResponseData, DeleteContextRequest, DeleteContextResponseData, GetContextsResponseData, Context, GenerateContextIdentityResponseData, GetContextIdentitiesResponseData, JoinContextResponseData, JoinSubgroupInheritanceResponseData, ContextGroupResponseData, ContextStorageResponseData, InviteSpecializedNodeRequest, InviteSpecializedNodeResponseData, UpdateContextApplicationRequest, ResyncContextRequest, ResyncContextResponseData, ContextsWithExecutorsResponseData, UploadBlobRequest, UploadBlobResponseData, DeleteBlobResponseData, ListBlobsResponseData, GetBlobInfoResponseData, CreateContextAliasRequest, CreateApplicationAliasRequest, CreateAliasResponseData, LookupAliasResponseData, DeleteAliasResponseData, ListAliasesResponseData, ListNamespacesResponseData, CreateNamespaceRequest, CreateNamespaceResponseData, DeleteNamespaceRequest, DeleteNamespaceResponseData, CreateNamespaceInvitationRequest, CreateNamespaceInvitationResponseData, CreateRecursiveInvitationResponseData, JoinNamespaceRequest, JoinNamespaceResponseData, CreateGroupInNamespaceRequest, CreateGroupInNamespaceResponseData, SubgroupEntry, Namespace, NamespaceIdentity, NodeIdentity, GroupInfoResponseData, DeleteGroupRequest, DeleteGroupResponseData, ListGroupMembersResponseData, ListGroupContextsResponseData, AddGroupMembersRequest, RemoveGroupMembersRequest, UpdateMemberRoleRequest, MemberCapabilities, SetMemberCapabilitiesRequest, SetDefaultCapabilitiesRequest, SetSubgroupVisibilityRequest, SetTeeAdmissionPolicyRequest, GetTeeAdmissionPolicyResponseData, SetGroupMetadataRequest, SetMemberMetadataRequest, SetContextMetadataRequest, MetadataRecord, SyncGroupRequest, SyncGroupResponseData, UpgradeGroupRequest, UpgradeGroupResponseData, GroupUpgradeStatusResponseData, MigrationStatus, CascadeStatusEntry, RetryGroupUpgradeRequest, RetryGroupUpgradeResponseData, ReparentGroupRequest, ReparentGroupResponseData, DetachContextFromGroupRequest, CreateGroupInvitationRequest, CreateGroupInvitationResponseData, CreateRecursiveGroupInvitationResponseData, JoinGroupRequest, JoinGroupResponseData, TeeInfoResponseData, TeeAttestRequest, TeeAttestResponseData, TeeVerifyQuoteRequest, TeeVerifyQuoteResponseData, PerformIntentRequest, PerformIntentResponseData, AdmitJoinRequest, AdmitJoinResponseData } from './admin-types.js';
+import type { HealthStatus, AdminAuthStatus, InstallApplicationRequest, InstallApplicationResponseData, InstallDevApplicationRequest, UninstallApplicationResponseData, ListApplicationsResponseData, GetApplicationResponseData, ApplicationVersionEntry, GetApplicationAbiResponseData, GetLatestVersionResponseData, ListPackagesResponseData, ListVersionsResponseData, CreateContextRequest, CreateContextResponseData, DeleteContextResponseData, GetContextsResponseData, Context, GenerateContextIdentityResponseData, GetContextIdentitiesResponseData, JoinContextResponseData, JoinSubgroupInheritanceResponseData, ContextGroupResponseData, ContextStorageResponseData, InviteSpecializedNodeRequest, InviteSpecializedNodeResponseData, UpdateContextApplicationRequest, ResyncContextRequest, ResyncContextResponseData, ContextsWithExecutorsResponseData, UploadBlobRequest, UploadBlobResponseData, DeleteBlobResponseData, ListBlobsResponseData, GetBlobInfoResponseData, CreateContextAliasRequest, CreateApplicationAliasRequest, CreateAliasResponseData, LookupAliasResponseData, DeleteAliasResponseData, ListAliasesResponseData, ListNamespacesResponseData, CreateNamespaceRequest, CreateNamespaceResponseData, DeleteNamespaceResponseData, CreateNamespaceInvitationRequest, CreateNamespaceInvitationResponseData, CreateRecursiveInvitationResponseData, JoinNamespaceRequest, JoinNamespaceResponseData, CreateGroupInNamespaceRequest, CreateGroupInNamespaceResponseData, SubgroupEntry, Namespace, NamespaceIdentity, NodeIdentity, AccountPairInitRequest, AccountPairInitResponseData, AccountPairCompleteRequest, AccountPairCompleteResponseData, RelinkDeviceRequest, RelinkDeviceResponseData, AccountDeviceEntry, AccountApplicationEntry, RevokeAccountDeviceRequest, RevokeAccountDeviceResponseData, GroupInfoResponseData, CreateGroupRequest, CreateGroupResponseData, DeleteGroupResponseData, ListGroupMembersResponseData, ListGroupContextsResponseData, AddGroupMembersRequest, RemoveGroupMembersRequest, UpdateMemberRoleRequest, MemberCapabilities, SetMemberCapabilitiesRequest, SetDefaultCapabilitiesRequest, SetMemberAutoFollowRequest, SetSubgroupVisibilityRequest, SetTeeAdmissionPolicyRequest, GetTeeAdmissionPolicyResponseData, SetGroupMetadataRequest, SetMemberMetadataRequest, SetContextMetadataRequest, MetadataRecord, SyncGroupResponseData, UpgradeGroupRequest, UpgradeGroupResponseData, GroupUpgradeStatusResponseData, MigrationStatus, CascadeStatusEntry, RetryGroupUpgradeResponseData, ReparentGroupRequest, ReparentGroupResponseData, IssueOwnershipProofRequest, IssueNamespaceOwnershipProofRequest, IssueOwnershipProofResponseData, CreateGroupInvitationRequest, CreateGroupInvitationResponseData, CreateRecursiveGroupInvitationResponseData, JoinGroupRequest, JoinGroupResponseData, TeeInfoResponseData, TeeAttestRequest, TeeAttestResponseData, TeeVerifyQuoteRequest, TeeVerifyQuoteResponseData, PerformIntentRequest, PerformIntentResponseData, AdmitJoinRequest, AdmitJoinResponseData } from './admin-types.js';
 /**
  * Compare two version strings by SemVer 2.0 precedence, ascending: negative if
  * `a < b`, positive if `a > b`, `0` if equal. Build metadata (`+...`) is stripped
@@ -52,7 +52,7 @@ export declare class AdminApiClient {
     listPackageVersions(packageName: string): Promise<ListVersionsResponseData>;
     getLatestPackageVersion(packageName: string): Promise<GetLatestVersionResponseData>;
     createContext(request: CreateContextRequest): Promise<CreateContextResponseData>;
-    deleteContext(contextId: string, request?: DeleteContextRequest): Promise<DeleteContextResponseData>;
+    deleteContext(contextId: string): Promise<DeleteContextResponseData>;
     getContexts(): Promise<GetContextsResponseData>;
     getContext(contextId: string): Promise<Context>;
     getContextsForApplication(applicationId: string): Promise<GetContextsResponseData>;
@@ -155,7 +155,7 @@ export declare class AdminApiClient {
     performIntent(contextId: string, request: PerformIntentRequest): Promise<PerformIntentResponseData>;
     listNamespacesForApplication(applicationId: string): Promise<ListNamespacesResponseData>;
     createNamespace(request: CreateNamespaceRequest): Promise<CreateNamespaceResponseData>;
-    deleteNamespace(namespaceId: string, request?: DeleteNamespaceRequest): Promise<DeleteNamespaceResponseData>;
+    deleteNamespace(namespaceId: string): Promise<DeleteNamespaceResponseData>;
     createNamespaceInvitation(namespaceId: string, request?: CreateNamespaceInvitationRequest): Promise<CreateNamespaceInvitationResponseData | CreateRecursiveInvitationResponseData>;
     /**
      * Present a join this caller signed to a node the inviter named as an
@@ -178,12 +178,103 @@ export declare class AdminApiClient {
     joinNamespace(namespaceId: string, request: JoinNamespaceRequest): Promise<JoinNamespaceResponseData>;
     createGroupInNamespace(namespaceId: string, request?: CreateGroupInNamespaceRequest): Promise<CreateGroupInNamespaceResponseData>;
     listNamespaceGroups(namespaceId: string): Promise<SubgroupEntry[]>;
+    /**
+     * Mint this node a device for an account that already lives somewhere else -
+     * the first half of pairing, run on the joining node.
+     *
+     * Publishes nothing and needs no key: it produces the device id, the two
+     * public keys and the signature that the account holder's
+     * {@link completeAccountPairing} certifies, plus a code to read out to them
+     * over a channel the payload does not travel on. Until that second half runs,
+     * the device this mints is inert.
+     *
+     * Takes a set of namespaces rather than one, and takes it from the caller
+     * because this node cannot discover it: a node that is a member of nothing can
+     * neither read the account's namespace set off a DAG nor derive it. One device
+     * covers however many are named - the certificate is over the account, not a
+     * scope - so there is one id and one code to hand over regardless.
+     */
+    initAccountPairing(request: AccountPairInitRequest): Promise<AccountPairInitResponseData>;
+    /**
+     * Certify a device another node minted, link it, and deliver its scope keys -
+     * the second half of pairing, run on the node that holds the account root.
+     *
+     * Every field but `applications` is copied verbatim out of that node's
+     * {@link initAccountPairing} answer. Only this side can complete it: the
+     * certificate is signed by the account root, which never leaves the node that
+     * holds it.
+     *
+     * The scope is named in applications, not namespaces, because that is the
+     * question a person can answer - a namespace is an implementation unit they
+     * never chose. Leave it out to grant every application.
+     */
+    completeAccountPairing(request: AccountPairCompleteRequest): Promise<AccountPairCompleteResponseData>;
+    /**
+     * Re-run the pairing fan-out for a device this account already certified,
+     * against the namespaces this node takes part in now.
+     *
+     * Pairing is a snapshot, and this is how it is repeated. A namespace created
+     * or joined afterwards holds no binding for a device paired before it, and the
+     * symptom is silence - the device simply never sees that namespace. Nothing
+     * but the id is needed to repair it: the certificate is already held here,
+     * root-signed and naming no namespace, so a fresh endorsement and a key wrap
+     * are all a later namespace is missing. The device does not have to be online.
+     *
+     * Passing `applications` widens the device's stored scope as well as
+     * repairing. Passing none - or an empty list - repairs against the scope
+     * already stored, which is deliberately NOT the "every application" that an
+     * empty list means on {@link completeAccountPairing}: overloading it here
+     * would make the accidental request the widest one.
+     */
+    relinkAccountDevice(deviceId: string, request?: RelinkDeviceRequest): Promise<RelinkDeviceResponseData>;
+    /**
+     * Every device of this account, as this node sees them - its own included.
+     *
+     * Joined from the node-local certificate cache and the live bindings of every
+     * namespace this node takes part in, so it is this node's view rather than a
+     * global one: a device certified by another holder appears with an empty
+     * `applications`, because the certificate that would name its scope is not
+     * cached here.
+     *
+     * The wire wraps this in `devices` rather than the usual `data`; the array is
+     * what a caller wants, so that wrapper is not passed on.
+     */
+    listAccountDevices(): Promise<AccountDeviceEntry[]>;
+    /**
+     * Every application this account speaks in, with the namespaces targeting each.
+     *
+     * What a device-scoping UI lists: {@link completeAccountPairing} and
+     * {@link relinkAccountDevice} both take applications, and this is where the
+     * ids they take come from. Derived from the namespaces this node takes part
+     * in, so an application installed with no namespace yet is absent - it has
+     * nothing to scope a device to until one exists.
+     *
+     * Wrapped in `applications` on the wire rather than `data`, unwrapped here for
+     * the same reason {@link listAccountDevices} unwraps `devices`.
+     */
+    listAccountApplications(): Promise<AccountApplicationEntry[]>;
+    /**
+     * Withdraw a device from this account, terminally.
+     *
+     * Two authorities reach the same endpoint. An admin may revoke any device and
+     * rotates the scope key as it goes. The account holder may revoke its own with
+     * a root-signed `proof`, which does not rotate - so read
+     * {@link RevokeAccountDeviceResponseData.revokedIn} rather than assuming the
+     * device lost its access: a namespace reporting `keyRotated: false` has
+     * stopped the device writing but leaves it able to read until an admin
+     * rotates.
+     *
+     * `namespaceId` names where to publish from, not the extent of the revocation:
+     * a device belongs to the account, so every namespace holding a binding for it
+     * is withdrawn from and reported back.
+     */
+    revokeAccountDevice(namespaceId: string, request: RevokeAccountDeviceRequest): Promise<RevokeAccountDeviceResponseData>;
     getGroupInfo(groupId: string): Promise<GroupInfoResponseData>;
     /** Thin wrapper over {@link getGroupInfo}: returns the group's `defaultCapabilities` bitmask. */
     getDefaultCapabilities(groupId: string): Promise<number>;
     /** Thin wrapper over {@link getGroupInfo}: returns the group's `subgroupVisibility`. */
     getSubgroupVisibility(groupId: string): Promise<string>;
-    deleteGroup(groupId: string, request?: DeleteGroupRequest): Promise<DeleteGroupResponseData>;
+    deleteGroup(groupId: string): Promise<DeleteGroupResponseData>;
     listGroupMembers(groupId: string): Promise<ListGroupMembersResponseData>;
     listGroupContexts(groupId: string): Promise<ListGroupContextsResponseData>;
     addGroupMembers(groupId: string, request: AddGroupMembersRequest): Promise<void>;
@@ -221,7 +312,7 @@ export declare class AdminApiClient {
     getMemberMetadata(groupId: string, identity: string): Promise<MetadataRecord | null>;
     setContextMetadata(groupId: string, contextId: string, request: SetContextMetadataRequest): Promise<void>;
     getContextMetadata(groupId: string, contextId: string): Promise<MetadataRecord | null>;
-    syncGroup(groupId: string, request?: SyncGroupRequest): Promise<SyncGroupResponseData>;
+    syncGroup(groupId: string): Promise<SyncGroupResponseData>;
     upgradeGroup(groupId: string, request: UpgradeGroupRequest): Promise<UpgradeGroupResponseData>;
     getGroupUpgradeStatus(groupId: string): Promise<GroupUpgradeStatusResponseData>;
     /**
@@ -232,11 +323,11 @@ export declare class AdminApiClient {
     getMigrationStatus(namespaceId: string): Promise<MigrationStatus>;
     /** Per-group cascade-migration snapshots for a namespace. */
     getCascadeStatus(namespaceId: string): Promise<CascadeStatusEntry[]>;
-    retryGroupUpgrade(groupId: string, request?: RetryGroupUpgradeRequest): Promise<RetryGroupUpgradeResponseData>;
+    retryGroupUpgrade(groupId: string): Promise<RetryGroupUpgradeResponseData>;
     /** Move `childGroupId` under `request.newParentId`. */
     reparentGroup(childGroupId: string, request: ReparentGroupRequest): Promise<ReparentGroupResponseData>;
     listSubgroups(groupId: string): Promise<SubgroupEntry[]>;
-    detachContextFromGroup(groupId: string, contextId: string, request?: DetachContextFromGroupRequest): Promise<void>;
+    detachContextFromGroup(groupId: string, contextId: string): Promise<void>;
     createGroupInvitation(groupId: string, request?: CreateGroupInvitationRequest): Promise<CreateGroupInvitationResponseData | CreateRecursiveGroupInvitationResponseData>;
     joinGroup(request: JoinGroupRequest): Promise<JoinGroupResponseData>;
     joinSubgroupInheritance(groupId: string): Promise<JoinSubgroupInheritanceResponseData>;
@@ -253,19 +344,17 @@ export declare class AdminApiClient {
     /** Node TLS certificate, PEM text (GET /admin-api/certificate). */
     getCertificate(): Promise<string>;
     /** Create a standalone group (POST /admin-api/groups). */
-    createGroup(request: Record<string, unknown>): Promise<{
-        groupId: string;
-    }>;
+    createGroup(request: CreateGroupRequest): Promise<CreateGroupResponseData>;
     /** Leave a group (POST /admin-api/groups/:group_id/leave). */
-    leaveGroup(groupId: string, request?: Record<string, unknown>): Promise<void>;
+    leaveGroup(groupId: string): Promise<void>;
     /** Leave a context (POST /admin-api/contexts/:context_id/leave). */
-    leaveContext(contextId: string, request?: Record<string, unknown>): Promise<void>;
+    leaveContext(contextId: string): Promise<void>;
     /** Leave a namespace (POST /admin-api/namespaces/:namespace_id/leave). */
-    leaveNamespace(namespaceId: string, request?: Record<string, unknown>): Promise<void>;
+    leaveNamespace(namespaceId: string): Promise<void>;
     /** Issue a group ownership proof (POST /admin-api/groups/:group_id/issue-ownership-proof). */
-    issueOwnershipProof(groupId: string, request?: Record<string, unknown>): Promise<unknown>;
+    issueOwnershipProof(groupId: string, request: IssueOwnershipProofRequest): Promise<IssueOwnershipProofResponseData>;
     /** Issue a namespace ownership proof (POST /admin-api/groups/:group_id/issue-namespace-ownership-proof). */
-    issueNamespaceOwnershipProof(groupId: string, request?: Record<string, unknown>): Promise<unknown>;
+    issueNamespaceOwnershipProof(groupId: string, request: IssueNamespaceOwnershipProofRequest): Promise<IssueOwnershipProofResponseData>;
     /**
      * Set a member's auto-follow flag (PUT
      * /admin-api/groups/:group_id/members/:identity/auto-follow).
@@ -274,7 +363,7 @@ export declare class AdminApiClient {
      * {@link listGroupMembers} — not the signing key that added them. Both are
      * 64 hex, so nothing but the source tells them apart.
      */
-    setMemberAutoFollow(groupId: string, identity: string, request: Record<string, unknown>): Promise<void>;
+    setMemberAutoFollow(groupId: string, identity: string, request: SetMemberAutoFollowRequest): Promise<void>;
     /** Abort a namespace migration (POST /admin-api/groups/:namespace_id/migration/abort). */
-    abortMigration(namespaceId: string, request?: Record<string, unknown>): Promise<unknown>;
+    abortMigration(namespaceId: string): Promise<unknown>;
 }

package/dist/admin-api/admin-client.js

@@ -184,14 +184,7 @@ export class AdminApiClient {
         const body = { ...request, initializationParams: request.initializationParams ?? [] };
         return unwrap(await this.httpClient.post('/admin-api/contexts', body));
     }
-    async deleteContext(contextId, request) {
-        if (request) {
-            return unwrap(await this.httpClient.request(`/admin-api/contexts/${contextId}`, {
-                method: 'DELETE',
-                body: JSON.stringify(request),
-                headers: { 'Content-Type': 'application/json' },
-            }));
-        }
+    async deleteContext(contextId) {
         return unwrap(await this.httpClient.delete(`/admin-api/contexts/${contextId}`));
     }
     async getContexts() {
@@ -417,30 +410,14 @@ export class AdminApiClient {
         return unwrap(await this.httpClient.get(`/admin-api/namespaces/for-application/${applicationId}`));
     }
     async createNamespace(request) {
-        // `upgradePolicy` is sent even though the request type no longer carries it.
-        //
-        // The concept was deleted server-side (calimero-network/core#3393), but only
-        // on master: every RELEASED node still declares the field required and
-        // rejects a body without it — `missing field 'upgradePolicy'`. A node that
-        // has dropped it ignores the extra key, so sending it is the one shape that
-        // works against both, and this SDK does not get to choose which node a
-        // caller points it at.
-        //
-        // `LazyOnAccess` because it was the default and is the only behaviour that
-        // survives the removal, so an old node given it does what a new one does.
-        //
-        // Remove once no supported release predates that change.
-        return unwrap(await this.httpClient.post('/admin-api/namespaces', {
-            upgradePolicy: 'LazyOnAccess',
-            ...request,
-        }));
+        return unwrap(await this.httpClient.post('/admin-api/namespaces', request));
     }
-    async deleteNamespace(namespaceId, request) {
-        // Core requires `Content-Type: application/json` on this DELETE even when the
-        // body is empty, so always send the header and a (possibly empty) JSON body.
+    async deleteNamespace(namespaceId) {
+        // Core requires `Content-Type: application/json` on this DELETE even though
+        // the body is always empty, so send the header and an empty JSON object.
         return unwrap(await this.httpClient.request(`/admin-api/namespaces/${namespaceId}`, {
             method: 'DELETE',
-            body: JSON.stringify(request ?? {}),
+            body: '{}',
             headers: { 'Content-Type': 'application/json' },
         }));
     }
@@ -486,6 +463,112 @@ export class AdminApiClient {
     async listNamespaceGroups(namespaceId) {
         return unwrap(await this.httpClient.get(`/admin-api/namespaces/${namespaceId}/groups`));
     }
+    // ---- Account Devices & Pairing ----
+    /**
+     * Mint this node a device for an account that already lives somewhere else -
+     * the first half of pairing, run on the joining node.
+     *
+     * Publishes nothing and needs no key: it produces the device id, the two
+     * public keys and the signature that the account holder's
+     * {@link completeAccountPairing} certifies, plus a code to read out to them
+     * over a channel the payload does not travel on. Until that second half runs,
+     * the device this mints is inert.
+     *
+     * Takes a set of namespaces rather than one, and takes it from the caller
+     * because this node cannot discover it: a node that is a member of nothing can
+     * neither read the account's namespace set off a DAG nor derive it. One device
+     * covers however many are named - the certificate is over the account, not a
+     * scope - so there is one id and one code to hand over regardless.
+     */
+    async initAccountPairing(request) {
+        return unwrap(await this.httpClient.post('/admin-api/account/pair-init', request));
+    }
+    /**
+     * Certify a device another node minted, link it, and deliver its scope keys -
+     * the second half of pairing, run on the node that holds the account root.
+     *
+     * Every field but `applications` is copied verbatim out of that node's
+     * {@link initAccountPairing} answer. Only this side can complete it: the
+     * certificate is signed by the account root, which never leaves the node that
+     * holds it.
+     *
+     * The scope is named in applications, not namespaces, because that is the
+     * question a person can answer - a namespace is an implementation unit they
+     * never chose. Leave it out to grant every application.
+     */
+    async completeAccountPairing(request) {
+        return unwrap(await this.httpClient.post('/admin-api/account/pair-complete', request));
+    }
+    /**
+     * Re-run the pairing fan-out for a device this account already certified,
+     * against the namespaces this node takes part in now.
+     *
+     * Pairing is a snapshot, and this is how it is repeated. A namespace created
+     * or joined afterwards holds no binding for a device paired before it, and the
+     * symptom is silence - the device simply never sees that namespace. Nothing
+     * but the id is needed to repair it: the certificate is already held here,
+     * root-signed and naming no namespace, so a fresh endorsement and a key wrap
+     * are all a later namespace is missing. The device does not have to be online.
+     *
+     * Passing `applications` widens the device's stored scope as well as
+     * repairing. Passing none - or an empty list - repairs against the scope
+     * already stored, which is deliberately NOT the "every application" that an
+     * empty list means on {@link completeAccountPairing}: overloading it here
+     * would make the accidental request the widest one.
+     */
+    async relinkAccountDevice(deviceId, request) {
+        return unwrap(await this.httpClient.post(`/admin-api/account/devices/${deviceId}/relink`, request ?? {}));
+    }
+    /**
+     * Every device of this account, as this node sees them - its own included.
+     *
+     * Joined from the node-local certificate cache and the live bindings of every
+     * namespace this node takes part in, so it is this node's view rather than a
+     * global one: a device certified by another holder appears with an empty
+     * `applications`, because the certificate that would name its scope is not
+     * cached here.
+     *
+     * The wire wraps this in `devices` rather than the usual `data`; the array is
+     * what a caller wants, so that wrapper is not passed on.
+     */
+    async listAccountDevices() {
+        const response = await this.httpClient.get('/admin-api/account/devices');
+        return response.devices;
+    }
+    /**
+     * Every application this account speaks in, with the namespaces targeting each.
+     *
+     * What a device-scoping UI lists: {@link completeAccountPairing} and
+     * {@link relinkAccountDevice} both take applications, and this is where the
+     * ids they take come from. Derived from the namespaces this node takes part
+     * in, so an application installed with no namespace yet is absent - it has
+     * nothing to scope a device to until one exists.
+     *
+     * Wrapped in `applications` on the wire rather than `data`, unwrapped here for
+     * the same reason {@link listAccountDevices} unwraps `devices`.
+     */
+    async listAccountApplications() {
+        const response = await this.httpClient.get('/admin-api/account/applications');
+        return response.applications;
+    }
+    /**
+     * Withdraw a device from this account, terminally.
+     *
+     * Two authorities reach the same endpoint. An admin may revoke any device and
+     * rotates the scope key as it goes. The account holder may revoke its own with
+     * a root-signed `proof`, which does not rotate - so read
+     * {@link RevokeAccountDeviceResponseData.revokedIn} rather than assuming the
+     * device lost its access: a namespace reporting `keyRotated: false` has
+     * stopped the device writing but leaves it able to read until an admin
+     * rotates.
+     *
+     * `namespaceId` names where to publish from, not the extent of the revocation:
+     * a device belongs to the account, so every namespace holding a binding for it
+     * is withdrawn from and reported back.
+     */
+    async revokeAccountDevice(namespaceId, request) {
+        return unwrap(await this.httpClient.post(`/admin-api/namespaces/${namespaceId}/account/revoke`, request));
+    }
     // ---- Group Management ----
     async getGroupInfo(groupId) {
         return unwrap(await this.httpClient.get(`/admin-api/groups/${groupId}`));
@@ -498,12 +581,12 @@ export class AdminApiClient {
     async getSubgroupVisibility(groupId) {
         return (await this.getGroupInfo(groupId)).subgroupVisibility;
     }
-    async deleteGroup(groupId, request) {
-        // Core requires `Content-Type: application/json` on this DELETE even with an
-        // empty body, so always send the header and a (possibly empty) JSON body.
+    async deleteGroup(groupId) {
+        // Core requires `Content-Type: application/json` on this DELETE even though
+        // the body is always empty, so send the header and an empty JSON object.
         return unwrap(await this.httpClient.request(`/admin-api/groups/${groupId}`, {
             method: 'DELETE',
-            body: JSON.stringify(request ?? {}),
+            body: '{}',
             headers: { 'Content-Type': 'application/json' },
         }));
     }
@@ -604,8 +687,8 @@ export class AdminApiClient {
         const response = await this.httpClient.get(`/admin-api/groups/${groupId}/contexts/${contextId}/metadata`);
         return response?.data ?? null;
     }
-    async syncGroup(groupId, request) {
-        return unwrap(await this.httpClient.post(`/admin-api/groups/${groupId}/sync`, request ?? {}));
+    async syncGroup(groupId) {
+        return unwrap(await this.httpClient.post(`/admin-api/groups/${groupId}/sync`, {}));
     }
     async upgradeGroup(groupId, request) {
         return unwrap(await this.httpClient.post(`/admin-api/groups/${groupId}/upgrade`, request));
@@ -627,8 +710,8 @@ export class AdminApiClient {
         const id = encodeURIComponent(namespaceId);
         return unwrap(await this.httpClient.get(`/admin-api/groups/${id}/cascade-status`));
     }
-    async retryGroupUpgrade(groupId, request) {
-        return unwrap(await this.httpClient.post(`/admin-api/groups/${groupId}/upgrade/retry`, request ?? {}));
+    async retryGroupUpgrade(groupId) {
+        return unwrap(await this.httpClient.post(`/admin-api/groups/${groupId}/upgrade/retry`, {}));
     }
     /** Move `childGroupId` under `request.newParentId`. */
     async reparentGroup(childGroupId, request) {
@@ -640,8 +723,8 @@ export class AdminApiClient {
         const response = await this.httpClient.get(`/admin-api/groups/${groupId}/subgroups`);
         return response.subgroups ?? response.data ?? [];
     }
-    async detachContextFromGroup(groupId, contextId, request) {
-        await this.httpClient.post(`/admin-api/groups/${groupId}/contexts/${contextId}/remove`, request ?? {});
+    async detachContextFromGroup(groupId, contextId) {
+        await this.httpClient.post(`/admin-api/groups/${groupId}/contexts/${contextId}/remove`, {});
     }
     // ---- Group Invitation & Join ----
     async createGroupInvitation(groupId, request) {
@@ -682,34 +765,27 @@ export class AdminApiClient {
     // ---- Group / context / namespace membership ----
     /** Create a standalone group (POST /admin-api/groups). */
     async createGroup(request) {
-        // `upgradePolicy` for the same reason as `createNamespace` above — these are
-        // the only two requests a released node still requires it on, and it ignores
-        // the extra key once the concept is gone. Spread after the caller's request
-        // so an explicit value wins.
-        return unwrap(await this.httpClient.post('/admin-api/groups', {
-            upgradePolicy: 'LazyOnAccess',
-            ...request,
-        }));
+        return unwrap(await this.httpClient.post('/admin-api/groups', request));
     }
     /** Leave a group (POST /admin-api/groups/:group_id/leave). */
-    async leaveGroup(groupId, request) {
-        await this.httpClient.post(`/admin-api/groups/${groupId}/leave`, request ?? {});
+    async leaveGroup(groupId) {
+        await this.httpClient.post(`/admin-api/groups/${groupId}/leave`, {});
     }
     /** Leave a context (POST /admin-api/contexts/:context_id/leave). */
-    async leaveContext(contextId, request) {
-        await this.httpClient.post(`/admin-api/contexts/${contextId}/leave`, request ?? {});
+    async leaveContext(contextId) {
+        await this.httpClient.post(`/admin-api/contexts/${contextId}/leave`, {});
     }
     /** Leave a namespace (POST /admin-api/namespaces/:namespace_id/leave). */
-    async leaveNamespace(namespaceId, request) {
-        await this.httpClient.post(`/admin-api/namespaces/${namespaceId}/leave`, request ?? {});
+    async leaveNamespace(namespaceId) {
+        await this.httpClient.post(`/admin-api/namespaces/${namespaceId}/leave`, {});
     }
     /** Issue a group ownership proof (POST /admin-api/groups/:group_id/issue-ownership-proof). */
     async issueOwnershipProof(groupId, request) {
-        return this.httpClient.post(`/admin-api/groups/${groupId}/issue-ownership-proof`, request ?? {});
+        return this.httpClient.post(`/admin-api/groups/${groupId}/issue-ownership-proof`, request);
     }
     /** Issue a namespace ownership proof (POST /admin-api/groups/:group_id/issue-namespace-ownership-proof). */
     async issueNamespaceOwnershipProof(groupId, request) {
-        return this.httpClient.post(`/admin-api/groups/${groupId}/issue-namespace-ownership-proof`, request ?? {});
+        return this.httpClient.post(`/admin-api/groups/${groupId}/issue-namespace-ownership-proof`, request);
     }
     /**
      * Set a member's auto-follow flag (PUT
@@ -723,7 +799,7 @@ export class AdminApiClient {
         await this.httpClient.put(`/admin-api/groups/${groupId}/members/${identity}/auto-follow`, request);
     }
     /** Abort a namespace migration (POST /admin-api/groups/:namespace_id/migration/abort). */
-    async abortMigration(namespaceId, request) {
-        return this.httpClient.post(`/admin-api/groups/${namespaceId}/migration/abort`, request ?? {});
+    async abortMigration(namespaceId) {
+        return this.httpClient.post(`/admin-api/groups/${namespaceId}/migration/abort`, {});
     }
 }