comisai 1.0.44 → 1.0.46

package/node_modules/@comis/agent/dist/executor/stream-wrappers/request-body/tool-result-clearing.d.ts

@@ -19,7 +19,7 @@ export declare const MICROCOMPACT_MIN_CONTENT_LENGTH = 1000;
  * Edit/write tool results are preserved because they carry the LLM's understanding
  * of what was changed -- clearing them loses context.
  *
- * EFF-02: these are Comis's ACTUAL emitted builtin tool names (the `block.name` on the
+ * These are Comis's ACTUAL emitted builtin tool names (the `block.name` on the
  * `tool_use` blocks in the message stream), verified at the builtin registrations:
  * `read` (read-tool), `grep` (grep-tool), `find` (find-tool), `ls` (ls-tool),
  * `exec` (exec-tool), `web_fetch` (web-fetch-tool), `web_search` (web-search-tool).
@@ -74,14 +74,14 @@ export declare function reorderContentForStablePrefix(messages: Array<Record<str
 /**
  * Strip thinking blocks from EVERY assistant message in the outgoing (replayed) request.
  *
- * cache break #C1/#C2 (2026-06-19): the LCD codec (parts-codec F3) reconstructs assistant
- * messages WITHOUT thinking (topLevelReasoningOnly), but the SDK's in-memory conversation
- * carries thinking on the ACTIVE tool cycle (the last assistant in the request). The earlier
- * #C1 fix kept that last assistant's thinking — but that one block is exactly what breaks the
- * cache: it is written WITH thinking (this call, where it is the active/last assistant) and
- * re-sent WITHOUT thinking the next call (when a newer assistant arrives and it becomes
+ * Why: the LCD codec (parts-codec) reconstructs assistant messages WITHOUT thinking
+ * (topLevelReasoningOnly), but the SDK's in-memory conversation carries thinking on the
+ * ACTIVE tool cycle (the last assistant in the request). Keeping only that last
+ * assistant's thinking is exactly what breaks the cache: the block is written WITH
+ * thinking (this call, where it is the active/last assistant) and re-sent WITHOUT
+ * thinking the next call (when a newer assistant arrives and it becomes
  * historical → stripped) → the cached prefix mutates at that index every turn boundary →
- * read collapse + re-write on thinking-heavy (coding) turns (#C2). Stripping thinking from
+ * read collapse + re-write on thinking-heavy (coding) turns. Stripping thinking from
  * EVERY replayed assistant (no keep-last exception) makes the cached form byte-identical to
  * the durable LCD form (zero historical thinking) so the prefix never mutates. Anthropic
  * tolerates a tool-use assistant with no thinking block as the active cycle — validated live
@@ -119,12 +119,12 @@ export declare function stripTransientRecallFromHistory(messages: Array<Record<s
  * Move the inline-recall block on the CURRENT (latest) user message off the cached
  * prefix and onto the UNCACHED tail.
  *
- * cache #C4 (2026-06-19): `envelope-wrapper` prepends the top-1 RAG recall block to the
+ * Why: `envelope-wrapper` prepends the top-1 RAG recall block to the
  * current user query, and pi-ai marks that message's last block with cache_control — so
  * the recall is CACHED while it's the current turn. The next call, that message goes
- * historical and `stripTransientRecallFromHistory` (C-FIX-3) removes the recall → the
+ * historical and `stripTransientRecallFromHistory` removes the recall → the
  * cached prefix mutates at that message → read collapse + a re-write of everything after
- * it (the dominant turn-boundary re-write, formerly mislabeled "#C3 / 4-marker cap").
+ * it (the dominant turn-boundary re-write).
  *
  * Unlike thinking (regenerated, so strippable everywhere — see `stripReplayThinking`),
  * recall is FUNCTIONAL input the model needs on the current turn, so it can't be removed.
@@ -144,7 +144,8 @@ export declare function deferRecallToUncachedTail(messages: Array<Record<string,
  * Strip the TRANSIENT inline-recall block from every HISTORICAL user-message item in an
  * OpenAI **Responses-API `input`** array, keeping it only on the latest user message.
  *
- * cache #C4-OAI (2026-06-19): the Anthropic prefix-stabilizers (C-FIX-3/#C4) are gated to
+ * Why: the Anthropic prefix-stabilizers (`stripTransientRecallFromHistory` /
+ * `deferRecallToUncachedTail`) are gated to
  * Anthropic-family providers (the cache_control machinery would 400 the Responses tools), so
  * they NEVER run for openai-codex — and Comis's request-body injector passes through entirely
  * for it. Result: the recall block on a user item is present while it's the current turn but
@@ -163,7 +164,7 @@ export declare function stripTransientRecallFromResponsesInput(input: Array<Reco
  * Strip ALL replayed `reasoning` items from an OpenAI Responses `input` array — the OpenAI
  * analog of {@link stripReplayThinking}.
  *
- * cache #C5-OAI (2026-06-19): on the native openai Responses API (`store: false`), the
+ * Why: on the native openai Responses API (`store: false`), the
  * pi-coding-agent conversation manager keeps `reasoning` items (which carry `encrypted_content`
  * for cross-step continuity) for RECENT turns but DROPS them from OLDER turns as the
  * conversation grows. A reasoning item present at an early index one turn is therefore gone the
@@ -175,7 +176,8 @@ export declare function stripTransientRecallFromResponsesInput(input: Array<Reco
  * this turn, then goes historical and is dropped next turn — the same boundary mutation). The
  * only byte-stable option is removing them CONSISTENTLY, every call. SAFE: the SDK already drops
  * aged reasoning and OpenAI still returns 200 (verified live: all turns ok, no 400). QUALITY
- * CAVEAT (bounded, reversible — the C-FIX-8 analog): the model re-reasons each step instead of
+ * CAVEAT (bounded, reversible — the same tradeoff as {@link stripReplayThinking}): the model
+ * re-reasons each step instead of
  * resuming the encrypted chain; reasoning-quality impact is unmeasured but the conclusions
  * (assistant messages + tool results) remain in context. Gated by the caller to the native
  * `openai`/Azure Responses path (codex keeps its reasoning stable and was already optimal).
@@ -188,7 +190,7 @@ export declare function stripReplayReasoningFromResponsesInput(input: Array<Reco
  * Defer the inline-recall block on the CURRENT (latest) user item of an OpenAI Responses
  * `input` array off the cacheable prefix and onto the UNCACHED tail.
  *
- * cache #C4-OAI (2026-06-19): stripping recall from HISTORICAL items alone
+ * Why: stripping recall from HISTORICAL items alone
  * (`stripTransientRecallFromResponsesInput`) is INSUFFICIENT — the LATEST user item still
  * carries recall, so this turn's auto-cache WRITE includes "U_latest + recall". Next turn that
  * item goes historical and the LCD rebuild emits it CLEAN (recall is transient, never

package/node_modules/@comis/agent/dist/executor/stream-wrappers/request-body/tool-result-clearing.js

@@ -21,7 +21,7 @@ export const MICROCOMPACT_MIN_CONTENT_LENGTH = 1000;
  * Edit/write tool results are preserved because they carry the LLM's understanding
  * of what was changed -- clearing them loses context.
  *
- * EFF-02: these are Comis's ACTUAL emitted builtin tool names (the `block.name` on the
+ * These are Comis's ACTUAL emitted builtin tool names (the `block.name` on the
  * `tool_use` blocks in the message stream), verified at the builtin registrations:
  * `read` (read-tool), `grep` (grep-tool), `find` (find-tool), `ls` (ls-tool),
  * `exec` (exec-tool), `web_fetch` (web-fetch-tool), `web_search` (web-search-tool).
@@ -239,14 +239,14 @@ export function reorderContentForStablePrefix(messages) {
 /**
  * Strip thinking blocks from EVERY assistant message in the outgoing (replayed) request.
  *
- * cache break #C1/#C2 (2026-06-19): the LCD codec (parts-codec F3) reconstructs assistant
- * messages WITHOUT thinking (topLevelReasoningOnly), but the SDK's in-memory conversation
- * carries thinking on the ACTIVE tool cycle (the last assistant in the request). The earlier
- * #C1 fix kept that last assistant's thinking — but that one block is exactly what breaks the
- * cache: it is written WITH thinking (this call, where it is the active/last assistant) and
- * re-sent WITHOUT thinking the next call (when a newer assistant arrives and it becomes
+ * Why: the LCD codec (parts-codec) reconstructs assistant messages WITHOUT thinking
+ * (topLevelReasoningOnly), but the SDK's in-memory conversation carries thinking on the
+ * ACTIVE tool cycle (the last assistant in the request). Keeping only that last
+ * assistant's thinking is exactly what breaks the cache: the block is written WITH
+ * thinking (this call, where it is the active/last assistant) and re-sent WITHOUT
+ * thinking the next call (when a newer assistant arrives and it becomes
  * historical → stripped) → the cached prefix mutates at that index every turn boundary →
- * read collapse + re-write on thinking-heavy (coding) turns (#C2). Stripping thinking from
+ * read collapse + re-write on thinking-heavy (coding) turns. Stripping thinking from
  * EVERY replayed assistant (no keep-last exception) makes the cached form byte-identical to
  * the durable LCD form (zero historical thinking) so the prefix never mutates. Anthropic
  * tolerates a tool-use assistant with no thinking block as the active cycle — validated live
@@ -340,12 +340,12 @@ const RECALL_PREFIX_RE = /^\s*\[Relevant context from memory:/;
  * Move the inline-recall block on the CURRENT (latest) user message off the cached
  * prefix and onto the UNCACHED tail.
  *
- * cache #C4 (2026-06-19): `envelope-wrapper` prepends the top-1 RAG recall block to the
+ * Why: `envelope-wrapper` prepends the top-1 RAG recall block to the
  * current user query, and pi-ai marks that message's last block with cache_control — so
  * the recall is CACHED while it's the current turn. The next call, that message goes
- * historical and `stripTransientRecallFromHistory` (C-FIX-3) removes the recall → the
+ * historical and `stripTransientRecallFromHistory` removes the recall → the
  * cached prefix mutates at that message → read collapse + a re-write of everything after
- * it (the dominant turn-boundary re-write, formerly mislabeled "#C3 / 4-marker cap").
+ * it (the dominant turn-boundary re-write).
  *
  * Unlike thinking (regenerated, so strippable everywhere — see `stripReplayThinking`),
  * recall is FUNCTIONAL input the model needs on the current turn, so it can't be removed.
@@ -404,7 +404,8 @@ export function deferRecallToUncachedTail(messages) {
  * Strip the TRANSIENT inline-recall block from every HISTORICAL user-message item in an
  * OpenAI **Responses-API `input`** array, keeping it only on the latest user message.
  *
- * cache #C4-OAI (2026-06-19): the Anthropic prefix-stabilizers (C-FIX-3/#C4) are gated to
+ * Why: the Anthropic prefix-stabilizers (`stripTransientRecallFromHistory` /
+ * `deferRecallToUncachedTail`) are gated to
  * Anthropic-family providers (the cache_control machinery would 400 the Responses tools), so
  * they NEVER run for openai-codex — and Comis's request-body injector passes through entirely
  * for it. Result: the recall block on a user item is present while it's the current turn but
@@ -464,7 +465,7 @@ export function stripTransientRecallFromResponsesInput(input) {
  * Strip ALL replayed `reasoning` items from an OpenAI Responses `input` array — the OpenAI
  * analog of {@link stripReplayThinking}.
  *
- * cache #C5-OAI (2026-06-19): on the native openai Responses API (`store: false`), the
+ * Why: on the native openai Responses API (`store: false`), the
  * pi-coding-agent conversation manager keeps `reasoning` items (which carry `encrypted_content`
  * for cross-step continuity) for RECENT turns but DROPS them from OLDER turns as the
  * conversation grows. A reasoning item present at an early index one turn is therefore gone the
@@ -476,7 +477,8 @@ export function stripTransientRecallFromResponsesInput(input) {
  * this turn, then goes historical and is dropped next turn — the same boundary mutation). The
  * only byte-stable option is removing them CONSISTENTLY, every call. SAFE: the SDK already drops
  * aged reasoning and OpenAI still returns 200 (verified live: all turns ok, no 400). QUALITY
- * CAVEAT (bounded, reversible — the C-FIX-8 analog): the model re-reasons each step instead of
+ * CAVEAT (bounded, reversible — the same tradeoff as {@link stripReplayThinking}): the model
+ * re-reasons each step instead of
  * resuming the encrypted chain; reasoning-quality impact is unmeasured but the conclusions
  * (assistant messages + tool results) remain in context. Gated by the caller to the native
  * `openai`/Azure Responses path (codex keeps its reasoning stable and was already optimal).
@@ -498,7 +500,7 @@ export function stripReplayReasoningFromResponsesInput(input) {
  * Defer the inline-recall block on the CURRENT (latest) user item of an OpenAI Responses
  * `input` array off the cacheable prefix and onto the UNCACHED tail.
  *
- * cache #C4-OAI (2026-06-19): stripping recall from HISTORICAL items alone
+ * Why: stripping recall from HISTORICAL items alone
  * (`stripTransientRecallFromResponsesInput`) is INSUFFICIENT — the LATEST user item still
  * carries recall, so this turn's auto-cache WRITE includes "U_latest + recall". Next turn that
  * item goes historical and the LCD rebuild emits it CLEAN (recall is transient, never

package/node_modules/@comis/agent/dist/executor/stream-wrappers/request-body/types.d.ts

@@ -157,7 +157,7 @@ export interface RequestBodyInjectorConfig {
     /**
      * ModelProfile resolved for this execution. Carries supportsPromptCache,
      * supportsServerToolSearch, and other capability flags resolved once
-     * per execution in pi-executor.ts (L1/L2 routing — Phase 155-01).
+     * per execution in pi-executor.ts (L1/L2 routing).
      *
      * When present: supportsPromptCache drives cache-breakpoint placement
      * (factory.ts needsCacheBreakpoints); supportsServerToolSearch drives

package/node_modules/@comis/agent/dist/executor/stream-wrappers/stub-filter-injector.js

@@ -26,8 +26,8 @@
  * Extract a tool's name across provider shapes: Anthropic puts it at top-level
  * `t.name`; OpenAI/Ollama (the /v1 tools array) nests it at `t.function.name`.
  * Checking only `t.name` silently no-ops the filter for OpenAI-format providers
- * (live finding, 2026-06-12: all deferred-tool stubs reached Ollama, nullifying
- * the small-class tool deferral and context-exhausting local models).
+ * (observed live: all deferred-tool stubs reached Ollama, nullifying the
+ * small-class tool deferral and context-exhausting local models).
  */
 function toolName(tool) {
     if (typeof tool.name === "string")

package/node_modules/@comis/agent/dist/executor/stream-wrappers/tool-call-repair-wrapper.d.ts

@@ -11,7 +11,7 @@
  * context so the MODEL sees a well-formed error and self-corrects by re-emitting
  * valid JSON on its next turn.
  *
- * WR-03: this synthetic toolResult does NOT interact with ToolRetryBreaker.
+ * This synthetic toolResult does NOT interact with ToolRetryBreaker.
  * The breaker's counters are driven exclusively by real tool-execution events
  * in pi-event-bridge.ts (ToolRetryBreaker.recordResult), not by messages a
  * StreamFn wrapper injects into context.messages. Moreover, unparseable args
@@ -21,7 +21,7 @@
  * is not a PARAMETER_VALIDATION_TAGS breaker carve-out (there is nothing to
  * carve out, because the breaker never sees this turn).
  *
- * S3 INVARIANT: repair is shape-only. Repaired args flow through the EXISTING
+ * INVARIANT: repair is shape-only. Repaired args flow through the EXISTING
  * downstream exec-security gates (validateExecCommand for exec tools) — those
  * gates are the final authority on scope for ALL tool types.
  *
@@ -40,12 +40,12 @@ import type { ModelProfile } from "../model-profile.js";
  *
  * When a ToolCall's arguments field arrives as a raw JSON string (runtime value
  * is a string despite being typed as Record<string, any>), this wrapper:
- * - Attempts structural repair via the SDK's parseStreamingJson (SA9: strict
- *   superset of the old trailing-comma-only repair; also handles truncated JSON
+ * - Attempts structural repair via the SDK's parseStreamingJson (a strict
+ *   superset of trailing-comma-only repair; also handles truncated JSON
  *   and control characters; same function the provider layer uses)
  * - On success: replaces the string with the parsed object (value-preserving)
  * - On failure: injects a synthetic ToolResultMessage error with a "Validation
