@calimero-network/mero-js 24.2.0 → 24.4.0

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

@@ -230,16 +230,18 @@ export declare class AdminApiClient {
      * Ask what this node can do for a member in `contextId`, before they sign
      * anything.
      *
-     * The two facts {@link performIntent} needs and a client cannot derive: whose
-     * account and key go in the warrant's `executor` and `executor_key`, and
-     * whether this node holds `CAN_AUTHOR_ON_BEHALF` on the owning group.
+     * The facts {@link performIntent} needs and a client cannot derive: whose
+     * account and key go in the warrant's `executor` and `executor_key`, which
+     * release it pins, and whether this node holds `CAN_AUTHOR_ON_BEHALF` on the
+     * owning group.
      * `canAuthorOnBehalf: false` comes back as an answer rather than an error, as
      * it is the default state of every context, so a caller can say "an admin of
      * `groupId` must grant it to `executorAccount`" instead of presenting a
      * warrant that will be refused after the author has spent a nonce on it.
      *
-     * `404` means the context belongs to no group, or this node holds no account
-     * yet; either way it can be named as no warrant's executor.
+     * `404` means the context belongs to no group, this node holds no account or
+     * identity in it yet, or its group names no release yet; no warrant can be
+     * spent here until that changes.
      *
      * For a caller with no credential on the node at all — a browser tab holding
      * one signing key — use `RelayClient`, which reads this same route on a node

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

@@ -562,16 +562,18 @@ export class AdminApiClient {
      * Ask what this node can do for a member in `contextId`, before they sign
      * anything.
      *
-     * The two facts {@link performIntent} needs and a client cannot derive: whose
-     * account and key go in the warrant's `executor` and `executor_key`, and
-     * whether this node holds `CAN_AUTHOR_ON_BEHALF` on the owning group.
+     * The facts {@link performIntent} needs and a client cannot derive: whose
+     * account and key go in the warrant's `executor` and `executor_key`, which
+     * release it pins, and whether this node holds `CAN_AUTHOR_ON_BEHALF` on the
+     * owning group.
      * `canAuthorOnBehalf: false` comes back as an answer rather than an error, as
      * it is the default state of every context, so a caller can say "an admin of
      * `groupId` must grant it to `executorAccount`" instead of presenting a
      * warrant that will be refused after the author has spent a nonce on it.
      *
-     * `404` means the context belongs to no group, or this node holds no account
-     * yet; either way it can be named as no warrant's executor.
+     * `404` means the context belongs to no group, this node holds no account or
+     * identity in it yet, or its group names no release yet; no warrant can be
+     * spent here until that changes.
      *
      * For a caller with no credential on the node at all — a browser tab holding
      * one signing key — use `RelayClient`, which reads this same route on a node

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

@@ -375,6 +375,25 @@ export interface Namespace {
      * this is absent only on nodes that predate it.
      */
     founding?: NamespaceFounding;
+    /**
+     * Group ops this node logged but holds unapplied, because their group's
+     * history is sealed under a key it lacks: their effects are missing here until
+     * that key arrives. What explains a subgroup that looks stale on this node and
+     * current on another. Absent when nothing is held, and on nodes that predate it.
+     */
+    heldOps?: NamespaceHeldOps;
+}
+/** The group ops a namespace holds unapplied on the node that answered. */
+export interface NamespaceHeldOps {
+    ops: NamespaceHeldOp[];
+    /** Holds past the node's listing bound, counted but not listed. */
+    untracked: number;
+}
+export interface NamespaceHeldOp {
+    /** Hex id of the namespace op in the governance DAG. */
+    deltaId: string;
+    /** Hex id of the group whose sealed history it waits on. */
+    groupId: string;
 }
 /**
  * The founder and salt a namespace id was derived from:
@@ -475,10 +494,10 @@ export interface PerformIntentResponseData {
  * What a node says about running intents in one context — read before minting a
  * warrant, not after being refused one.
  *
- * Every input to a warrant is something the author already holds except two:
- * whose account and key go in `executor` and `executor_key`, and whether that
- * node may act here at all. Both belong to the node, so both are answered here,
- * on the path the intent will be presented to.
+ * Every input to a warrant is something the author already holds except three:
+ * whose account and key go in `executor` and `executor_key`, which release it
+ * pins, and whether that node may act here at all. The node knows them, so they
+ * are answered here, on the path the intent will be presented to.
  *
  * Reading it first is what lets a client fail before signing. A warrant spends a
  * nonce from a monotonic per-device sequence, and one naming the wrong executor
@@ -504,6 +523,14 @@ export interface IntentRelayInfo {
     canAuthorOnBehalf: boolean;
     /** The group whose admin must grant that capability, 64 hex. */
     groupId: string;
+    /**
+     * The blob id of the release that group names, 64 hex: what a warrant for this
+     * node must pin as `release_bytecode_id`. The route answers 404 while the group
+     * names no release.
+     */
+    releaseBytecodeId: string;
+    /** That release's semver, for the warrant's `release_version`. */
+    releaseVersion: string;
 }
 export interface NodeIdentity {
     /**