@calimero-network/mero-js 13.2.4 → 13.3.0

package/dist/index.cjs

@@ -1167,6 +1167,39 @@ var AdminApiClient = class {
     const node = await this.getNodeIdentity();
     return { namespaceId, publicKey: node.publicKey, account: node.accountId };
   }
+  /**
+   * Ask this node to run one method on a member's behalf, under a warrant that
+   * member signed.
+   *
+   * The node executes and signs the envelope with its own key; the change is
+   * attributed to the **author**. Both halves travel together, so every peer
+   * re-checks that the member consented instead of trusting the relay.
+   *
+   * Three things have to be true first, and none is implied by the others:
+   *
+   * - the author's **account** is a member of the group owning the context —
+   *   their device joins nothing and is in no group's binding rows, which is
+   *   exactly the case a device certificate covers;
+   * - this node holds `CAN_AUTHOR_ON_BEHALF` on that group, which is implied by
+   *   neither membership nor admin;
+   * - the warrant has not been spent. It is single-use: presenting a valid one
+   *   twice is refused, because the signature stays valid forever and replay is
+   *   not forgery.
+   *
+   * A refusal comes back as a `403` carrying the reason — "an admin must grant
+   * CAN_AUTHOR_ON_BEHALF to …", or that the nonce is already spent — so a caller
+   * can tell which precondition failed rather than only that one did.
+   *
+   * This SDK does not mint warrants; see {@link PerformIntentRequest.warrant}.
+   */
+  async performIntent(contextId, request) {
+    return unwrap(
+      await this.httpClient.post(
+        `/admin-api/contexts/${contextId}/intents`,
+        request
+      )
+    );
+  }
   async listNamespacesForApplication(applicationId) {
     return unwrap(await this.httpClient.get(`/admin-api/namespaces/for-application/${applicationId}`));
   }