- *   failed" prefix so the model self-corrects on its next turn. (WR-03: this
+ *   failed" prefix so the model self-corrects on its next turn. (This
  *   does NOT touch ToolRetryBreaker — the breaker is driven by real
  *   tool-execution events in pi-event-bridge.ts, and unparseable args never
  *   reach tool execution, so the breaker is uninvolved on this path.)

package/node_modules/@comis/agent/dist/executor/stream-wrappers/tool-call-repair-wrapper.js

@@ -12,7 +12,7 @@
  * context so the MODEL sees a well-formed error and self-corrects by re-emitting
  * valid JSON on its next turn.
  *
- * WR-03: this synthetic toolResult does NOT interact with ToolRetryBreaker.
+ * This synthetic toolResult does NOT interact with ToolRetryBreaker.
  * The breaker's counters are driven exclusively by real tool-execution events
  * in pi-event-bridge.ts (ToolRetryBreaker.recordResult), not by messages a
  * StreamFn wrapper injects into context.messages. Moreover, unparseable args
@@ -22,7 +22,7 @@
  * is not a PARAMETER_VALIDATION_TAGS breaker carve-out (there is nothing to
  * carve out, because the breaker never sees this turn).
  *
- * S3 INVARIANT: repair is shape-only. Repaired args flow through the EXISTING
+ * INVARIANT: repair is shape-only. Repaired args flow through the EXISTING
  * downstream exec-security gates (validateExecCommand for exec tools) — those
  * gates are the final authority on scope for ALL tool types.
  *
