@sema-agent/core 7.15.0 → 7.17.0

package/dist/core/ask-unresolvable-notice.js

@@ -1,5 +1,15 @@
+export const ASK_UNRESOLVABLE_CAUSES = ["approver_unavailable", "no_approver_wired", "mandate_unreconstructible"];
+const ASK_UNRESOLVABLE_CAUSE_SET = new Set(ASK_UNRESOLVABLE_CAUSES);
+export function isAskUnresolvableCause(v) {
+    return ASK_UNRESOLVABLE_CAUSE_SET.has(v);
+}
+const CAUSE_CLAUSE = {
+    approver_unavailable: "the approver reported that nobody is reachable for this ask",
+    no_approver_wired: "no approver (or question face) is wired for this run — the headless posture",
+    mandate_unreconstructible: "an inherited durable-approval mandate binds this ask and this leg has no park facility to honor it",
+};
 export function askUnresolvableNotice(facts) {
-    const { sessionId, toolName, toolCallId, settlementKind, parkLaneExisted } = facts;
+    const { sessionId, toolName, toolCallId, cause, parkLaneExisted } = facts;
     if (typeof sessionId !== "string" || sessionId.length === 0) {
         throw new TypeError("delegation.ask_unresolvable: sessionId is required — a user-audience notice with no session routes nowhere");
     }
@@ -9,17 +19,15 @@ export function askUnresolvableNotice(facts) {
     if (typeof toolCallId !== "string" || toolCallId.length === 0) {
         throw new TypeError("delegation.ask_unresolvable: toolCallId is required");
     }
-    if (settlementKind !== "approver_unavailable") {
-        throw new TypeError(`delegation.ask_unresolvable: settlementKind ${JSON.stringify(settlementKind)} is not the unavailable settlement`);
+    if (!isAskUnresolvableCause(cause)) {
+        throw new TypeError(`delegation.ask_unresolvable: cause ${JSON.stringify(cause)} is not one of ${ASK_UNRESOLVABLE_CAUSES.join("/")}`);
     }
-    const park = parkLaneExisted
-        ? "the durable approval park did not take it"
-        : "no durable approval park is armed for this run";
+    const park = parkLaneExisted ? "the durable approval park did not take it" : "no durable approval park is armed for this run";
     return {
         code: "delegation.ask_unresolvable",
-        message: `approval for "${toolName}" could not be resolved: the approver reported that nobody is reachable for this ask and ${park} — ` +
+        message: `approval for "${toolName}" could not be resolved: ${CAUSE_CLAUSE[cause]} and ${park} — ` +
             `the call was denied fail-closed and did not run. To let such approvals wait for a person, run with a checkpoint store and a ` +
             `durable approval opt-in (or a live approver reachable for delegated children).`,
-        detail: { sessionId, toolName, toolCallId, settlementKind, parkLaneExisted: parkLaneExisted === true },
+        detail: { sessionId, toolName, toolCallId, cause, parkLaneExisted: parkLaneExisted === true },
     };
 }

package/dist/core/auto-compaction.d.ts

@@ -99,7 +99,7 @@ export interface CompactionForkContext {
     modelId?: string;
 }
 export interface MaybeCompactOptions {
-    /** RB-473 — disclosure channel for CONTAINED host-callback failures in this scope (the RB-463
+    /** Disclosure channel for CONTAINED host-callback failures in this scope (the RB-463
      *  isolation primitive's bounded first-failure per site). Absent ⇒ failures are counted only. */
     onNotifyError?: (failure: import("./safe-notify.js").SafeNotifyFailure) => void;
     /** The session to compact. Typed on the INTERFACE face (typecheck 车 2026-07-24): every member this
@@ -109,7 +109,7 @@ export interface MaybeCompactOptions {
      *  the compaction-boundary epoch restatement/advance must hash the SAME artifact identity as the
      *  prepare-time pin, or every compaction under a declaration-carrying run would flap the pin. */
     epochDeclaredSections?: import("../prompt-assembly/epoch.js").EpochDeclaredSections;
-    /** RB-31 (design/148 S2) — a compaction-boundary CENTER CANDIDATE ADOPTION, pre-assembled by the
+    /** A compaction-boundary CENTER CANDIDATE ADOPTION, pre-assembled by the
      *  caller (prepare's seam): the descriptor advances with the candidate's declarations + provenance
      *  in the SAME CAS append as the new baseline, and `apply()` (the live prefix/fingerprint swap)
      *  runs ONLY after that append succeeded — a failed/blocked compaction must swap nothing. */
@@ -160,7 +160,7 @@ export interface MaybeCompactOptions {
      *  including the preCompact hook's additions, gets the same treatment). */
     customInstructions?: string;
     /**
-     * #500 — the user's / project's own INSTRUCTION-FILE content (the CLAUDE.md family this
+     * The user's / project's own INSTRUCTION-FILE content (the CLAUDE.md family this
      * deployment loads into an ordinary session), for the INDEPENDENT summary form.
      *
      * Why it needs a seat at all: the summarization prompt carries CC's closing invitation to follow
@@ -300,7 +300,7 @@ export interface MaybeCompactOptions {
          */
         instructionSourcePaths?: ReadonlyArray<string>;
         /**
-         * RB-197②(独立复审 + 命中,已修): `recentlyReadFiles` yields CANONICAL keys (resolveKey
+         * `recentlyReadFiles` yields CANONICAL keys (resolveKey
          * output — the same coordinate `ReadFileState` is keyed in), but `instructionSourcePaths` and the
          * kept-tail scan inside `maybeCompact` (which reads raw tool-call arguments via
          * `extractFileOpsFromMessage`) do NOT share that coordinate — a model-typed relative path and its
@@ -315,7 +315,7 @@ export interface MaybeCompactOptions {
          */
         normalizePath?: (raw: string) => Promise<string>;
         /**
-         * RB-197②(交叉复审命中,已修) — a kept-tail Read tool-CALL's mere presence does not prove the
+         * A kept-tail Read tool-CALL's mere presence does not prove the
          * file's real content is visible there: its toolRESULT may be a dedup stub ("unchanged since you
          * last read it…") whose ORIGINAL full transmission sits in the summarized prefix THIS compaction is
          * about to cut away — preserving read-state for such a path would leave both the kept tail and the
@@ -328,14 +328,14 @@ export interface MaybeCompactOptions {
         isDedupStubResult?: (resultText: string) => boolean;
     };
     /**
-     * RB-197: fires ONCE per LANDED compaction (after `appendCompaction` committed the new baseline), with the
+     * Fires ONCE per LANDED compaction (after `appendCompaction` committed the new baseline), with the
      * files that were attached WHOLE (untruncated) into the summary. The Runner wires this to the read-state
      * invalidation (`applyCompactionToReadFileState`): the summary just replaced the history the read-dedup
      * stubs point at, so stale entries must drop and the re-attached content re-registers. Kept OUTSIDE
      * `workingFileAttachments` deliberately — the invalidation is owed even when attachments are disabled
      * (an empty array then). Best-effort: a throwing callback must not fail the landed compaction.
      *
-     * RB-197②(命中,已修;独立复审第二轮又命中一条同族缺口,已修) `preserveReadState`:
+     * `preserveReadState`:
      * canonical-coordinate paths (same shape as `normalizePath`'s output) whose read-state entry must
      * survive the compaction's clear even though they are NOT in `attachedComplete` — every file
      * `maybeCompact` deliberately skipped re-attaching, for EITHER exclusion reason (kept-tail-visible,
@@ -474,7 +474,7 @@ export interface MaybeCompactOptions {
         keptChars: number;
     }) => void;
     /**
-     * RB-402 — the design/36 ToolSearch activation set LIVE at this pass (the
+     * The design/36 ToolSearch activation set LIVE at this pass (the
      * runner threads `[...prepared.activeTools]` on all three lanes: boundary, PTL recovery, finish).
      * Persisted into the landed compaction entry's details (`CompactionDetails.activeTools`) so the
      * NEXT task boundary's re-derivation — whose transcript source (ToolSearch toolCall parts) this
@@ -510,7 +510,7 @@ export declare function maybeCompact(opts: MaybeCompactOptions): Promise<{
      *  (`enabled:false`) — the request can never be honored this run. Lets the caller resolve a manual
      *  /compact with the honest `"disabled"` outcome (and trace frame) instead of a structural noop. */
     disabled?: boolean;
-    /** RB-398-b: set (with `compacted:false`) when the pass PASSED the trigger gate
+    /** Set (with `compacted:false`) when the pass PASSED the trigger gate
      *  (natural or forced) but found nothing to summarize — no valid cut point / empty history. Was
      *  previously indistinguishable from the quiet under-threshold return, so a forced pass with
      *  nothing to do looked identical to one that never wanted to run; the caller's outcome event
@@ -597,7 +597,7 @@ export declare function maybeCompact(opts: MaybeCompactOptions): Promise<{
         modelId?: string;
     };
     /**
-     * RB-126 (2026-07-25): the trigger inputs THIS pass used, reported on
+     * The trigger inputs THIS pass used, reported on
      * EVERY return path — including the ordinary "nothing to do" one. A consumer rendering "how full is the
      * context" was otherwise forced to re-derive the numerator itself, and a re-derivation that drifts from
      * the engine's own is the projection-antipattern this repo keeps paying for: the displayed percentage

package/dist/core/auto-mode-arming.d.ts

@@ -29,7 +29,7 @@ export interface AutoModeArmingRecipe {
     /** Classify round-trip cap, ms. */
     timeoutMs?: number;
     /**
-     * #556 — the classifier DENIAL-LIMIT bounds (`RunnerDeps.autoMode.denialLimit`, CC 2.1.250 `FO`/`AKe`):
+     * The classifier DENIAL-LIMIT bounds (`RunnerDeps.autoMode.denialLimit`, CC 2.1.250 `FO`/`AKe`):
      * how many blocks the ancestor's classifier was allowed before a person had to look, and the window the
      * fallback ask ran under. A KNOB triple, not prompt body — every member is orderable, so the fold takes
      * the strictest of the two sides rather than refusing on a difference.
@@ -87,7 +87,7 @@ export interface AutoModeArmingFace {
     crossSessionMessagesRule?: boolean;
 }
 /**
- * #556 — the ONE tighten rule for the denial-limit bounds, shared by {@link foldAutoModeArming} and by
+ * The ONE tighten rule for the denial-limit bounds, shared by {@link foldAutoModeArming} and by
  * the runner's rebuilt-tracker mint (a second computation of "the strictest of these two" is how the
  * recipe's account and the tracker's actual bounds would come to disagree). Both sides' EFFECTIVE values
  * are materialized first (an omitted bound is the default the tracker applies, never "unbounded" — the

package/dist/core/background-agent-store.d.ts

@@ -104,18 +104,18 @@ export interface BackgroundAgentRecord {
     parkClaimId?: string;
     summary?: string;
     finalOutput?: string;
-    /** RB-205-B: the FULL result (workflow.ts NH-1 shape via {@link BackgroundAgentTaskHandle.resultFull}),
+    /** The FULL result (workflow.ts NH-1 shape via {@link BackgroundAgentTaskHandle.resultFull}),
      *  set only when it differs from `finalOutput` — the restart/durable-fallback poll path needs the same
      *  pairing the live handle carries, or a process restart loses the very recoverability this field exists
      *  to preserve. */
     finalOutputFull?: string;
     /** The child's failure text (registry `handle.error` mirror; the reap-stop sentinel never lands here).
-     *  RB-237: the stale-running reap flip ALSO writes its attribution here (`??`-guarded) —
+     *  The stale-running reap flip ALSO writes its attribution here (`??`-guarded) —
      *  `error` is the field the durable serving face renders (`serveDurableAgentRow`), while `summary`
      *  has no reader on that face, so an attribution written only to `summary` was invisible: a host
      *  crash read as a bare `failed` + "(no result text)". */
     error?: string;
-    /** RB-405 (durable archival mirror) — the classification triplet the in-memory handle carries under
+    /** The classification triplet the in-memory handle carries under
      *  the SAME names (`errorCode`/`errorRetryable`/`errorKind`; see RB-386②/RB-405 G3 on
      *  {@link import("./task-registry-shared.js").BackgroundAgentTaskHandle}), written to this row at the
      *  same terminal write that lands `error` — so a cross-restart fallback read
@@ -146,7 +146,7 @@ export interface BackgroundAgentRecord {
     rev: number;
 }
 /**
- * RB-423 — the terminal payload a REVIVAL must erase from the row it is re-launching, as ONE list.
+ * The terminal payload a REVIVAL must erase from the row it is re-launching, as ONE list.
  *
  * A revived handle starts a fresh cycle on an existing row: status flips back to `running`, but every
  * field describing how the PREVIOUS cycle ended is still sitting there. Left standing, each one
@@ -249,7 +249,7 @@ export declare function canAccessAgentRecord(record: Pick<BackgroundAgentRecord,
  *   terminal-looking row whose rev the flush has not yet bumped. In-process sweeps are gated on the
  *   live handle; cross-process revival (S3) must claim-CAS FIRST (see {@link BackgroundAgentRecord.writerId}).
  */
-/** RB-237: the stale-running reap flip's attribution, written to BOTH `summary` (legacy
+/** The stale-running reap flip's attribution, written to BOTH `summary` (legacy
  *  slot, kept for any out-of-repo reader) and `error` (the field {@link canAccessAgentRecord}-gated
  *  durable serving actually renders). One exported constant so the two store implementations (in-memory
  *  here, file twin) can never drift apart (RB-74/RB-111 family). Wording carries CC 2.1.220's three

package/dist/core/background-shell.d.ts

@@ -133,7 +133,7 @@ export interface BackgroundShellCapability {
  */
 export declare function hasBackgroundShell(env: ExecutionEnv): env is ExecutionEnv & BackgroundShellCapability;
 /**
- * RB-164 — the ONE way core runs an env-level background sweep.
+ * The ONE way core runs an env-level background sweep.
  *
  * ## Why a single entry point
  * `disposeBackgroundShells` lives in the execution-env layer and cannot reach the task registry, so the

package/dist/core/checkpoint-execution-record.d.ts

@@ -24,9 +24,6 @@ import type { GateOutcome } from "./gate-outcome.js";
  */
 export declare const EXECUTION_OUTCOME_RECORD_WORDS: readonly ["recorded", "already_recorded", "not_resolved", "absent"];
 export type ExecutionOutcomeRecordWord = (typeof EXECUTION_OUTCOME_RECORD_WORDS)[number];
-/** Membership test for {@link ExecutionOutcomeRecordWord} — a deployment store answers across a process
- *  boundary, so the consumer validating its word must not hand-roll the set. */
-export declare function isExecutionOutcomeRecordWord(v: unknown): v is ExecutionOutcomeRecordWord;
 /**
  * The one disposition table over {@link ExecutionOutcomeRecordWord}: does this answer mean the row now
  * carries NO execution record — i.e. the leg's disposition of the decided action is not on file? The

package/dist/core/checkpoint-execution-record.js

@@ -1,9 +1,5 @@
 import {} from "./ask-origin.js";
 export const EXECUTION_OUTCOME_RECORD_WORDS = ["recorded", "already_recorded", "not_resolved", "absent"];
-const EXECUTION_OUTCOME_RECORD_WORD_SET = new Set(EXECUTION_OUTCOME_RECORD_WORDS);
-export function isExecutionOutcomeRecordWord(v) {
-    return EXECUTION_OUTCOME_RECORD_WORD_SET.has(v);
-}
 export const EXECUTION_RECORD_LEAVES_ROW_UNRECORDED = {
     recorded: false,
     already_recorded: false,