@terminal3/t3n-sdk 5.26.0 → 5.27.0

package/dist/index.d.ts

@@ -2533,8 +2533,20 @@ interface AuditBatch {
      * commit? `false` means the call rolled back or trapped, so an event's
      * `outcome: "success"` in this batch is the contract's *claim*, not a
      * committed fact — filter on this when you need only durable events.
+     * This holds for approval events too (`details.event_type` is
+     * `action.escalated`, `action.reviewed` or `action.executed`): a
+     * rolled-back approver batch can list `action.reviewed` as `success` next
+     * to a failed `action.executed`, so always check `committed`. Events in a
+     * batch share one timestamp and are ordered by their position in `events`.
      */
     committed: boolean;
+    /**
+     * Present when the platform, not a client, started this dispatch, for
+     * example `"hitl-resume:<run id>"` for a call resumed after a human
+     * approval. Absent for a client call. The id after the prefix may itself
+     * contain colons, so do not split on them.
+     */
+    origin?: string;
     events: AuditEvent[];
 }
 /**
@@ -2634,6 +2646,14 @@ interface ActivityEntry {
      * validated one.
      */
     roles?: string[];
+    /**
+     * Present when the node, not the caller, started the call, for example
+     * `"hitl-resume:<run id>"` for the call the node ran as the requester
+     * once an approval was granted. Stamped by the node, never by a contract.
+     * Absent when the caller started the call. The id after the prefix may
+     * itself contain colons, so do not split on them.
+     */
+    origin?: string;
     /**
      * Labels the contract chose for this call — the `custom` object it returned
      * in its response, which the node removes from the response and stores on