@@ -39,12 +39,12 @@ import { parseStreamingJson } from "@earendil-works/pi-ai";
  *
  * When a ToolCall's arguments field arrives as a raw JSON string (runtime value
  * is a string despite being typed as Record<string, any>), this wrapper:
- * - Attempts structural repair via the SDK's parseStreamingJson (SA9: strict
- *   superset of the old trailing-comma-only repair; also handles truncated JSON
+ * - Attempts structural repair via the SDK's parseStreamingJson (a strict
+ *   superset of trailing-comma-only repair; also handles truncated JSON
  *   and control characters; same function the provider layer uses)
  * - On success: replaces the string with the parsed object (value-preserving)
  * - On failure: injects a synthetic ToolResultMessage error with a "Validation
- *   failed" prefix so the model self-corrects on its next turn. (WR-03: this
+ *   failed" prefix so the model self-corrects on its next turn. (This
  *   does NOT touch ToolRetryBreaker — the breaker is driven by real
  *   tool-execution events in pi-event-bridge.ts, and unparseable args never
  *   reach tool execution, so the breaker is uninvolved on this path.)
@@ -59,7 +59,7 @@ export function createToolCallRepairWrapper(_modelProfile, logger) {
     return function toolCallRepairWrapper(next) {
         return (model, context, options) => {
             const repairedMessages = [];
-            // WR-04 (idempotency): the wrapper runs on the OUTGOING context on every
+            // Idempotency: the wrapper runs on the OUTGOING context on every
             // stream call. Collect the toolCallIds that already have a toolResult so a
             // second pass over the same history does NOT inject a duplicate synthetic
             // validation-failed result for a tool call that was already answered.
@@ -93,8 +93,8 @@ export function createToolCallRepairWrapper(_modelProfile, logger) {
                     if (typeof rawArgs !== "string")
                         return block;
                     // Arguments arrived as a raw JSON string — attempt shape-only repair via the SDK's
-                    // parseStreamingJson (SA9: same fn the provider layer uses; strict superset of the
-                    // old trailing-comma-only repair: handles trailing commas + truncated + control chars).
+                    // parseStreamingJson (same fn the provider layer uses; a strict superset of
+                    // trailing-comma-only repair: handles trailing commas + truncated + control chars).
                     // parseStreamingJson NEVER throws — returns {} or partial object for garbage input.
                     // Cast: rawArgs is narrowed to never by TS (ToolCall.arguments: Record<string,any>)
                     // but we confirmed it is a string above; the cast is safe and intentional.
@@ -131,7 +131,7 @@ export function createToolCallRepairWrapper(_modelProfile, logger) {
                     }
                     // Irreparable — inject a synthetic ToolResultMessage error so the model
                     // sees a well-formed validation error and self-corrects on its next
-                    // turn. WR-03: this message is context for the MODEL only; it does not
+                    // turn. This message is context for the MODEL only; it does not
                     // reach ToolRetryBreaker (counters come from real tool-execution events
                     // in pi-event-bridge.ts), and unparseable args never trigger a tool
                     // execution, so the breaker is not involved on this path.
@@ -142,14 +142,14 @@ export function createToolCallRepairWrapper(_modelProfile, logger) {
                         hint: "Model emitted irreparable tool-call JSON; returning validation_failed",
                     }, "Irreparable tool-call JSON — shape repair failed");
                     modified = true;
-                    // WR-04 (well-formed assistant block): replace the raw string args with
+                    // Well-formed assistant block: replace the raw string args with
                     // a safe empty object so the outgoing assistant message carries
                     // arguments as the object the SDK/provider serializer expects (a string
                     // may be rejected or silently mishandled). Replacing it also means a
                     // second pass over this history sees a parsed object (not a string) and
                     // will not re-detect / re-fail this same tool call.
                     const sanitizedBlock = { ...toolCall, arguments: {} };
-                    // WR-04 (de-dup): only inject a synthetic toolResult if this tool call
+                    // De-dup: only inject a synthetic toolResult if this tool call
                     // does not already have one in the history. Prevents duplicating the
                     // validation-failed message (and growing context) on every turn.
                     if (!existingToolResultIds.has(toolCall.id)) {

package/node_modules/@comis/agent/dist/executor/stream-wrappers/turn-result-budget-wrapper.d.ts

@@ -26,14 +26,14 @@ export interface TurnResultBudgetWrapperResult {
  * Create a wrapper that enforces a per-turn aggregate character budget across
  * all tool results before passing context to the LLM.
  *
- * Uses the pure `applyTurnResultBudget` function from .
+ * Uses the pure `applyTurnResultBudget` function from safety/turn-result-budget.ts.
  * When the budget is exceeded, tool results are proportionally truncated
  * with each tool guaranteed at least `minCharsPerTool` characters.
  *
  * @param maxTurnChars - Maximum aggregate text chars across all tool results per turn
  * @param minCharsPerTool - Minimum chars each tool result is guaranteed
  * @param logger - Logger for WARN output when budget is exceeded
- * @param onTruncation - Optional callback for per-tool truncation metadata ( audit)
+ * @param onTruncation - Optional callback for per-tool truncation metadata (feeds audit event metadata)
  * @returns Object with wrapper and getTurnBudgetSummary getter
  */
 export declare function createTurnResultBudgetWrapper(maxTurnChars: number, minCharsPerTool: number, logger: ComisLogger, onTruncation?: (toolCallId: string, meta: {

package/node_modules/@comis/agent/dist/executor/stream-wrappers/turn-result-budget-wrapper.js

@@ -12,14 +12,14 @@ import { applyTurnResultBudget } from "../../safety/turn-result-budget.js";
  * Create a wrapper that enforces a per-turn aggregate character budget across
  * all tool results before passing context to the LLM.
  *
- * Uses the pure `applyTurnResultBudget` function from .
+ * Uses the pure `applyTurnResultBudget` function from safety/turn-result-budget.ts.
  * When the budget is exceeded, tool results are proportionally truncated
  * with each tool guaranteed at least `minCharsPerTool` characters.
  *
  * @param maxTurnChars - Maximum aggregate text chars across all tool results per turn
  * @param minCharsPerTool - Minimum chars each tool result is guaranteed
  * @param logger - Logger for WARN output when budget is exceeded
- * @param onTruncation - Optional callback for per-tool truncation metadata ( audit)
+ * @param onTruncation - Optional callback for per-tool truncation metadata (feeds audit event metadata)
  * @returns Object with wrapper and getTurnBudgetSummary getter
  */
 export function createTurnResultBudgetWrapper(maxTurnChars, minCharsPerTool, logger, onTruncation) {

package/node_modules/@comis/agent/dist/executor/timeout-knob.d.ts

@@ -1,6 +1,6 @@
 /**
- * TIMEOUT_KNOB_BY_SOURCE table (LAT-01): source → knob templating for timeout
- * hints, mirroring the KNOB-02 `CAP_KNOB_BY_SOURCE` discipline
+ * TIMEOUT_KNOB_BY_SOURCE table: source → knob templating for timeout
+ * hints, mirroring the `CAP_KNOB_BY_SOURCE` discipline
  * (context-engine/errors.ts:39-47). Every timeout hint/payload renders its
  * knob string from here — never an ad-hoc string at a classify site.
  *
@@ -10,16 +10,15 @@ import type { TimeoutSource } from "../model/operation-model-resolver.js";
 /**
  * Render the exact config knob (or honest prose) for a timeout binding source.
  *
- * Table-not-template discipline (KNOB-02 precedent): NEVER string-template a
+ * Table-not-template discipline: NEVER string-template a
  * config key from the source name; sources without a real knob
- * (`graph_constant`) get honest prose, never a rendered fake key (D-11 — the
- * dead-knob lie class this phase kills). The operation key is `timeout`, NOT
- * `timeoutMs` — `OperationModelEntrySchema` is strictObject, so the
- * documented `timeoutMs` would be REJECTED at config parse (177-RESEARCH
- * Critical Finding 2; the doc itself is fixed in 177-06).
+ * (`graph_constant`) get honest prose, never a rendered fake key — a hint
+ * must never name a knob that does not exist. The operation key is
+ * `timeout`, NOT `timeoutMs` — `OperationModelEntrySchema` is strictObject,
+ * so a `timeoutMs` key would be REJECTED at config parse.
  *
  * Interpolates ONLY agentId + operationType (both already log-canonical
- * fields) — never env values, never message bodies (T-177-05).
+ * fields) — never env values, never message bodies.
  *
  * @param source - Which resolution level bound the effective timeout
  * @param agentId - Agent whose config owns the knob; undefined renders the
@@ -31,17 +30,17 @@ import type { TimeoutSource } from "../model/operation-model-resolver.js";
  */
 export declare function describeTimeoutKnob(source: TimeoutSource, agentId: string | undefined, operationType: string | undefined): string;
 /**
- * Render the retry/fallback whole-turn knob (177-REVIEW WR-01).
+ * Render the retry/fallback whole-turn knob.
  *
  * Rotation, model-fallback, and LKW prompts race the NON-resettable
- * `retryPromptTimeoutMs` (LAT-02 Open Q2: whole-turn semantics,
- * pin-and-document), so a kill on those paths — `PromptTimeoutError.limit`
- * absent — must name the retry knob. The source→knob table above describes
- * the **promptTimeoutMs** binding and would render the stall knob for a kill
- * the stall budget never saw (wrong framing, wrong lever, the retry value
- * misattributed to the stall key).
+ * `retryPromptTimeoutMs` (whole-turn semantics), so a kill on those
+ * paths — `PromptTimeoutError.limit` absent — must name the retry knob.
+ * The source→knob table above describes the **promptTimeoutMs** binding
+ * and would render the stall knob for a kill the stall budget never saw
+ * (wrong framing, wrong lever, the retry value misattributed to the
+ * stall key).
  *
- * Same interpolation discipline as the table: agentId only (T-177-05); the
- * key is a REAL `agents.*` family, never a rendered fake (D-11).
+ * Same interpolation discipline as the table: agentId only; the key is a
+ * REAL `agents.*` family, never a rendered fake.
  */
 export declare function describeRetryTimeoutKnob(agentId: string | undefined): string;

package/node_modules/@comis/agent/dist/executor/timeout-knob.js

@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * TIMEOUT_KNOB_BY_SOURCE table (LAT-01): source → knob templating for timeout
- * hints, mirroring the KNOB-02 `CAP_KNOB_BY_SOURCE` discipline
+ * TIMEOUT_KNOB_BY_SOURCE table: source → knob templating for timeout
+ * hints, mirroring the `CAP_KNOB_BY_SOURCE` discipline
  * (context-engine/errors.ts:39-47). Every timeout hint/payload renders its
  * knob string from here — never an ad-hoc string at a classify site.
  *
@@ -10,16 +10,15 @@
 /**
  * Render the exact config knob (or honest prose) for a timeout binding source.
  *
- * Table-not-template discipline (KNOB-02 precedent): NEVER string-template a
+ * Table-not-template discipline: NEVER string-template a
  * config key from the source name; sources without a real knob
- * (`graph_constant`) get honest prose, never a rendered fake key (D-11 — the
- * dead-knob lie class this phase kills). The operation key is `timeout`, NOT
- * `timeoutMs` — `OperationModelEntrySchema` is strictObject, so the
- * documented `timeoutMs` would be REJECTED at config parse (177-RESEARCH
- * Critical Finding 2; the doc itself is fixed in 177-06).
+ * (`graph_constant`) get honest prose, never a rendered fake key — a hint
+ * must never name a knob that does not exist. The operation key is
+ * `timeout`, NOT `timeoutMs` — `OperationModelEntrySchema` is strictObject,
+ * so a `timeoutMs` key would be REJECTED at config parse.
  *
  * Interpolates ONLY agentId + operationType (both already log-canonical
- * fields) — never env values, never message bodies (T-177-05).
+ * fields) — never env values, never message bodies.
  *
  * @param source - Which resolution level bound the effective timeout
  * @param agentId - Agent whose config owns the knob; undefined renders the
@@ -45,18 +44,18 @@ export function describeTimeoutKnob(source, agentId, operationType) {
     }
 }
 /**
- * Render the retry/fallback whole-turn knob (177-REVIEW WR-01).
+ * Render the retry/fallback whole-turn knob.
  *
  * Rotation, model-fallback, and LKW prompts race the NON-resettable
- * `retryPromptTimeoutMs` (LAT-02 Open Q2: whole-turn semantics,
- * pin-and-document), so a kill on those paths — `PromptTimeoutError.limit`
- * absent — must name the retry knob. The source→knob table above describes
- * the **promptTimeoutMs** binding and would render the stall knob for a kill
- * the stall budget never saw (wrong framing, wrong lever, the retry value
- * misattributed to the stall key).
+ * `retryPromptTimeoutMs` (whole-turn semantics), so a kill on those
+ * paths — `PromptTimeoutError.limit` absent — must name the retry knob.
+ * The source→knob table above describes the **promptTimeoutMs** binding
+ * and would render the stall knob for a kill the stall budget never saw
+ * (wrong framing, wrong lever, the retry value misattributed to the
+ * stall key).
  *
- * Same interpolation discipline as the table: agentId only (T-177-05); the
- * key is a REAL `agents.*` family, never a rendered fake (D-11).
+ * Same interpolation discipline as the table: agentId only; the key is a
+ * REAL `agents.*` family, never a rendered fake.
  */
 export function describeRetryTimeoutKnob(agentId) {
     return `agents.${agentId ?? "<id>"}.promptTimeout.retryPromptTimeoutMs`;

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

@@ -1,5 +1,5 @@
 /**
- * Per-field stringified-JSON tool-argument coercion (F-3, live 2026-06-12).
+ * Per-field stringified-JSON tool-argument coercion.
  *
  * Small models routinely emit a well-formed arguments object whose ONE
  * array/object field is a *stringified* JSON value, e.g.

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

@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * Per-field stringified-JSON tool-argument coercion (F-3, live 2026-06-12).
+ * Per-field stringified-JSON tool-argument coercion.
  *
  * Small models routinely emit a well-formed arguments object whose ONE
  * array/object field is a *stringified* JSON value, e.g.

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

@@ -1,7 +1,6 @@
 /**
- * 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
@@ -9,7 +8,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
  */
@@ -75,7 +74,7 @@ export interface DeferralContext {
      *  queries re-ask for loaded MCPs. Must NOT include names that were
      *  deferred -- pass the post-deferral set, not mergedCustomTools. */
     activeToolNames?: ReadonlySet<string>;
-    /** SD7 (Phase 159): capability-class active-tool ceiling.
+    /** Capability-class active-tool ceiling.
      *  When set, the active tool count is capped to this value after all other
      *  deferral passes. Only CORE_TOOLS and recently-used tools are guaranteed
      *  active; the cold long-tail is deferred behind discover_tools until the
@@ -115,8 +114,8 @@ export declare const DEFERRAL_RULES: DeferralRule[];
  */
 export declare const CORE_TOOLS: Set<string>;
 /**
- * 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.
@@ -127,12 +126,11 @@ export declare const CORE_TOOLS: Set<string>;
  * 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.
@@ -190,7 +188,7 @@ export declare function resolveToolDescription(tool: ToolDefinition): string;
  * 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] }`.
@@ -276,7 +274,7 @@ export interface EnforceToolBudgetFitParams {
     /** The system prompt text WITHOUT tool schemas — the non-evictable fixed
      *  overhead the fit budget must reserve. Passed as TEXT (not a char count) so
      *  the token estimate applies scriptTokenFactor over the actual script, exactly
-     *  as estimateSystemTokensFactored does (TOK-01). */
+     *  as estimateSystemTokensFactored does. */
     systemPromptText: string;
     /** Effective context window in tokens (min(configured, served, capabilityCap)). */
     contextWindow: number;
@@ -385,8 +383,8 @@ export interface ToolDiscoveryScoreConfig {
  * 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.