niceeval 0.13.1 → 0.13.2

package/dist/runner/sandbox-pool.d.ts

@@ -37,7 +37,16 @@ export declare class ReusableSandboxPool {
     private readonly waiters;
     private creating;
     private stopped;
+    /** One physical stop operation owns every instance/finalizer exactly once. */
+    private stopCompletion;
     private readonly runtimeFailures;
+    /**
+     * Whole-Experiment physical cleanup ledger. This is intentionally distinct
+     * from `runtimeFailures`: the latter is a per-Attempt diagnostic channel and
+     * is drained once that Attempt seals, whereas this collection is replayed by
+     * the terminal `stop()` even if an entry was retired long before then.
+     */
+    private readonly cleanupFailures;
     /** Provider 可观察的物理 owner；Group 池不能随首个未携入成员改用另一个 Eval ID。 */
     private readonly materializationOwnerId;
     /** 本次 Run 内的 Sandbox 编号计数器;淘汰的实例不让号,编号在结果里永远指向同一个实例。 */
@@ -48,8 +57,15 @@ export declare class ReusableSandboxPool {
     constructor(plan: Extract<LinkedRunPlan, {
         readonly _tag: "Sandbox";
     }>, capacity: number, feedback: ScopedFeedback, setupContext: SandboxHookContext, runtimeServices?: SandboxRuntimeServices, agent?: SandboxAgent | undefined, runTiming?: import("./timing.js").RunTimingRecorder | undefined, materializationOwnerId?: string, nextReuseSandboxNumber?: (() => number) | undefined, groupPlugins?: readonly LinkedPluginLifecycle[], groupPluginContext?: GroupPluginContext | undefined);
-    /** 把整座池登记进调用方 Scope；Invocation 中断与正常结束走同一条 stop finalizer。 */
+    /**
+     * Registers only an awaiter in the outer Invocation Scope. The real stop is
+     * initiated by the Experiment lifecycle before its teardown; if the outer
+     * Scope closes first it joins the same single-flight result rather than
+     * repeating provider or plugin finalizers.
+     */
     managed(): Effect.Effect<this, never, Scope.Scope>;
+    /** Closes admission before the Experiment starts physical cleanup. */
+    freeze(): Effect.Effect<void>;
     /**
      * @param attemptDeadlineMs 这条 Attempt 实际生效的超时上限(解析链见 runner/timeout.ts)。
      * `undefined` = 四层都没声明上限:请求的寿命只能覆盖收尾预留——Attempt 本身没有 deadline,
@@ -57,7 +73,8 @@ export declare class ReusableSandboxPool {
      * 就是「不声明上限」的代价(两种时间的分界见 docs/feature/sandbox/reuse.md)。
      */
     acquire(attemptDeadlineMs: number | undefined, buildLocators: ReadonlyMap<BuildKey, JsonValue>): Effect.Effect<ReusableSandboxLease, Error | import("../sandbox/runtime.js").SandboxRuntimeMaterializationError, Scope.Scope>;
-    stop(): Effect.Effect<void>;
+    stop(): Effect.Effect<void, unknown>;
+    private stopAll;
     /** Drained by the scheduler after the lease Scope sealed the prior result. */
     drainRuntimeFailures(): readonly ReusableSandboxPoolRuntimeFailure[];
     private create;
@@ -67,4 +84,19 @@ export declare class ReusableSandboxPool {
     private retire;
     private wake;
     private awaitWake;
+    /**
+     * A create/ensureLifetime failure can still run provider and Sandbox Scope
+     * finalizers. The entry is not yet in `entries`, so `stopAll()` cannot find
+     * it later; record a close failure now and replay it from the Experiment
+     * lifetime ledger instead of letting an `onError` cleanup failure vanish.
+     */
+    private closeFailedCreateScope;
+    private recordCleanupFailure;
+    /**
+     * `materializeSandboxRunPlan` deliberately converts hook/provider cleanup
+     * failures into feedback and continues its Scope.close. Preserve that signal
+     * beside thrown Scope close failures, without changing the public Sandbox
+     * lifecycle API or its diagnostic-only finalizer contract.
+     */
+    private lifecycleFeedback;
 }