comisai 1.0.42 → 1.0.45

package/dist/index.d.ts

@@ -8,6 +8,8 @@ import * as scheduler from "@comis/scheduler";
 import * as agent from "@comis/agent";
 import * as channels from "@comis/channels";
 import * as orchestrator from "@comis/orchestrator";
+import * as observability from "@comis/observability";
+import * as observabilityOtel from "@comis/observability-otel";
 import * as cli from "@comis/cli";
 import * as daemon from "@comis/daemon";
-export { shared, core, infra, memory, gateway, skills, scheduler, agent, channels, orchestrator, cli, daemon, };
+export { shared, core, infra, memory, gateway, skills, scheduler, agent, channels, orchestrator, observability, observabilityOtel, cli, daemon, };

package/dist/index.js

@@ -11,6 +11,8 @@ import * as scheduler from "@comis/scheduler";
 import * as agent from "@comis/agent";
 import * as channels from "@comis/channels";
 import * as orchestrator from "@comis/orchestrator";
+import * as observability from "@comis/observability";
+import * as observabilityOtel from "@comis/observability-otel";
 import * as cli from "@comis/cli";
 import * as daemon from "@comis/daemon";
-export { shared, core, infra, memory, gateway, skills, scheduler, agent, channels, orchestrator, cli, daemon, };
+export { shared, core, infra, memory, gateway, skills, scheduler, agent, channels, orchestrator, observability, observabilityOtel, cli, daemon, };

package/dist/observability-otel.d.ts

@@ -0,0 +1 @@
+export * from "@comis/observability-otel";

package/dist/observability-otel.js

@@ -0,0 +1,2 @@
+// SPDX-License-Identifier: Apache-2.0
+export * from "@comis/observability-otel";

package/dist/observability.d.ts

@@ -0,0 +1 @@
+export * from "@comis/observability";

package/dist/observability.js

@@ -0,0 +1,2 @@
+// SPDX-License-Identifier: Apache-2.0
+export * from "@comis/observability";

package/node_modules/@comis/agent/dist/background/background-task-persistence.d.ts

@@ -4,7 +4,16 @@ export declare const TASK_DIR_NAME = "background-tasks";
 /**
  * Persist a task to disk synchronously.
  *
- * Writes to `dataDir/{agentId}/{taskId}.json`.
+ * Writes to `dataDir/{agentId}/{taskId}.json`. Routes through the
+ * `@comis/observability` fs-safe substrate so the parent dir lands at
+ * `0o700` and the file at `0o600` (file-mode invariants). `dataDir`
+ * is passed as `confinedBaseDir` for the ancestor-symlink defense.
+ *
+ * Result errors are intentionally swallowed — this writer's existing
+ * contract is best-effort persistence: a failure to persist must not
+ * propagate to the caller (which already returned a placeholder to the
+ * agent). The subsequent recovery scan will simply miss this task,
+ * matching the pre-migration semantics.
  */
 export declare function persistTaskSync(dataDir: string, task: BackgroundTask | PersistedTaskState): void;
 /**

package/node_modules/@comis/agent/dist/background/background-task-persistence.js

@@ -3,13 +3,19 @@
 /**
  * File-based persistence for background tasks.
  *
- * Uses synchronous file I/O (writeFileSync, readFileSync) to ensure
- * task state is persisted before returning placeholder to caller.
+ * Uses synchronous file I/O via the `@comis/observability` fs-safe
+ * substrate to ensure task state is persisted before returning a
+ * placeholder to the caller. Every write goes through `writeRegularFile`
+ * (file mode `0o600`) and every dir creation goes through
+ * `ensureContainedDir` (dir mode `0o700`), honoring file-mode invariants
+ * (files at `0o600`, dirs at `0o700`). `dataDir` is threaded as the `confinedBaseDir`
+ * ancestor-symlink defense.
  *
  * @module
  */
-import { mkdirSync, writeFileSync, readFileSync, readdirSync, statSync, unlinkSync, existsSync } from "node:fs";
+import { readFileSync, readdirSync, statSync, unlinkSync, existsSync } from "node:fs";
 import { safePath, systemNowMs } from "@comis/core";
