@tangle-network/agent-runtime 0.89.0 → 0.90.1

package/dist/{worktree-harness-CX_McRLp.d.ts → completion-gate-DkAnUmpb.d.ts}

@@ -1,48 +1,5 @@
-import { a as Executor } from './types-Driepl87.js';
-import { L as LocalHarness } from './local-harness-sI0S_XNA.js';
-
-/**
- *
- * The completion-oracle: **settled ⟺ DELIVERED.**
- *
- * Foreman's one hard lesson (0/18 self-improvement deliverables) — "done" must mean a check
- * PASSED, not the agent's say-so. `gateOnDeliverable` wraps an `Executor` so its settlement
- * is `valid` ONLY when the deliverable check passes. The child still RUNS and settles (its
- * spend is conserved into the pool either way), but a child that ran WITHOUT delivering
- * settles `valid:false` — so a keep-best driver never counts it as done, and a gate never
- * inflates with self-judged wins.
- *
- * Dual-purpose by construction:
- *  - product: the agent fleet only advances on real, checked deliverables.
- *  - proof: the gate's `valid` is the honest settle — equal-k comparisons can't be gamed by an
- *    arm that "ran" without producing the artifact.
- *
- * The check is a DEPLOYABLE oracle — a test command, a state verifier, the commit0 judge —
- * read off the child's output, never the model judging itself. A throwing check is
- * fail-closed (not delivered), never a crash.
- *
- * @experimental
- */
-
-/**
- * The deployable completion oracle passed to {@link gateOnDeliverable}: a `check` that
- * decides DELIVERED (settles `valid` ⟺ it resolves true) plus an optional `describe` of
- * what the spawn was supposed to produce. The check reads the child's output — never the
- * model judging itself.
- */
-interface DeliverableSpec<Out = unknown> {
-    /** The deployable check that decides DELIVERED. `settled.valid ⟺ this resolves true`. */
-    check: (out: Out) => boolean | Promise<boolean>;
-    /** What the spawn was supposed to produce — surfaced in traces/reports. */
-    describe?: string;
-}
-/**
- * Wrap an `Executor` so its settlement `valid` reflects the deliverable check, not the
- * inner verdict. Handles both `execute` shapes (one-shot `Promise<ExecutorResult>` and
- * streaming `AsyncIterable<UsageEvent>` + `resultArtifact()`); the check runs once the inner
- * executor has produced its output. The inner `score` is preserved; only `valid` is gated.
- */
-declare function gateOnDeliverable<Out>(inner: Executor<Out>, deliverable: DeliverableSpec<Out>): Executor<Out>;
+import { L as LocalHarness } from './local-harness-dcD5WTTr.js';
+import { c as Executor } from './types-eMNgWgFi.js';
 
 /**
  *
@@ -197,4 +154,47 @@ type WorktreeCheckRunner = (opts: {
     output: string;
 }>;
 
+/**
+ *
+ * The completion-oracle: **settled ⟺ DELIVERED.**
+ *
+ * Foreman's one hard lesson (0/18 self-improvement deliverables) — "done" must mean a check
+ * PASSED, not the agent's say-so. `gateOnDeliverable` wraps an `Executor` so its settlement
+ * is `valid` ONLY when the deliverable check passes. The child still RUNS and settles (its
+ * spend is conserved into the pool either way), but a child that ran WITHOUT delivering
+ * settles `valid:false` — so a keep-best driver never counts it as done, and a gate never
+ * inflates with self-judged wins.
+ *
+ * Dual-purpose by construction:
+ *  - product: the agent fleet only advances on real, checked deliverables.
+ *  - proof: the gate's `valid` is the honest settle — equal-k comparisons can't be gamed by an
+ *    arm that "ran" without producing the artifact.
+ *
+ * The check is a DEPLOYABLE oracle — a test command, a state verifier, the commit0 judge —
+ * read off the child's output, never the model judging itself. A throwing check is
+ * fail-closed (not delivered), never a crash.
+ *
+ * @experimental
+ */
+
+/**
+ * The deployable completion oracle passed to {@link gateOnDeliverable}: a `check` that
+ * decides DELIVERED (settles `valid` ⟺ it resolves true) plus an optional `describe` of
+ * what the spawn was supposed to produce. The check reads the child's output — never the
+ * model judging itself.
+ */
+interface DeliverableSpec<Out = unknown> {
+    /** The deployable check that decides DELIVERED. `settled.valid ⟺ this resolves true`. */
+    check: (out: Out) => boolean | Promise<boolean>;
+    /** What the spawn was supposed to produce — surfaced in traces/reports. */
+    describe?: string;
+}
+/**
+ * Wrap an `Executor` so its settlement `valid` reflects the deliverable check, not the
+ * inner verdict. Handles both `execute` shapes (one-shot `Promise<ExecutorResult>` and
+ * streaming `AsyncIterable<UsageEvent>` + `resultArtifact()`); the check runs once the inner
+ * executor has produced its output. The inner `score` is preserved; only `valid` is gated.
+ */
+declare function gateOnDeliverable<Out>(inner: Executor<Out>, deliverable: DeliverableSpec<Out>): Executor<Out>;
+
 export { type CreateWorktreeOptions as C, type DeliverableSpec as D, type GitRunner as G, type RemoveWorktreeOptions as R, type WorktreeHarnessResult as W, type WorktreeCheckRunner as a, type DiffOptions as b, type DiffResult as c, type WorktreeHandle as d, captureWorktreeDiff as e, createWorktree as f, type WorktreeCommandResult as g, gateOnDeliverable as h, removeWorktree as r };