comisai 1.0.45 → 1.0.46

package/node_modules/@comis/agent/dist/executor/tool-deferral.js

@@ -1,8 +1,7 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * Unified tool deferral engine: replaces the MCP-only applyMcpToolDeferral()
- * with rule-based, budget-based, and small-model deferral, plus BM25-scored
- * discover_tools for searching deferred tools.
+ * Unified tool deferral engine: rule-based, budget-based, and small-model
+ * deferral, plus BM25-scored discover_tools for searching deferred tools.
  *
  * Deferral model (exclude model): Deferred tools are removed from the tools
  * parameter entirely and partitioned into a DeferredToolEntry list. A
@@ -10,7 +9,7 @@
  * LLM to search and fetch full schemas on demand. Discovered tools (tracked
  * via DiscoveryTracker) are re-included in the active context with their
  * original schemas. This achieves ~81% token savings for 100 tools compared
- * to the previous description-swap (pre-register) model.
+ * to shipping every full schema inline.
  *
  * @module
  */
@@ -94,8 +93,8 @@ export const CORE_TOOLS = new Set([
     "web_search", "web_fetch",
 ]);
 /**
- * CWF-04 (Phase 168): orchestration entry primitives that stay active for `small`-class
- * models even under the SD7 tool-ceiling. Only `small` — nano's aggressive CORE_TOOLS-only
+ * Orchestration entry primitives that stay active for `small`-class
+ * models even under the active-tool ceiling. Only `small` — nano's aggressive CORE_TOOLS-only
  * path fires before the ceiling block, so nano retains its own deliberate policy (nano is
  * below the NL→DAG comprehension cliff; promoting pipeline for nano gives it a tool it
  * cannot use and needlessly expands its manifest). frontier/mid: ceiling never fires.
@@ -106,12 +105,11 @@ export const CORE_TOOLS = new Set([
  * pipeline schema ~6052 chars ÷ 3.5 = ~1729 tokens.
  *
  * Pre-deferral systemTokens estimate (cachedSystemTokensEstimate) remains stale for the
- * CURRENT turn (it's computed before deferral fires) — this is a pre-existing known
- * subtlety (Pitfall 4), not introduced by Phase 168. Budget algebra will accurately reflect
- * the post-ceiling manifest on the NEXT assembly.
+ * CURRENT turn (it's computed before deferral fires) — a known subtlety. Budget algebra
+ * will accurately reflect the post-ceiling manifest on the NEXT assembly.
  *
- * Extend only when O2 DAG templates demand it (future milestone); never add all four
- * orchestration primitives — each extra schema fights the ceiling this fix pursues.
+ * Extend only when DAG templates demand it; never add all four orchestration
+ * primitives — each extra schema fights the ceiling this set exists to protect.
  *
  * Exported for test access (mirrors the `CORE_TOOLS` convention); no non-test external
  * caller currently consumes this constant.
@@ -180,7 +178,7 @@ export function extractRecentlyUsedToolNames(messages, lookbackCount = 20) {
 export function resolveToolDescription(tool) {
     const entry = LEAN_TOOL_DESCRIPTIONS[tool.name];
     if (typeof entry === "function") {
-        // WR-01 / TODO(Phase-152): pass capabilityClass when small-model lean
+        // TODO: pass capabilityClass when small-model lean
         // descriptions are introduced. Until then, "large" is the correct safe
         // default — it produces the same output as the current behavior, and
         // DeferralContext.capabilityClass is not threaded to this function yet.
@@ -212,7 +210,7 @@ export function resolveToolDescription(tool) {
  * Anthropic regex tool. Naming the tool explicitly gives the model a
  * concrete next step.
  *
- * C3 (Plan 152-04): optional `maxEntries` cap truncates the formatted list
+ * The optional `maxEntries` cap truncates the formatted list
  * and appends a "[+N more deferred tools — use discover_tools to list all]"
  * suffix. Frontier/mid: uncapped (options undefined or {}). Small/nano: caller
  * passes `{ maxEntries: DEFERRED_TOOLS_MAX_BY_CLASS[capabilityClass] }`.
@@ -225,7 +223,7 @@ export function resolveToolDescription(tool) {
 export function buildDeferredToolsContext(entries, options) {
     if (entries.length === 0)
         return "";
-    // C3: apply maxEntries cap before formatting
+    // Apply the maxEntries cap before formatting
     const maxEntries = options?.maxEntries;
     let effectiveEntries = entries;
     let truncatedCount = 0;
@@ -258,7 +256,7 @@ export function buildDeferredToolsContext(entries, options) {
         const shortNames = tools.map(t => t.name.startsWith(prefix) ? t.name.slice(prefix.length) : t.name);
         lines.push(`[${server}] (${tools.length} tools): ${shortNames.join(", ")}`);
     }
-    // C3: append truncation notice when entries were capped
+    // Append a truncation notice when entries were capped
     if (truncatedCount > 0) {
         lines.push(`[+${truncatedCount} more deferred tools — use discover_tools to list all]`);
     }
@@ -325,9 +323,9 @@ export function applyToolDeferral(tools, _contextWindow, deferralContext, logger
     // the most constrained models). Providers without mid-turn injection (OpenAI,
     // xAI, etc.) were already exempt from MCP deferral and remain so -- the
     // flip means the Anthropic/Google branch now matches their behavior.
-    // Aggressive deferral for nano-class models (behavior-neutral: old modelTier="small" at <=32K maps to capabilityClass="nano")
-    // Phase 159/SD7: 'small' class ceiling policy implemented via DeferralContext.activeToolCeiling.
-    // nano retains its own aggressive CORE_TOOLS-only path below.
+    // Aggressive deferral for nano-class models. The 'small' class ceiling policy
+    // is implemented via DeferralContext.activeToolCeiling; nano retains its own
+    // aggressive CORE_TOOLS-only path here.
     if (deferralContext.capabilityClass === "nano") {
         for (const t of tools) {
             if (!deferredSet.has(t.name) && !CORE_TOOLS.has(t.name) && !deferralContext.recentlyUsedToolNames.has(t.name)) {
@@ -335,9 +333,9 @@ export function applyToolDeferral(tools, _contextWindow, deferralContext, logger
             }
         }
     }
-    // SD7 (Phase 159): active-tool ceiling for small class (fills Phase-152/SD7 deferred TODO).
-    // Only fires when DeferralContext.activeToolCeiling is set — undefined guard preserves
-    // the Phase-151 regression test (makeContext without activeToolCeiling → skipped).
+    // Active-tool ceiling for the small capability class.
+    // Only fires when DeferralContext.activeToolCeiling is set — undefined means
+    // no ceiling (a DeferralContext without activeToolCeiling skips this pass).
     // CRITICAL: mirrors the nano path — CORE_TOOLS and recently-used tools are NEVER deferred.
     // Deferred tools remain fully reachable via discover_tools (no capability removal).
     if (deferralContext.activeToolCeiling !== undefined) {
@@ -352,12 +350,12 @@ export function applyToolDeferral(tools, _contextWindow, deferralContext, logger
                     continue;
                 if (CORE_TOOLS.has(t.name))
                     continue;
-                // CWF-04 (Phase 168): pipeline (and future orchestration entries) stays active for
+                // pipeline (and future orchestration entries) stays active for
                 // small-class models. Only fires in this ceiling block — which only runs for small
                 // (activeToolCeiling is undefined for nano/frontier/mid). The capabilityClass check
                 // is technically redundant (the block only runs for small) but makes the SMALL-ONLY
-                // intent unambiguous. Nano's aggressive path above is unaffected — nano stays
-                // byte-identical (pipeline still deferred for nano, test :485 GREEN).
+                // intent unambiguous. Nano's aggressive path above is unaffected — pipeline is
+                // still deferred for nano.
                 if (deferralContext.capabilityClass === "small" && SMALL_CLASS_ORCHESTRATION_TOOLS.has(t.name))
                     continue;
                 if (deferralContext.recentlyUsedToolNames.has(t.name))
@@ -450,7 +448,7 @@ export function applyToolDeferral(tools, _contextWindow, deferralContext, logger
  *  term). ONE ceil over the summed chars. */
 function toolCorpusTokens(tools) {
     // tool name + description + JSON.stringify(parameters) is machine-emitted Latin
-    // flat-by-design: JSON (scriptTokenFactor 1.0) — mirrors estimateSystemTokensFactored's toolOverheadChars (TOK-01)
+    // flat-by-design: JSON (scriptTokenFactor 1.0) — mirrors estimateSystemTokensFactored's toolOverheadChars
     return Math.ceil(toolDefOverheadChars(tools) / CHARS_PER_TOKEN_RATIO);
 }
 /**
@@ -523,7 +521,7 @@ export function computeWindowFitBudget(params) {
  */
 export function enforceToolBudgetFit(params) {
     const { activeTools, deferredEntries, systemPromptText, contextWindow, outputHeadroom, messageFloorTokens, coreToolNames, recentlyUsedToolNames, discoverToolName, logger, } = params;
-    // TOK-01: the system-prompt term divides chars by the SAME script factor as
+    // The system-prompt term divides chars by the SAME script factor as
     // estimateSystemTokensFactored (a dense Hebrew/CJK prompt carries ~2-3× tokens
     // per char) so the residual budget is not over-stated for non-Latin prompts —
     // under-counting here would let tools through that then overflow the window.
@@ -773,8 +771,8 @@ const DEFAULT_TOOL_DISCOVERY_SCORES = {
  * BM25 scores are normalized to [0, 1] (fraction of top match) BEFORE the
  * score-floor filter applies, matching the semantics of hybrid-mode scoring.
  * This ensures the top match always clears any floor <= 1.0 whenever any
- * positive signal exists (fixes the srv1593437 08:06:39Z "install MCP"
- * regression where raw BM25 ~0.74 was dropped by the 0.8 raw-score floor).
+ * positive signal exists (fixes a live regression where an "install MCP"
+ * query's raw BM25 ~0.74 was dropped by the 0.8 raw-score floor).
  *
  * @param scoreConfig Optional score-floor override (defaults to 0.8 BM25 /
  *   0.35 hybrid). Zero or negative floors disable the filter.
@@ -1113,7 +1111,7 @@ export function createAutoDiscoveryStubs(deferredEntries, discoveryTracker, logg
             name: entry.name,
             label: originalLabel ?? entry.name,
             description: entry.description,
-            // ROOT-CAUSE context-exhaustion fix (2026-06-22 VPS gpt-5.3-codex): the stub
+            // ROOT-CAUSE context-exhaustion fix (observed live with gpt-5.3-codex): the stub
             // carries a MINIMAL placeholder schema, NOT entry.original.parameters (the
             // full ~195-tok schema). The stub exists ONLY so the SDK's agent-loop
             // RESOLVES the deferred tool's NAME (prevents "Tool X not found" when a skill

package/node_modules/@comis/agent/dist/executor/tool-overhead.d.ts

@@ -1,14 +1,14 @@
 /**
  * The tool-schema char-overhead reduce — extracted from executor-tool-assembly.ts
- * so the turn-time S estimate and the FLOOR-01 boot floor share ONE function
- * (I8/R-3; the extraction IS the drift pin).
+ * so the turn-time S estimate and the boot-time viable floor share ONE function
+ * (the extraction IS the drift pin).
  *
  * Consumers:
  *   - executor-tool-assembly.ts: cachedSystemTokensEstimate (the turn-time S term)
- *   - context-engine/viable-floor.ts: toolSchemaTokens (the FLOOR-01 boot term)
+ *   - context-engine/viable-floor.ts: toolSchemaTokens (the boot-floor term)
  *
  * viable-floor.test.ts pins both sites to this single export by FUNCTION-REFERENCE
- * IDENTITY (FLOOR-01-13) — a re-derived copy at either site cannot pass.
+ * IDENTITY — a re-derived copy at either site cannot pass.
  *
  * @module
  */
@@ -35,16 +35,16 @@ export interface ToolOverheadInput {
 /**
  * Sum of name + description + JSON.stringify(parameters) lengths across the
  * toolset — the char-size basis for the system-token estimate (S) at turn time
- * and for the FLOOR-01 toolSchemaTokens term at boot.
+ * and for the viable-floor toolSchemaTokens term at boot.
  *
- * ROOT-CAUSE context-exhaustion fix (2026-06-22 VPS gpt-5.3-codex): auto-discovery
+ * ROOT-CAUSE context-exhaustion fix (observed live with gpt-5.3-codex): auto-discovery
  * STUBS (those carrying DEFERRAL_STUB_MARKER_KEY) are EXCLUDED. The fit pass defers
  * ~50 of 65 tools, then createAutoDiscoveryStubs pushes a stub per deferred tool
  * into mergedCustomTools so the SDK can resolve their names; createStubFilterInjector
  * strips those stubs from the WIRE (zero request cost). Counting them here made every
  * S estimate over the full mergedCustomTools balloon back to ~all-65-tools size, so
  * the pre-flight saw assembled ≈ 13.7K > the 8192 window and FALSE-exhausted — silently
- * negating the deferral. Skipping marked stubs makes the estimate match the wire (the
- * lead's "skip stubs in toolDefOverheadChars" fix). Non-stub tools are byte-identical.
+ * negating the deferral. Skipping marked stubs makes the estimate match the wire.
+ * Non-stub tools are byte-identical.
  */
 export declare function toolDefOverheadChars(tools: ReadonlyArray<ToolOverheadInput>): number;

package/node_modules/@comis/agent/dist/executor/tool-overhead.js

@@ -1,15 +1,15 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
  * The tool-schema char-overhead reduce — extracted from executor-tool-assembly.ts
- * so the turn-time S estimate and the FLOOR-01 boot floor share ONE function
- * (I8/R-3; the extraction IS the drift pin).
+ * so the turn-time S estimate and the boot-time viable floor share ONE function
+ * (the extraction IS the drift pin).
  *
  * Consumers:
  *   - executor-tool-assembly.ts: cachedSystemTokensEstimate (the turn-time S term)
- *   - context-engine/viable-floor.ts: toolSchemaTokens (the FLOOR-01 boot term)
+ *   - context-engine/viable-floor.ts: toolSchemaTokens (the boot-floor term)
  *
  * viable-floor.test.ts pins both sites to this single export by FUNCTION-REFERENCE
- * IDENTITY (FLOOR-01-13) — a re-derived copy at either site cannot pass.
+ * IDENTITY — a re-derived copy at either site cannot pass.
  *
  * @module
  */
@@ -25,17 +25,17 @@ export const DEFERRAL_STUB_MARKER_KEY = "__comis_deferral_stub__";
 /**
  * Sum of name + description + JSON.stringify(parameters) lengths across the
  * toolset — the char-size basis for the system-token estimate (S) at turn time
- * and for the FLOOR-01 toolSchemaTokens term at boot.
+ * and for the viable-floor toolSchemaTokens term at boot.
  *
- * ROOT-CAUSE context-exhaustion fix (2026-06-22 VPS gpt-5.3-codex): auto-discovery
+ * ROOT-CAUSE context-exhaustion fix (observed live with gpt-5.3-codex): auto-discovery
  * STUBS (those carrying DEFERRAL_STUB_MARKER_KEY) are EXCLUDED. The fit pass defers
  * ~50 of 65 tools, then createAutoDiscoveryStubs pushes a stub per deferred tool
  * into mergedCustomTools so the SDK can resolve their names; createStubFilterInjector
  * strips those stubs from the WIRE (zero request cost). Counting them here made every
  * S estimate over the full mergedCustomTools balloon back to ~all-65-tools size, so
  * the pre-flight saw assembled ≈ 13.7K > the 8192 window and FALSE-exhausted — silently
- * negating the deferral. Skipping marked stubs makes the estimate match the wire (the
- * lead's "skip stubs in toolDefOverheadChars" fix). Non-stub tools are byte-identical.
+ * negating the deferral. Skipping marked stubs makes the estimate match the wire.
+ * Non-stub tools are byte-identical.
  */
 export function toolDefOverheadChars(tools) {
     return tools.reduce((sum, t) => {

package/node_modules/@comis/agent/dist/executor/tool-parallelism.d.ts

@@ -56,9 +56,9 @@ export declare function createMutationSerializer(): (tools: ToolDefinition[]) =>
  * `execute()` promises resolve in COMPLETION order — which is
  * nondeterministic across turns. If concurrent results were placed into the
  * message array in completion order, the cached prompt prefix would change
- * turn-over-turn and bust the prompt cache (T-221-STREAM-01, a cost DoS).
+ * turn-over-turn and bust the prompt cache (a cost DoS).
  *
- * SDK-side guarantee (Q-STREAM-1 spike, @earendil-works/pi-coding-agent
+ * SDK-side guarantee (verified against @earendil-works/pi-coding-agent
  * 0.79.3): the SDK already "appends persisted tool results in assistant
  * source order" (CHANGELOG #3503) regardless of which tool finishes first,
  * and `createMutationSerializer` above wraps `execute()` WITHOUT reordering

package/node_modules/@comis/agent/dist/executor/tool-parallelism.js

@@ -1,5 +1,5 @@
 // SPDX-License-Identifier: Apache-2.0
-// @allow-throw: createOrderPreservingResultBuffer (221-05) invariant guards — RangeError on a non-negative-integer toolCallCount / out-of-range record index; Error on duplicate-fill or incomplete-flush (a hole would tear the cache-stable prefix). These are programmer-error fail-fast guards on the buffer's contract (it is called once-per-index by construction by the executor loop), not recoverable runtime conditions; consumed on the executor tool-parallelism path.
+// @allow-throw: createOrderPreservingResultBuffer invariant guards — RangeError on a non-negative-integer toolCallCount / out-of-range record index; Error on duplicate-fill or incomplete-flush (a hole would tear the cache-stable prefix). These are programmer-error fail-fast guards on the buffer's contract (it is called once-per-index by construction by the executor loop), not recoverable runtime conditions; consumed on the executor tool-parallelism path.
 /**
  * Tool Parallelism: Read-only classifier and mutation serializer.
  *

package/node_modules/@comis/agent/dist/executor/turn-loop-detector.d.ts

@@ -1,5 +1,6 @@
 /**
- * Per-execution turn-loop detector (FIX #2 — the durable platform guard).
+ * Per-execution turn-loop detector — the durable platform guard against
+ * runaway tool-call loops.
  *
  * Root-cause incident: a model issued ~150 identical reads of the same four
  * already-inlined workspace files in one turn, hit maxSteps, and aborted. This
@@ -14,8 +15,8 @@
  *
  * Safety: caching is an explicit ALLOWLIST of idempotent read-only tools. Any
  * tool NOT in the allowlist is treated as a side-effecting mutation — it is
- * never cached or short-circuited (T-hbe-03: a stale "success" for a write
- * would be a tampering bug), and it INVALIDATES the read cache so a read after
+ * never cached or short-circuited (a stale "success" for a write would be a
+ * tampering bug), and it INVALIDATES the read cache so a read after
  * a write of the same path really re-executes.
  *
  * State is closure-local (one instance per execution run) — NO module-level

package/node_modules/@comis/agent/dist/executor/turn-loop-detector.js

@@ -1,6 +1,7 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * Per-execution turn-loop detector (FIX #2 — the durable platform guard).
+ * Per-execution turn-loop detector — the durable platform guard against
+ * runaway tool-call loops.
  *
  * Root-cause incident: a model issued ~150 identical reads of the same four
  * already-inlined workspace files in one turn, hit maxSteps, and aborted. This
@@ -15,8 +16,8 @@
  *
  * Safety: caching is an explicit ALLOWLIST of idempotent read-only tools. Any
  * tool NOT in the allowlist is treated as a side-effecting mutation — it is
- * never cached or short-circuited (T-hbe-03: a stale "success" for a write
- * would be a tampering bug), and it INVALIDATES the read cache so a read after
+ * never cached or short-circuited (a stale "success" for a write would be a
+ * tampering bug), and it INVALIDATES the read cache so a read after
  * a write of the same path really re-executes.
  *
  * State is closure-local (one instance per execution run) — NO module-level
@@ -68,7 +69,7 @@ function cacheKey(toolName, args) {
     return `${toolName}::${canonicalize(args)}`;
 }
 /**
- * True when a tool result represents a FAILURE / blocked call (F-15). The canonical
+ * True when a tool result represents a FAILURE / blocked call. The canonical
  * signal is `isError: true`; we also catch content-gate / sandbox rejections that
  * surface a marker but may not set the flag. A failed mutation makes NO progress —
  * a small model looping on a doomed tool (e.g. exec repeatedly content-gate-rejected,
@@ -118,7 +119,7 @@ export function createTurnLoopDetector() {
             if (!isIdempotentRead(toolName)) {
                 // Mutation: invalidate the read cache (write-between-reads forces a real
                 // re-execution of the next read). A SUCCESSFUL mutation is genuine progress
-                // (reset). A FAILED/blocked mutation is NOT progress (F-15): count it so a
+                // (reset). A FAILED/blocked mutation is NOT progress: count it so a
                 // model looping on a doomed tool trips the loop guard and degrades honestly
                 // instead of running to makespan.
                 readCache.clear();

package/node_modules/@comis/agent/dist/executor/types.d.ts

@@ -13,6 +13,9 @@ import type { TimeoutSource } from "../model/operation-model-resolver.js";
 export interface ExecutionResult {
     response: string;
     sessionKey: SessionKey;
+    /** PER-EXECUTION token totals (the bridge's accumulation for THIS execute()
+     *  call) — scope-consistent with `cost`. For the session-cumulative total
+     *  (across every execution on the persisted session) read `sessionTokensUsed`. */
     tokensUsed: {
         input: number;
         output: number;
@@ -20,6 +23,18 @@ export interface ExecutionResult {
         cacheRead?: number;
         cacheWrite?: number;
     };
+    /** SDK CUMULATIVE session token totals (all executions on the persisted
+     *  session) — the `/status` / session-inspect view. Absent when the SDK
+     *  reported no stats (e.g. an abort before any LLM call). Distinct from the
+     *  per-execution `tokensUsed` so a per-execution log line / obs row never
+     *  reports a session-cumulative token count beside a per-execution cost. */
+    sessionTokensUsed?: {
+        input: number;
+        output: number;
+        total: number;
+        cacheRead?: number;
+        cacheWrite?: number;
+    };
     cost: {
         total: number;
         cacheSaved?: number;
@@ -27,17 +42,17 @@ export interface ExecutionResult {
         ghostCostUsd?: number;
         /** Number of API requests that timed out. */
         timedOutRequests?: number;
-        /** 1.3: Session-cumulative total cost across all turns (USD). */
-        sessionCostUsd?: number;
-        /** 1.3: Session-cumulative cache savings across all turns (USD). */
-        sessionCacheSavedUsd?: number;
+        /** Session-cumulative total cost across all turns (USD). */
+        executionCostUsd?: number;
+        /** Session-cumulative cache savings across all turns (USD). */
+        executionCacheSavedUsd?: number;
     };
     stepsExecuted: number;
     llmCalls: number;
     finishReason: "stop" | "max_steps" | "budget_exceeded" | "budget_exhausted" | "circuit_open" | "provider_degraded" | "context_loop" | "context_exhausted" | "output_starved" | "session_reset" | "loop_detected" | "prompt_timeout" | "spend_exceeded" | "error";
     /** Ordered list of tool names invoked during execution (for post-mortem analysis). */
     toolCallHistory?: string[];
-    /** Issue-4 narrate-without-emit nudge outcome (small/nano only). A fired-but-
+    /** Narrate-without-emit nudge outcome (small/nano only). A fired-but-
      *  unrecovered nudge promotes the clean would-be terminal to the named
      *  degraded cause `narration_stall` at the post-execution chokepoint. */
     narrateNudge?: {
@@ -68,9 +83,9 @@ export interface ExecutionResult {
         stopReason: string;
     };
     /** Silent Execution Planner metrics (undefined if SEP inactive).
-     *  SEP is observability-only post-L4: plan extraction + step counting
-     *  remain; the legacy enforcement nudge was replaced by the post-batch
-     *  continuation handler. */
+     *  SEP is observability-only: plan extraction + step counting
+     *  remain; enforcement is handled by the post-batch continuation
+     *  handler, not an SEP nudge. */
     plannerMetrics?: {
         stepsPlanned: number;
         stepsCompleted: number;
@@ -90,7 +105,7 @@ export interface ExecutionOverrides {
     /** Override the shared StepCounter with a fresh instance.
      *  When provided, this counter is used instead of the deps.stepCounter. */
     stepCounter?: StepCounter;
-    /** Per-execution token cap for sub-agent isolation (BUDGET-01).
+    /** Per-execution token cap for sub-agent isolation.
      *  Fed to budgetGuard.resetExecution(cap); checkBudget enforces
      *  min(config.perExecution, tokenBudget) so a runaway child is stopped
      *  mid-run. Absent ⇒ resetExecution() with no cap (config.perExecution). */
@@ -117,9 +132,9 @@ export interface ExecutionOverrides {
     skipSep?: boolean;
     /** Per-operation prompt timeout override. When set, shadows config.promptTimeout for ALL LLM calls in this execution.
      *  `source` labels which resolution level produced promptTimeoutMs — carried,
-     *  never re-derived (LAT-01: the cron producer materializes this object
+     *  never re-derived (the cron producer materializes this object
      *  unconditionally, so the label cannot be inferred at decode). Absent ⇒
-     *  legacy producer ⇒ treated as operation_explicit at decode. */
+     *  treated as operation_explicit at decode. */
     promptTimeout?: {
         promptTimeoutMs?: number;
         retryPromptTimeoutMs?: number;
@@ -137,12 +152,12 @@ export interface ExecutionOverrides {
      *  agents where all tools are reachable. */
     activeToolGroups?: string[];
     /**
-     * WT-01: per-run workspace override — the child's file-tool jail cwd for THIS
+     * Per-run workspace override — the child's file-tool jail cwd for THIS
      * execution. A `spawn --worktree` child runs in an ISOLATED git worktree, so the
      * daemon passes the worktree dir here; the executor uses it as the SDK session
      * cwd + the resource-loader / command-handler / context-engine workspace root,
      * so exec/read/write/edit resolve inside the worktree (still attenuated + jailed
-     * — the worktree is confined under the agent's own jailed workspace, T-219-11).
+     * — the worktree is confined under the agent's own jailed workspace).
      * Absent ⇒ `deps.workspaceDir` (the agent's shared workspace — today's path,
      * byte-identical).
      */

package/node_modules/@comis/agent/dist/executor/user-representation-block.d.ts

@@ -1,24 +1,19 @@
 /**
- * The PURE deterministic per-user-profile formatter (the v2.31 FOLD-01 read path).
+ * The PURE deterministic per-user-profile formatter (the profile read path).
  * The read-path analog of {@link buildTemporalGuidanceBlock} (rag/temporal-guidance.ts):
  * a pure function over a `kind:"profile"` {@link MentalModel} that returns a FIXED-shape
- * system-prompt block (a `<user_profile>` block, the §7.3-guidance analog), or
+ * system-prompt block (a `<user_profile>` block), or
  * `undefined` when there is nothing to inject. When it returns `undefined` the caller
  * pushes NOTHING onto `memorySections` — that is the default-OFF byte-identity no-op
- * (a user with no profile leaves the prompt byte-identical to today's).
+ * (a user with no profile leaves the prompt byte-identical to the no-profile form).
  *
  * Wiring: prompt-assembly reads the profile LLM-FREE
  * (`mentalModelStore.list(scope, "profile")`, a deterministic store read — NO model
  * call) and pushes this block onto `memorySections`, exactly like the
- * temporal-guidance block. This is the milestone's #1 binding constraint: the
+ * temporal-guidance block. The binding constraint: the
  * recall HOT PATH stays LLM-free — the read is a deterministic store.list + this
  * pure format, never a recall lane / reasoning seam.
  *
- * v2.31 Phase 225-05: the legacy `buildUserRepresentationBlock(UserRepresentationEntry[])`
- * formatter (the old `userRepresentationStore.read` path) was DELETED with the standalone
- * user-representation subsystem. `buildProfileBlock` is the sole survivor — it renders the
- * SAME `<user_profile>` envelope from the folded kind:"profile" doc.
- *
  * Imports ONLY @comis/core TYPES — the agent-package production source must not
  * import the memory package (architecture.test.ts "agent -> memory cut"). The
  * profile `content` was already redaction-checked + `validateLearnedDocBody`-clean +
@@ -30,20 +25,17 @@
 import type { MentalModel } from "@comis/core";
 /**
  * Build the per-user profile system-prompt block from a `kind:"profile"`
- * {@link MentalModel} — the FOLD-01 (Phase 225) read-path replacement for the
- * deleted legacy `buildUserRepresentationBlock`. The fold rewired the `<user_profile>`
- * source from the deleted `userRepresentationStore` (a `UserRepresentationEntry[]`)
- * to the mental-model store (a `kind:"profile"` doc whose `structuredBody.sections`
+ * {@link MentalModel}. The `<user_profile>` source is the mental-model store
+ * (a `kind:"profile"` doc whose `structuredBody.sections`
  * are keyed by the four PREFIX-TYPE ids the `PROFILE_REFLECT_PROMPT` emits —
  * `identity` / `preference` / `relationship` / `instruction`).
  *
- * PURE + byte-stable (the legacy formatter's contract): it
+ * PURE + byte-stable: it
  * takes ONLY the doc and returns `string | undefined`, with NO store call, no
  * wall-clock read, no model, no `Result` wrapper (the sanctioned pure format
- * carve-out). It maps each prefix-type section onto the SAME fixed
- * {@link GROUP_ORDER} groups + the SAME code-pinned {@link GROUP_HEADING} prose +
- * the SAME `<user_profile>` wrapper as the legacy formatter — so the block is
- * EQUIVALENT-OR-BETTER (FOLD-03): same wrapper, same facts, same fixed group order
+ * carve-out). It maps each prefix-type section onto the fixed
+ * {@link GROUP_ORDER} groups + the code-pinned {@link GROUP_HEADING} prose +
+ * the `<user_profile>` wrapper
  * (the heading is taken from CODE, never the doc's own — so it cannot drift from
  * the pinned prose). A section whose id is not a known prefix type is ignored
  * (forward-compatible); a section with an empty body contributes no heading.
@@ -51,7 +43,7 @@ import type { MentalModel } from "@comis/core";
  * Returns `undefined` when the doc has NO usable section content (no
  * structuredBody, or every prefix-type section is empty/absent) — the caller then
  * pushes NOTHING onto `memorySections`, the default-OFF byte-identity no-op (a user
- * with no profile leaves the prompt byte-identical to today's). The doc's `content`
+ * with no profile leaves the prompt byte-identical to the no-profile form). The doc's `content`
  * was redaction-checked + `validateLearnedDocBody`-clean + high-trust at WRITE time;
  * this read-side formatter does not re-validate.
  */

package/node_modules/@comis/agent/dist/executor/user-representation-block.js

@@ -1,25 +1,20 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The PURE deterministic per-user-profile formatter (the v2.31 FOLD-01 read path).
+ * The PURE deterministic per-user-profile formatter (the profile read path).
  * The read-path analog of {@link buildTemporalGuidanceBlock} (rag/temporal-guidance.ts):
  * a pure function over a `kind:"profile"` {@link MentalModel} that returns a FIXED-shape
- * system-prompt block (a `<user_profile>` block, the §7.3-guidance analog), or
+ * system-prompt block (a `<user_profile>` block), or
  * `undefined` when there is nothing to inject. When it returns `undefined` the caller
  * pushes NOTHING onto `memorySections` — that is the default-OFF byte-identity no-op
- * (a user with no profile leaves the prompt byte-identical to today's).
+ * (a user with no profile leaves the prompt byte-identical to the no-profile form).
  *
  * Wiring: prompt-assembly reads the profile LLM-FREE
  * (`mentalModelStore.list(scope, "profile")`, a deterministic store read — NO model
  * call) and pushes this block onto `memorySections`, exactly like the
- * temporal-guidance block. This is the milestone's #1 binding constraint: the
+ * temporal-guidance block. The binding constraint: the
  * recall HOT PATH stays LLM-free — the read is a deterministic store.list + this
  * pure format, never a recall lane / reasoning seam.
  *
- * v2.31 Phase 225-05: the legacy `buildUserRepresentationBlock(UserRepresentationEntry[])`
- * formatter (the old `userRepresentationStore.read` path) was DELETED with the standalone
- * user-representation subsystem. `buildProfileBlock` is the sole survivor — it renders the
- * SAME `<user_profile>` envelope from the folded kind:"profile" doc.
- *
  * Imports ONLY @comis/core TYPES — the agent-package production source must not
  * import the memory package (architecture.test.ts "agent -> memory cut"). The
  * profile `content` was already redaction-checked + `validateLearnedDocBody`-clean +
@@ -49,20 +44,17 @@ const GROUP_HEADING = {
 };
 /**
  * Build the per-user profile system-prompt block from a `kind:"profile"`
- * {@link MentalModel} — the FOLD-01 (Phase 225) read-path replacement for the
- * deleted legacy `buildUserRepresentationBlock`. The fold rewired the `<user_profile>`
- * source from the deleted `userRepresentationStore` (a `UserRepresentationEntry[]`)
- * to the mental-model store (a `kind:"profile"` doc whose `structuredBody.sections`
+ * {@link MentalModel}. The `<user_profile>` source is the mental-model store
+ * (a `kind:"profile"` doc whose `structuredBody.sections`
  * are keyed by the four PREFIX-TYPE ids the `PROFILE_REFLECT_PROMPT` emits —
  * `identity` / `preference` / `relationship` / `instruction`).
  *
- * PURE + byte-stable (the legacy formatter's contract): it
+ * PURE + byte-stable: it
  * takes ONLY the doc and returns `string | undefined`, with NO store call, no
  * wall-clock read, no model, no `Result` wrapper (the sanctioned pure format
- * carve-out). It maps each prefix-type section onto the SAME fixed
- * {@link GROUP_ORDER} groups + the SAME code-pinned {@link GROUP_HEADING} prose +
- * the SAME `<user_profile>` wrapper as the legacy formatter — so the block is
- * EQUIVALENT-OR-BETTER (FOLD-03): same wrapper, same facts, same fixed group order
+ * carve-out). It maps each prefix-type section onto the fixed
+ * {@link GROUP_ORDER} groups + the code-pinned {@link GROUP_HEADING} prose +
+ * the `<user_profile>` wrapper
  * (the heading is taken from CODE, never the doc's own — so it cannot drift from
  * the pinned prose). A section whose id is not a known prefix type is ignored
  * (forward-compatible); a section with an empty body contributes no heading.
@@ -70,7 +62,7 @@ const GROUP_HEADING = {
  * Returns `undefined` when the doc has NO usable section content (no
  * structuredBody, or every prefix-type section is empty/absent) — the caller then
  * pushes NOTHING onto `memorySections`, the default-OFF byte-identity no-op (a user
- * with no profile leaves the prompt byte-identical to today's). The doc's `content`
+ * with no profile leaves the prompt byte-identical to the no-profile form). The doc's `content`
  * was redaction-checked + `validateLearnedDocBody`-clean + high-trust at WRITE time;
  * this read-side formatter does not re-validate.
  */

package/node_modules/@comis/agent/dist/executor/verification-gate-synth-deps.d.ts

@@ -7,10 +7,10 @@
  * ModelProfile derives capacity/security from capabilityClass (the hook has no
  * resolved ModelProfile in scope).
  *
- * WR-02: apiKey:"" is SAFE here because shouldRunCritic (verification-gate.ts)
+ * apiKey:"" is SAFE here because shouldRunCritic (verification-gate.ts)
  * gates the critic to keyless providers (ollama/lm-studio) — a key-requiring
- * cloud provider is skipped-with-WARN upstream and never reaches this builder.
- * Cloud apiKey threading is deferred to Phase 155.
+ * cloud provider is skipped-with-WARN upstream and never reaches this builder,
+ * so no cloud apiKey threading exists here.
  *
  * Forbidden: Date.now(), raw setTimeout/clearTimeout, new Date().
  * Invariant: no compatibility shims, no deprecated annotations.

package/node_modules/@comis/agent/dist/executor/verification-gate-synth-deps.js

@@ -5,7 +5,7 @@ export function buildSyntheticCriticDeps(params) {
         deps: {
             provider: params.provider,
             modelId: params.modelId,
-            apiKey: "", // WR-02: keyless-only (gated by shouldRunCritic); cloud → Phase 155
+            apiKey: "", // keyless-only (gated by shouldRunCritic); cloud providers never reach here
             clock: params.clock,
             logger: params.logger,
             agentId: params.agentId,

package/node_modules/@comis/agent/dist/executor/verification-gate.d.ts

@@ -16,20 +16,20 @@ export interface CriticDeps {
     eventBus: TypedEventBus;
 }
 /**
- * CRITIC-ONLY verdict budget — NOT the main answer path (CR-01). 512 tokens
+ * CRITIC-ONLY verdict budget — NOT the main answer path. 512 tokens
  * suffices for the small verdict JSON; native-reasoning profiles get 4× so
- * reasoning_content doesn't starve the verdict (D7).
+ * reasoning_content doesn't starve the verdict.
  */
 export declare function resolveMaxOutputTokens(profile: ModelProfile): number;
 /**
- * CR-01: MAIN-PATH output budget. Returns the model's REAL maxOutputTokens so
+ * MAIN-PATH output budget. Returns the model's REAL maxOutputTokens so
  * the visible answer is never clamped to the 512-token verdict reserve.
  * Non-reasoning → full profile budget; native-reasoning → sized UP (never
  * down) so reasoning_content can't starve the answer. config.maxTokens (when
  * set by the operator) takes precedence at the call site.
  */
 export declare function resolveMainPathMaxOutputTokens(profile: ModelProfile): number;
-/** Exported for parity assertion in scaffold-defaults.ts (Plan 02 cross-file test). */
+/** Exported for the cross-file parity assertion in the scaffold-defaults tests. */
 export declare const KEYLESS_CRITIC_PROVIDERS: Set<string>;
 export declare function shouldRunCritic(params: {
     capabilityClass: CapabilityClass | undefined;
@@ -37,18 +37,18 @@ export declare function shouldRunCritic(params: {
     executionPlanRef: {
         current: ExecutionPlan | undefined;
     };
-    /** Resolved provider for this execution (WR-02: keyless-only gate). */
+    /** Resolved provider for this execution (keyless-only gate). */
     provider: string;
-    /** Optional logger for the skip-with-WARN diagnostic (WR-02). */
+    /** Optional logger for the skip-with-WARN diagnostic. */
     logger?: ComisLogger;
-    /** SD3 (Phase 158): pre-resolved effective enabled flag from resolveScaffoldDefaults. */
+    /** Pre-resolved effective enabled flag from resolveScaffoldDefaults. */
     effectiveEnabled?: boolean;
 }): boolean;
 export declare function runVerificationCritic(params: {
     response: string;
     plan: ExecutionPlan | undefined;
     deps: CriticDeps;
-    /** Retained for the future re-queue path (R5/Phase 155+); not branched on now. */
+    /** Retained for a future re-queue path; not branched on now. */
     maxRetries?: number;
 }): Promise<{
     verdict: CriticVerdict["verdict"];