+import { ensureContainedDir, writeRegularFile } from "@comis/observability";
 /** Directory name under data dir for background task state files. */
 export const TASK_DIR_NAME = "background-tasks";
 /**
@@ -37,14 +43,23 @@ function toPersistedState(task) {
 /**
  * Persist a task to disk synchronously.
  *
- * Writes to `dataDir/{agentId}/{taskId}.json`.
+ * Writes to `dataDir/{agentId}/{taskId}.json`. Routes through the
+ * `@comis/observability` fs-safe substrate so the parent dir lands at
+ * `0o700` and the file at `0o600` (file-mode invariants). `dataDir`
+ * is passed as `confinedBaseDir` for the ancestor-symlink defense.
+ *
+ * Result errors are intentionally swallowed — this writer's existing
+ * contract is best-effort persistence: a failure to persist must not
+ * propagate to the caller (which already returned a placeholder to the
+ * agent). The subsequent recovery scan will simply miss this task,
+ * matching the pre-migration semantics.
  */
 export function persistTaskSync(dataDir, task) {
     const agentDir = safePath(dataDir, task.origin.agentId);
-    mkdirSync(agentDir, { recursive: true });
+    ensureContainedDir({ dir: agentDir, mode: 0o700, confinedBaseDir: dataDir });
     const filePath = safePath(agentDir, `${task.id}.json`);
     const state = "_promise" in task ? toPersistedState(task) : task;
-    writeFileSync(filePath, JSON.stringify(state, null, 2), "utf-8");
+    writeRegularFile({ path: filePath, content: JSON.stringify(state, null, 2), confinedBaseDir: dataDir });
 }
 /**
  * Load a single task from disk.
@@ -121,7 +136,7 @@ export function recoverTasks(dataDir) {
                     task.status = "failed";
                     task.error = "Daemon restarted while task was running";
                     task.completedAt = systemNowMs();
-                    writeFileSync(filePath, JSON.stringify(task, null, 2), "utf-8");
+                    writeRegularFile({ path: filePath, content: JSON.stringify(task, null, 2), confinedBaseDir: dataDir });
                 }
                 recovered.push(task);
             }

package/node_modules/@comis/agent/dist/background/background-task-types.d.ts

@@ -55,7 +55,7 @@ export interface BackgroundTask {
     notificationPolicy?: BackgroundTaskNotificationPolicy;
     /** Live three-state session lifecycle. Optional; recovery defaults to
      *  "pending" when absent. The dispatcher inspects this before firing
-     *  notifyFn. */
+     *  fallbackNotifyFn. */
     dispatchState?: BackgroundSessionState;
     _promise?: Promise<unknown>;
     _abortController?: AbortController;
@@ -81,7 +81,7 @@ export interface PersistedTaskState {
     notificationPolicy?: BackgroundTaskNotificationPolicy;
     /**
      * Three-state session lifecycle. Optional; recovery defaults to "pending"
-     * when absent. The dispatcher inspects this before firing notifyFn.
+     * when absent. The dispatcher inspects this before firing fallbackNotifyFn.
      */
     dispatchState?: BackgroundSessionState;
 }

package/node_modules/@comis/agent/dist/background/completion-dispatcher.d.ts

