lua-cli 3.32.3 → 3.32.5

package/dist/api-exports.d.ts

@@ -1360,9 +1360,11 @@ export declare type ChatMessage = TextMessage | ImageMessage | FileMessage;
 /**
  * A container arm: a `StepRef` — a `createStep` object, or a string naming an entry declared elsewhere in the chain
  * (`agentStep` / `specialistStep` / `toolStep` / `workflow`, and since LUA-684 `approval` / `waitForSignal`, so an
- * approval can run concurrently with another row) — or (B14 — lands with WF-509) the two-element chain
- * `[mapConfig, stepRef]`. A HITL arm takes the previous output as its payload, so it never heads a `[map, step]`
- * chain, and a `loop` body cannot be one until the engine proves it (`node-type-unsupported-in-container`).
+ * approval can run concurrently with another row) — or the two-element pair `[mapConfig, stepRef]`: the step runs
+ * with the map as its own `input` (LUA-780 — a `parallel` arm only; a `foreach` / `loop` body receives its item /
+ * the previous output and refuses the pair, `mapping-placement`, unless the target is a `.workflow()` node, whose
+ * `input` is the child run's). A HITL arm takes the previous output as its payload, so it never heads a
+ * `[map, step]` pair, and a `loop` body cannot be one until the engine proves it (`node-type-unsupported-in-container`).
  */
 export declare type ContainerArm = StepRef | [LuaMapConfig, StepRef];
 
@@ -7312,11 +7314,21 @@ declare interface WorkflowRun {
     parentRunId?: string;
     correlationKey?: string;
     tags?: string[];
+    /** R4 `gate` (02 §2.4). LUA-788: a `kind:'billing'` gate names the wallet's refusal (`code`), the held step and its expiry. */
     gate?: {
         kind: string;
         reason?: string;
-        since?: string;
+        since?: string | number;
+        code?: string;
+        stepId?: string;
+        expiresAt?: number;
     };
+    /**
+     * Server-decided (09 §9.6): `raise_budget` on a budget gate (LUA-665), `top_up` on a billing gate (LUA-788 — the
+     * wallet clears it; the engine re-checks and resumes on its own), `cancel_again` / `force` under a pending cancel,
+     * else `none`. Absent on an older server.
+     */
+    nextAction?: 'cancel_again' | 'force' | 'none' | 'raise_budget' | 'top_up';
     /**
      * The pending / audited cancel request (`runCancelView`): who asked and when; `wall` when it was the run wall's
      * own (LUA-686); LUA-704: `forcedBy` / `forcedAt` / `forceReason` on a forced terminal (`abandoned`, or