@@ -87,11 +87,9 @@ export interface DispatcherTaskManager {
 /**
  * Dispatcher dependencies.
  *
- * Public minimum: `eventBus`, `taskManager`, `logger`. Tests use
- * `notifyFn`; production wires both `notifyFn` and `fallbackNotifyFn`
- * (they are aliases — the dispatcher prefers `fallbackNotifyFn` when
- * both are provided so production callers reading the daemon wiring
- * see the canonical name).
+ * Public minimum: `eventBus`, `taskManager`, `logger`. Production wires
+ * `fallbackNotifyFn` (the user-visible notification fired when the
+ * dispatcher cannot route to the originating session).
  *
  * `sessionStore` + `maxBackgroundHops` are optional. When absent, the
  * dispatcher falls back to the safe behavior: pending → dispatched
@@ -103,12 +101,9 @@ export interface CompletionDispatcherDeps {
     taskManager: DispatcherTaskManager;
     /**
      * User-visible notification fired when the dispatcher cannot route to
-     * the originating session. Either name accepted; `fallbackNotifyFn`
-     * preferred when both are provided.
+     * the originating session.
      */
     fallbackNotifyFn?: NotifyFn;
-    /** Alias for `fallbackNotifyFn` (test fixture compatibility). */
-    notifyFn?: NotifyFn;
     /** Active-session check (production wiring). When absent, the dispatcher
      *  defers to the runner without firing fallback. */
     sessionStore?: DispatcherSessionStore;

package/node_modules/@comis/agent/dist/background/completion-dispatcher.js

@@ -79,7 +79,7 @@ export const BackgroundTaskNotificationPolicy = {
  */
 export function createCompletionDispatcher(deps) {
     const log = deps.logger.child({ submodule: "completion-dispatcher" });
-    const fallback = deps.fallbackNotifyFn ?? deps.notifyFn;
+    const fallback = deps.fallbackNotifyFn;
     let stopped = false;
     let inflight = Promise.resolve();
     const onCompleted = (data) => {
@@ -178,7 +178,7 @@ export function createCompletionDispatcher(deps) {
                 // traceId from origin keeps log lines threaded.
                 traceId: task.origin?.traceId ?? undefined,
                 hint: "No fallbackNotifyFn wired; dispatcher cannot fire user-visible notification",
-            }, "Completion dispatcher: fallback skipped (no notifyFn)");
+            }, "Completion dispatcher: fallback skipped (no fallbackNotifyFn)");
             return;
         }
         try {

package/node_modules/@comis/agent/dist/background/completion-runner.d.ts

@@ -19,7 +19,7 @@
  * from `background_task:completed.timestamp` to this event for SLO tracking.
  *
  * Failure isolation: each handler is wrapped in suppressError so a single
- * completion's failure does not tear down the subscription (AGENTS §2.1).
+ * completion's failure does not tear down the subscription.
  *
  * @module
  */

package/node_modules/@comis/agent/dist/background/completion-runner.js

@@ -20,7 +20,7 @@
  * from `background_task:completed.timestamp` to this event for SLO tracking.
  *
  * Failure isolation: each handler is wrapped in suppressError so a single
- * completion's failure does not tear down the subscription (AGENTS §2.1).
+ * completion's failure does not tear down the subscription.
  *
  * @module
  */

package/node_modules/@comis/agent/dist/bootstrap/sections/autonomy-doctrine.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Autonomy doctrine: the one-paragraph, always-on contract + routing rule.
+ *
+ * Every top-level run (and every sub-agent / lockdown run) carries this
+ * paragraph in its bootstrap system prompt, even when the model never opens the
+ * full `autonomy` skill. It is the always-on floor; the bundled `autonomy` skill
+ * is the on-demand detail.
+ *
+ * The framing reflects current behavior: runs are revocable/clamped, NOT durable
+ * (no resume across a daemon restart). It names no introspection surface (no
+ * `whoami`, `capabilities.introspect`, or `comis-agent` CLI).
+ */
+/**
+ * Build the always-on autonomy doctrine section.
+ *
+ * Returns a heading-first `string[]`: the `## Autonomy` heading followed by
+ * one paragraph of prose (authored as concatenated fragments for readability)
+ * stating the routing rule, the delegate-then-synthesize rule (heavy/long/
+ * high-volume work goes to a fresh-window child, the lead synthesizes its
+ * returned summary + `ResultRef`), the autonomy envelope, the contract truth,
+ * and how to read a denial.
+ *
+ * The capability claim is PROFILE-CONDITIONAL by phrasing, not by plumbing: the
+ * opener says "When your agent profile grants autonomy capabilities (the
+ * `standard` default does; `assistant` does not), you can …" so the always-on
+ * paragraph stays accurate for EVERY resolved profile — including `assistant`
+ * (`enabled:false, capabilities:[]`, `schema-agent-autonomy.ts`) — without
+ * threading the resolved posture through `AssemblerParams`. This keeps the
+ * single universal paragraph (it rides every bootstrap prompt) while avoiding
+ * the over-claim a categorical "You can spawn sub-agents …" would make for an
+ * `assistant`-profile agent that holds none of those caps.
+ *
+ * Registered in `SECTIONS` with `MODES_ALL_PLUS_COMPACT`
+ * (the same membership `identity`/`safety` use), placed after `language` so it
+ * lands in the semi-stable body and does not disturb the cache-block
+ * boundaries (`computeBlockBoundaries`).
+ */
+export declare function buildAutonomyDoctrineSection(): string[];

package/node_modules/@comis/agent/dist/bootstrap/sections/autonomy-doctrine.js

@@ -0,0 +1,63 @@
+// SPDX-License-Identifier: Apache-2.0
+/**
+ * Autonomy doctrine: the one-paragraph, always-on contract + routing rule.
+ *
+ * Every top-level run (and every sub-agent / lockdown run) carries this
+ * paragraph in its bootstrap system prompt, even when the model never opens the
+ * full `autonomy` skill. It is the always-on floor; the bundled `autonomy` skill
+ * is the on-demand detail.
+ *
+ * The framing reflects current behavior: runs are revocable/clamped, NOT durable
+ * (no resume across a daemon restart). It names no introspection surface (no
+ * `whoami`, `capabilities.introspect`, or `comis-agent` CLI).
+ */
+/**
+ * Build the always-on autonomy doctrine section.
+ *
+ * Returns a heading-first `string[]`: the `## Autonomy` heading followed by
+ * one paragraph of prose (authored as concatenated fragments for readability)
+ * stating the routing rule, the delegate-then-synthesize rule (heavy/long/
+ * high-volume work goes to a fresh-window child, the lead synthesizes its
+ * returned summary + `ResultRef`), the autonomy envelope, the contract truth,
+ * and how to read a denial.
+ *
+ * The capability claim is PROFILE-CONDITIONAL by phrasing, not by plumbing: the
+ * opener says "When your agent profile grants autonomy capabilities (the
+ * `standard` default does; `assistant` does not), you can …" so the always-on
+ * paragraph stays accurate for EVERY resolved profile — including `assistant`
+ * (`enabled:false, capabilities:[]`, `schema-agent-autonomy.ts`) — without
+ * threading the resolved posture through `AssemblerParams`. This keeps the
+ * single universal paragraph (it rides every bootstrap prompt) while avoiding
+ * the over-claim a categorical "You can spawn sub-agents …" would make for an
+ * `assistant`-profile agent that holds none of those caps.
+ *
+ * Registered in `SECTIONS` with `MODES_ALL_PLUS_COMPACT`
+ * (the same membership `identity`/`safety` use), placed after `language` so it
+ * lands in the semi-stable body and does not disturb the cache-block
+ * boundaries (`computeBlockBoundaries`).
+ */
+export function buildAutonomyDoctrineSection() {
+    return [
+        "## Autonomy",
+        "",
+        "When your agent profile grants autonomy capabilities (the `standard` default does; `assistant` " +
+            "does not), you can act on your own within a bounded envelope: spawn sub-agents, run DAGs, " +
+            "schedule your own cron jobs, research the web, and message your origin channel — all " +
+            "budget-capped, rate-limited, and revocable (long runs may be clamped or stopped, and do not " +
+            "resume across a daemon restart). Route by shape: a single step is a direct tool call; a " +
+            "multi-step read/fetch/synthesize/fan-out chain is one `orchestrate(script)` turn. Route by " +
+            "weight too: delegate heavy, long-running, or high-volume work to a fresh-window child via " +
+            "`sessions_spawn` — each child runs an isolated context with its own budget and returns a " +
+            "bounded summary plus a `ResultRef` handle to its full output, which you then synthesize " +
+            "(drilling into the `ResultRef` on demand) rather than doing the heavy work inline and " +
+            "burning your own window. A `coordinator`-role lead MUST delegate such work (it holds only " +
+            "the orchestration surface); any other autonomy-bearing agent SHOULD, to keep its window " +
+            "lean. You are " +
+            "confined to your workspace; you cannot read secrets, mint tokens, change config, or reach the " +
+            "control plane — don't try. A `CapabilityDeniedError` — or any quota, budget, or rate-limit " +
+            "denial — means you lack that capability or hit a ceiling: adapt or report — do not retry the " +
+            "same blocked call in a loop. (Under an unattended profile the platform escalates a blocked " +
+            "irreversible action to your operator for you; you still adapt and continue, you do not wait on " +
+            "it.)",
+    ];
+}

package/node_modules/@comis/agent/dist/bootstrap/sections/context-sections.d.ts

@@ -24,6 +24,8 @@ export interface SubagentRoleParams {
     parentSummary?: string;
     /** Map of all registered agent IDs to their workspace directories. */
     agentWorkspaces?: Record<string, string>;
+    /** Inherited conversation language for non-en user-facing output. */
+    language?: string;
 }
 /**
  * Build the Task Planning section for the Silent Execution Planner.
@@ -36,6 +38,31 @@ export interface SubagentRoleParams {
  * @returns Lines for the section, or empty array if disabled
  */
 export declare function buildTaskPlanningSection(sepEnabled: boolean, isMinimal: boolean): string[];
+/**
+ * Build the Compressed-context uncertainty clause. Included in the
+ * cache-stable system prompt whenever the DAG (LCD) engine is enabled
+ * (`dagModeEnabled`), so the model knows its context may contain LOSSY,
+ * untrusted summaries and treats them as compressed recall cues -- not proof.
+ *
+ * **Mode-gated, NOT per-turn.** The clause is gated on the per-session
+ * `contextEngine.version === "dag"` (a stable, operator-only config value),
+ * NOT on whether a summary is literally present this turn. dag mode guarantees
+ * summaries WILL appear once history grows past `contextThreshold`, so
+ * mode-gating is correct-enough AND keeps the system-prompt prefix cache-stable
+ * (gating on per-turn store state would thrash the Anthropic prompt cache on
+ * every compaction). Mirrors `buildMemoryRecallSection`'s capability-gate shape.
+ *
+ * The marker vocabulary here (`trust=untrusted`, `depth`, `descendant_count`,
+ * the time-range, and the "Expand for details about:" footer) MUST match what
+ * the LCD assembler actually renders around each summary (`lcd-assembler.ts`
+ * `summaryRefToMessage`). The recovery TOOLS (`ctx_*`) are deliberately NOT
+ * named here.
+ *
+ * @param dagModeEnabled - true when `contextEngine.version === "dag"`
+ * @param isMinimal - minimal (sub-agent) prompt mode
+ * @returns Lines for the section, or empty array if disabled
+ */
+export declare function buildLossinessUncertaintySection(dagModeEnabled: boolean, isMinimal: boolean): string[];
 export declare function buildPersonaSection(files: BootstrapContextFile[]): string[];
 export declare function buildProjectContextSection(files: BootstrapContextFile[], _isMinimal: boolean, excludeFiles?: Set<string>, workspaceProfile?: "full" | "specialist"): string[];
 export declare function buildPostCompactionRecoverySection(files: BootstrapContextFile[], isMinimal: boolean, sectionNames?: string[]): string[];

package/node_modules/@comis/agent/dist/bootstrap/sections/context-sections.js

@@ -7,6 +7,7 @@ import { extractMarkdownSections, MAX_POST_COMPACTION_CHARS } from "../section-e
 import { TEMPLATE_MARKER } from "../../workspace/templates.js";
 // ---------------------------------------------------------------------------
 // Task Planning (SEP system prompt section -- static, cache-stable)
+// SEP = Silent Execution Planner.
 // ---------------------------------------------------------------------------
 /**
  * Build the Task Planning section for the Silent Execution Planner.
@@ -31,7 +32,46 @@ export function buildTaskPlanningSection(sepEnabled, isMinimal) {
     ];
 }
 // ---------------------------------------------------------------------------
-// 16a. Persona (SOUL.md promoted to standalone section before Safety)
+// Compressed context (lossiness/uncertainty clause -- static, cache-stable)
+// ---------------------------------------------------------------------------
+/**
+ * Build the Compressed-context uncertainty clause. Included in the
+ * cache-stable system prompt whenever the DAG (LCD) engine is enabled
+ * (`dagModeEnabled`), so the model knows its context may contain LOSSY,
+ * untrusted summaries and treats them as compressed recall cues -- not proof.
+ *
+ * **Mode-gated, NOT per-turn.** The clause is gated on the per-session
+ * `contextEngine.version === "dag"` (a stable, operator-only config value),
+ * NOT on whether a summary is literally present this turn. dag mode guarantees
+ * summaries WILL appear once history grows past `contextThreshold`, so
+ * mode-gating is correct-enough AND keeps the system-prompt prefix cache-stable
+ * (gating on per-turn store state would thrash the Anthropic prompt cache on
+ * every compaction). Mirrors `buildMemoryRecallSection`'s capability-gate shape.
+ *
+ * The marker vocabulary here (`trust=untrusted`, `depth`, `descendant_count`,
+ * the time-range, and the "Expand for details about:" footer) MUST match what
+ * the LCD assembler actually renders around each summary (`lcd-assembler.ts`
+ * `summaryRefToMessage`). The recovery TOOLS (`ctx_*`) are deliberately NOT
+ * named here.
+ *
+ * @param dagModeEnabled - true when `contextEngine.version === "dag"`
+ * @param isMinimal - minimal (sub-agent) prompt mode
+ * @returns Lines for the section, or empty array if disabled
+ */
+export function buildLossinessUncertaintySection(dagModeEnabled, isMinimal) {
+    if (isMinimal || !dagModeEnabled)
+        return [];
+    return [
+        "## Compressed context",
+        "Some earlier turns in your context are shown as LOSSY summaries, marked `trust=untrusted` with a `depth`, a `descendant_count`, and a time-range. Deeper summaries (higher `depth`) are summaries-of-summaries and are even lossier.",
+        "Treat summaries as compressed recall cues, NOT proof.",
+        "Do NOT assert exact commands, SHAs, file paths, numbers, or timestamps from a summary -- those details may be lossy or absent.",
+        "Prefer newer, verbatim evidence over a summary when they conflict.",
+        "A summary's `Expand for details about:` footer describes what was compressed; the underlying detail is preserved losslessly in the store.",
+    ];
+}
+// ---------------------------------------------------------------------------
+// Persona (SOUL.md promoted to a standalone section before Safety)
 // ---------------------------------------------------------------------------
 export function buildPersonaSection(files) {
     const soul = files.find((f) => f.path.toLowerCase() === "soul.md");
@@ -92,7 +132,7 @@ const SPECIALIST_AGENTS_MD = `# Platform Instructions (Specialist)
 - Use structured output as defined in ROLE.md
 - Be concise — you're a specialist worker, not a conversationalist`;
 // ---------------------------------------------------------------------------
-// 16. Project Context (include in minimal)
+// Project Context (included in minimal mode)
 // ---------------------------------------------------------------------------
 export function buildProjectContextSection(files, _isMinimal, excludeFiles, workspaceProfile) {
     if (files.length === 0)
@@ -128,7 +168,7 @@ export function buildProjectContextSection(files, _isMinimal, excludeFiles, work
     return lines;
 }
 // ---------------------------------------------------------------------------
-// 16a-post. Post-Compaction Recovery (skip if minimal or no AGENTS.md)
+// Post-Compaction Recovery (skipped if minimal or no AGENTS.md)
 // ---------------------------------------------------------------------------
 export function buildPostCompactionRecoverySection(files, isMinimal, sectionNames) {
     if (isMinimal)
@@ -156,7 +196,7 @@ export function buildPostCompactionRecoverySection(files, isMinimal, sectionName
     ];
 }
 // ---------------------------------------------------------------------------
-// 17. Subagent Context (only for sub-agents / minimal mode)
+// Subagent Context (only for sub-agents / minimal mode)
 // ---------------------------------------------------------------------------
 export function buildSubagentContextSection(extraSystemPrompt) {
     if (!extraSystemPrompt)
@@ -164,7 +204,7 @@ export function buildSubagentContextSection(extraSystemPrompt) {
     return ["## Additional Context", extraSystemPrompt];
 }
 // ---------------------------------------------------------------------------
-// 18. Subagent Role (only for sub-agents -- structured replacement for buildSubagentContextSection)
+// Subagent Role (only for sub-agents -- structured replacement for buildSubagentContextSection)
 // ---------------------------------------------------------------------------
 export function buildSubagentRoleSection(params) {
     if (!params)
@@ -181,6 +221,9 @@ export function buildSubagentRoleSection(params) {
         `You are NOT the ${parentLabel}. Do not try to be.`,
     ];
     // --- New enriched sections (inserted BEFORE Rules) ---
+    if (params.language && params.language !== "en") {
+        lines.push("", "### Language", `Produce all user-facing output in ${params.language} (the conversation language). Code, identifiers, and file paths stay verbatim.`);
+    }
     if (params.objective) {
         lines.push("", "### Objective", `Your primary objective: ${params.objective}`, "Stay focused on this objective throughout your execution. If you lose context due to compaction, re-read this section.");
     }

package/node_modules/@comis/agent/dist/bootstrap/sections/index.d.ts

@@ -1,4 +1,5 @@
 export * from "./core-sections.js";
+export * from "./autonomy-doctrine.js";
 export * from "./tooling-sections.js";
 export * from "./tool-descriptions.js";
 export * from "./skills-memory-sections.js";

package/node_modules/@comis/agent/dist/bootstrap/sections/index.js

@@ -1,5 +1,6 @@
 // SPDX-License-Identifier: Apache-2.0
 export * from "./core-sections.js";
+export * from "./autonomy-doctrine.js";
 export * from "./tooling-sections.js";
 export * from "./tool-descriptions.js";
 export * from "./skills-memory-sections.js";

package/node_modules/@comis/agent/dist/bootstrap/sections/skills-memory-sections.js

@@ -69,6 +69,9 @@ export function buildMemoryRecallSection(hasMemoryTools, isMinimal) {
         "If memory_search returns relevant results, use them in your answer.",
         "If memory_search returns no results, answer based on available context. Do not mention that you searched.",
         "",
+        "### The Current Conversation Is Authoritative",
+        "Recalled memories and `memory_search` results come from PAST conversations and may be OUTDATED. When a recalled fact conflicts with what the user has stated in the CURRENT conversation, the current conversation always takes precedence — never override a fresh statement with a stale memory. Treat recalled memories as background context, not as ground truth: if the user gave a value (a codeword, a name, a preference, a number) earlier in THIS conversation, use that value even if memory recalls a different one from before.",
+        "",
         "### Tools",
         '- **memory_search**: Search past conversations and stored facts. Use natural language queries (e.g., "user\'s timezone preference" not just "timezone").',
         '- **memory_store**: Save facts, preferences, decisions, and context for future recall. Use tags for categorization (e.g., ["preference"], ["project"]).',

package/node_modules/@comis/agent/dist/bootstrap/sections/tool-descriptions.d.ts

@@ -16,12 +16,11 @@
  *
  * @module
  */
-import type { ModelTier } from "./tooling-sections.js";
 /** Context for dynamic tool description builders. */
 export interface ToolDescriptionContext {
     channelType?: string;
     trustLevel?: string;
-    modelTier: ModelTier;
+    modelTier: "small" | "medium" | "large";
 }
 /** Terse 5-8 word summaries for system prompt "Available Tools" listing. */
 export declare const TOOL_SUMMARIES: Record<string, string>;

package/node_modules/@comis/agent/dist/bootstrap/sections/tool-descriptions.js

@@ -77,11 +77,6 @@ export const TOOL_SUMMARIES = {
     telegram_action: "Perform actions on Telegram platform",
     slack_action: "Perform actions on Slack platform",
     whatsapp_action: "Perform actions on WhatsApp platform",
-    // Context
-    ctx_search: "Search current context window entries",
-    ctx_inspect: "Inspect individual context entry details",
-    ctx_expand: "Expand compressed or summarized entries",
-    ctx_recall: "Recall evicted context by query",
     // Privileged / Supervisor
     agents_manage: "Manage full agent fleet (admin)",
     obs_query: "Query platform diagnostics data (admin)",
@@ -151,11 +146,6 @@ export const LEAN_TOOL_DESCRIPTIONS = {
     telegram_action: "Telegram actions: pin, poll, sticker, chat info, admin, topics.",
     slack_action: "Slack actions: pin, topic, archive, channels, invites.",
     whatsapp_action: "WhatsApp actions: group management, participants, settings.",
-    // ----- Context -----
-    ctx_search: "Search context window for matching entries by query.",
-    ctx_inspect: "Inspect detailed metadata of a context entry by ID.",
-    ctx_expand: "Expand a compressed or summarized context entry to full content.",
-    ctx_recall: "Recall evicted context entries by semantic query.",
     // ----- Privileged / Supervisor (dynamic: admin suffix) -----
     agents_manage: (ctx) => {
         const base = "Manage agent fleet: list, create, get, update, delete, suspend, resume. For batch creation, pass workspace.role/identity inline to skip the 2-step write flow.";
@@ -214,11 +204,10 @@ export const LEAN_TOOL_DESCRIPTIONS = {
 export const TOOL_ORDER = [
     // Start (high-frequency): file ops, messaging, memory, web
     "read", "edit", "notebook_edit", "write", "exec", "message", "memory_search", "web_search",
-    // Middle (low-frequency): platform actions, privileged, context, media
+    // Middle (low-frequency): platform actions, privileged, media
     "discord_action", "telegram_action", "slack_action", "whatsapp_action",
     "agents_manage", "obs_query", "sessions_manage", "memory_manage",
     "channels_manage", "tokens_manage", "models_manage", "providers_manage", "skills_manage", "mcp_manage", "heartbeat_manage",
-    "ctx_search", "ctx_inspect", "ctx_expand", "ctx_recall",
     "image_analyze", "tts_synthesize", "transcribe_audio", "describe_video", "extract_document",
     "browser", "gateway",
     // End (medium-frequency): file nav, sessions, process, cron
@@ -439,9 +428,15 @@ IMPORTANT: Never modify config YAML files directly -- always use gateway tool ac
 ## Credential Discovery
 When the user asks to install, configure, or connect something that requires an API key, token, secret, or credential: call gateway(action:"env_list", filter:"<PATTERN>*") BEFORE asking the user. env_list returns only NAMES (never values), so it is safe to call proactively. Only ask the user for the credential if env_list returns no matching name. Use filter patterns like "GEMINI*", "OPENAI*", or "*_API_KEY" to narrow the search.
 ## MCP Output Directory
-When installing or invoking an MCP server that writes files (images, audio, documents): outputs must land inside the workspace so message.attach and exec can reach them. If the MCP exposes an output-dir env var (common: OUTPUT_DIR, OUTPUT_PATH, SAVE_PATH, DATA_DIR), set it via gateway(action:"patch") to ~/.comis/workspace/output/<mcp-server-name>/. If the MCP takes an output path per tool call, always pass a path under that directory. Server names must match /^[a-zA-Z0-9_-]+$/ -- no dots, slashes, or whitespace. The daemon auto-creates the directory and sets stdio MCP cwd to it, so MCPs writing to "." are safe by default; MCPs that hardcode absolute paths (e.g., ~/Documents, /tmp) will escape the workspace.`,
+When installing or invoking an MCP server that writes files (images, audio, documents): outputs must land inside the workspace so message.attach and exec can reach them. If the MCP exposes an output-dir env var (common: OUTPUT_DIR, OUTPUT_PATH, SAVE_PATH, DATA_DIR), set it via gateway(action:"patch") to ~/.comis/workspace/output/<mcp-server-name>/. If the MCP takes an output path per tool call, always pass a path under that directory. Server names must match /^[a-zA-Z0-9_-]+$/ -- no dots, slashes, or whitespace. The daemon auto-creates the directory and sets stdio MCP cwd to it, so MCPs writing to "." are safe by default; MCPs that hardcode absolute paths (e.g., ~/Documents, /tmp) will escape the workspace.
+## Installing an MCP server
+Use mcp_manage as the canonical entry point for MCP server install / inspect / remove. Call discover_tools({query: "mcp_manage"}) first if you need a discovery pointer to its schema. NEVER use gateway(action:"patch") against integrations.mcp.servers — that path bypasses credential validation and produces invalid config. If mcp_manage is unavailable, report the limitation; do NOT improvise with gateway.
+Single mcp.servers entry shape: {name, transport, command?, args?, url?, env?, cwd?, enabled?: true, headers?, maxConcurrency?}. README-style mcpServers maps use <id> as the JSON-object key — when migrating those into integrations.mcp.servers (an array), move the <id> into the name field and DROP UI-only fields like label.`,
     channels_manage: `## Channel Management Side Effects
 Enable, disable, and configure actions persist to config.yaml and trigger daemon restart. Current execution terminates after the tool returns. Batch changes together and warn the user before proceeding.`,
+    mcp_manage: `Use mcp_manage as the canonical path for MCP server connect, disconnect, and status. A Validation failed result means fix the arguments — not abandon the tool or switch to gateway.
+## OAuth-required MCP servers
+When mcp_manage(action:"connect", url:..., transport:"http") returns an Unauthorized error or a structured needs_oauth_login action hint, the server requires OAuth. Retry as: mcp_manage(action:"connect", auth:"oauth", url:..., transport:"http"). If the daemon then responds with a needs_oauth_login action, invoke mcp_login({server_name}) to start the PKCE flow. mcp_login returns a verification URL — deliver it to the user via the message tool BEFORE starting any background polling. Do NOT curl device-code endpoints. Do NOT write tokens to the workspace. Do NOT call gateway(action:"patch") against integrations.mcp.servers. For RFC 8628 device-flow servers (when mcp_login returns status:"device_code_pending"), deliver BOTH the verificationUri AND the userCode to the user via the message tool in the form \`Verification URL: <verificationUri>\\nCode: <userCode>\` BEFORE waiting for the poll to complete. Do NOT continue with other tool calls until the operator has had time to authorize at the verification URL.`,
     exec: `## Exec Guide
 IMPORTANT: Do NOT use exec for operations that have dedicated tools:
 - File reading -> use read tool (not cat/head/tail/less)

package/node_modules/@comis/agent/dist/bootstrap/sections/tooling-sections.d.ts

@@ -2,8 +2,6 @@
  * Tooling section builders: tool listing, tool call style, self-update gating,
  * and compacted output recovery.
  */
-/** Model size tier — determines prompt verbosity for tool descriptions. */
-export type ModelTier = "small" | "medium" | "large";
 /**
  * Build the residual one-liner pointing the model at the per-turn
  * `## Capabilities` block. The capability-index is now the only path.
@@ -11,7 +9,7 @@ export type ModelTier = "small" | "medium" | "large";
  * The wording below is normative — the per-turn `## Capabilities` block is
  * rendered into the dynamic preamble by `executor-prompt-runner.ts`.
  */
-export declare function buildToolingSection(toolNames: string[], _modelTier: ModelTier, _toolSummaries?: Record<string, string>): string[];
+export declare function buildToolingSection(toolNames: string[], _modelTier: "small" | "medium" | "large", _toolSummaries?: Record<string, string>): string[];
 /**
  * Build the static "## Tool Call Style" section with conditional coding guidelines.
  *

package/node_modules/@comis/agent/dist/bootstrap/sections/tooling-sections.js

@@ -4,6 +4,9 @@
  * and compacted output recovery.
  */
 import { getProviders } from "@earendil-works/pi-ai";
+// ---------------------------------------------------------------------------
+// 3. Tooling (include in minimal)
+// ---------------------------------------------------------------------------
 /**
  * Build the residual one-liner pointing the model at the per-turn
  * `## Capabilities` block. The capability-index is now the only path.
@@ -74,10 +77,10 @@ export function buildToolCallStyleSection(isMinimal, toolNames = []) {
         // because the first read sets the default; the second is the install
         // fallback. Capability-index is always on.
         guidelines.push("- **Tool-first principle.** When this turn includes a `Capabilities` context and the task can be satisfied by a connected tool or available skill, prefer that capability over installing a Python or Node package. Use installs only for capabilities not covered by active tools, deferred tools, or visible prompt skills.");
-        guidelines.push("- **Python projects:** Always create a virtualenv per project (`python3 -m venv .venv`). "
-            + "Install packages into the project venv (`source .venv/bin/activate && pip install ...`). "
-            + "Never use `--break-system-packages` — it pollutes the system Python. "
-            + "Each project directory should have its own `.venv`.");
+        guidelines.push("- **Python projects:** Create a project virtualenv with `python3 -m venv .venv`, then call "
+            + "`.venv/bin/python3` and `.venv/bin/pip install <pkgs>` directly. "
+            + "Do not source the venv activate script — the exec sandbox blocks shell-source. "
+            + "Never use `--break-system-packages`. Each project gets its own `.venv`.");
     }
     if (guidelines.length > 0) {
         lines.push("", "### Coding Guidelines", ...guidelines);