@capybara-hq/kernel 0.1.0-rc.1 → 0.1.0-rc.11

package/dist/runtime/context/build.js

@@ -1,7 +1,14 @@
 import { createHash } from "node:crypto";
 import { MEDIA_LIMITS, } from "@capybara-hq/plugin-sdk";
+import { renderBackgroundFinished } from "../../background/render.js";
+import { isAbsorbable, } from "../../conversations/events.js";
 import { catalogText, isAlwaysLoaded } from "../../tools/builtins/tool-search.js";
-import { invokedSkillNames, invokedSkillsText, skillsCatalogEvents, snapshotChangeText, snapshotCurrentText, snapshotSystemText, systemSkillsCatalog, } from "./skills.js";
+import { renderSubagentDelivery } from "../subagents/render.js";
+import { environmentPathsAt, environmentPathsText } from "./environment-paths.js";
+import { LEGACY_CATALOG_HEADER, LEGACY_SKILL_TEXTS, usesLegacyToolNames } from "./legacy-text.js";
+import { currentRunContext, runContextEvents, runContextFullText, runContextText, senderLines, } from "./run-context.js";
+import { invokedSkillNames, invokedSkillsText, SKILL_TEXTS, skillsCatalogEvents, snapshotChangeText, snapshotCurrentText, snapshotSystemText, systemSkillsCatalog, } from "./skills.js";
+import { toolsChangedText } from "./tool-changes.js";
 /**
  * 平台行为规范（模型可见，英文）。短而通用（spec 6 原则 5）；不放时间戳、会话 ID 等会变化的内容，
  * 保证同一 agent 版本在所有会话中 system 前缀一致、可命中提示词缓存。改动它会让所有缓存失效。
@@ -322,17 +329,24 @@ export function summaryText(summary) {
  * 由会话事件日志 + agent 定义构建模型请求（纯函数，不做 I/O）。
  * - system：`BEHAVIOR_RULES + "\n\n" + agent.instructions` 一个块，打缓存断点（a sub-agent's log:
  *   `BEHAVIOR_RULES`, its preamble and its instructions, all from its `subagent_started`）；日志里第一份 `skills_catalog`
- *   快照在任何 `model_call` 之前时，技能目录接在这个块末尾（Ruling M17，见 ./skills.ts）；启用 tool_search 时
+ *   快照在任何 `model_call` 之前时，技能目录接在这个块末尾（Ruling M17，见 ./skills.ts）；启用 ToolSearch 时
  *   第二个块是工具目录（见 {@link BuildModelRequestInput.toolSearch}）；
  * - 之后的 `skills_catalog` 在所在位置渲染为 system 变更提醒；被压缩摘要覆盖的，若摘要时生效的目录与 system 里的
  *   不同，紧随摘要补一条完整的当前目录；
  * - messages：最近一条摘要（若有）作为首条 user 消息，其后按 seq 回放 `coversUpToSeq` 之后的
  *   `user_message` / `assistant_message`（content 原样，含 opaque；aborted 的也回放；媒体引用按
  *   {@link resolveMedia} 换成 base64 或文字占位）/ `reminder`
- *   （`role: "system"`，放在它所在的位置）；`tool_result` 事件还原为紧随其 assistant 消息之后的一条 user 消息
+ *   （`role: "system"`，放在它所在的位置）/ `tools_changed` (`role: "system"`, the text of {@link toolsChangedText}, at its position) /
+ *   `environment_paths` (`role: "system"` at its position, `environmentPathsText`; covered by the
+ *   summary: the latest one follows the summary) /
+ *   `run_context` (`role: "system"` at its position, `runContextText`; covered by the summary: the
+ *   current context follows the summary whole; a user message's sender line by `senderLines`) /
+ *   `background_task_finished`（`role: "system"`, the text of
+ *   {@link renderBackgroundFinished}, placed like a user_message）/ `subagent_delivery` (likewise,
+ *   the text of {@link renderSubagentDelivery})；`tool_result` 事件还原为紧随其 assistant 消息之后的一条 user 消息
  *   （同一步的多个结果合并，按该 assistant 消息里 tool_call 的顺序；找不到对应调用的结果不进请求）。
  *   其他事件不进请求。提供 `absorbedUpToSeq` 时，
- *   尚未被吸收的 user_message 不进请求，运行中途到达的插话放在吸收它的调用处（见 BuildModelRequestInput）。
+ *   尚未被吸收的可吸收事件不进请求，运行中途到达的放在吸收它的调用处（见 BuildModelRequestInput）。
  * 只追加：新事件只会在 messages 末尾追加；唯一的前缀变化来自新的压缩摘要。
  * `step` 与 `agentVersion` 不进请求内容（保证缓存前缀稳定），由调用方写入 `model_call` 事件。
  */
@@ -377,7 +391,7 @@ export function buildModelRequest(input) {
             lastCall = absorbedBy(e);
     }
     /**
-     * 第 i 个事件（user_message）的放置方式：
+     * 第 i 个事件（可吸收事件：user_message / background_task_finished / subagent_delivery）的放置方式：
      * - `inline`：在吸收它的调用（之后第一个 `absorbedBy ≥ seq` 的 model_call，或本次请求）之前，
      *   没有「由未吸收它的调用生成的回复」→ 按 seq 原位回放（常规情况，与不提供 absorbedUpToSeq 时一致）；
      * - `deferred`：它之后有非空 assistant_message 是由一次没有吸收它的 model_call 生成的（它在那一步
@@ -455,14 +469,38 @@ export function buildModelRequest(input) {
         }
         racedPending = racedPending.filter((x) => x.seq > toSeq);
     };
-    /** A user message's blocks, with its fork report when it has one. */
+    /** Run context spec §4: the sender lines, by the messages after the summary boundary. */
+    const senders = senderLines(events, after);
+    /**
+     * A user message's blocks: its sender line first when the sender changed (a separate block, so
+     * `content[0]` stays the typed text), then its own blocks, then its fork report when it has one.
+     */
     const userBlocks = (u) => {
         const report = forkReports.get(u.seq);
+        const line = senders.get(u.seq);
         const blocks = blocksOf(u.payload.content);
-        return report === undefined ? blocks : [...blocks, { type: "text", text: report }];
+        return [
+            ...(line === undefined ? [] : [{ type: "text", text: line }]),
+            ...blocks,
+            ...(report === undefined ? [] : [{ type: "text", text: report }]),
+        ];
     };
-    /** 被某次模型调用跳过（运行中途到达）、尚未被吸收的 user_message，按 seq 升序。 */
+    /** 被某次模型调用跳过（运行中途到达）、尚未被吸收的可吸收事件，按 seq 升序。 */
     let deferred = [];
+    /**
+     * An absorbable event as a request message: a user turn, or the system text of a finished task
+     * or a sub-agent's delivery.
+     */
+    const absorbableMessage = (e) => {
+        switch (e.type) {
+            case "user_message":
+                return { role: "user", content: userBlocks(e) };
+            case "background_task_finished":
+                return { role: "system", content: renderBackgroundFinished(e.payload) };
+            case "subagent_delivery":
+                return { role: "system", content: renderSubagentDelivery(e.payload) };
+        }
+    };
     /**
      * 把已被吸收（seq ≤ upTo）的延后消息按 seq 顺序放进 messages，插在末尾连续的 system 提醒之前
      * （若有）。这样某一步自己写在 model_call 之前的提醒（含收尾提醒）仍排在它所跟随的用户消息之后，
@@ -476,7 +514,7 @@ export function buildModelRequest(input) {
         let at = messages.length;
         while (at > 0 && messages[at - 1]?.role === "system")
             at--;
-        messages.splice(at, 0, ...ready.map((u) => ({ role: "user", content: userBlocks(u) })));
+        messages.splice(at, 0, ...ready.map(absorbableMessage));
     };
     /** (runId, callId) → 该调用的 tool_result 事件（同一调用只取第一个）。 */
     const results = new Map();
@@ -488,6 +526,10 @@ export function buildModelRequest(input) {
         if (!results.has(k))
             results.set(k, e.payload);
     }
+    // System texts naming a builtin: a request whose tools were recorded before the tool rename
+    // renders the frozen pre-rename wording, so it rebuilds exactly (tool naming spec §10)
+    const legacyNames = usesLegacyToolNames(input.tools ?? []);
+    const skillTexts = legacyNames ? LEGACY_SKILL_TEXTS : SKILL_TEXTS;
     // 技能目录（Ruling M17）：第一份快照进 system；之后的每份在所在位置追加变更提醒（相对上一份快照）。
     const skillSnaps = skillsCatalogEvents(events);
     const systemSkills = systemSkillsCatalog(events);
@@ -500,37 +542,52 @@ export function buildModelRequest(input) {
             role: "user",
             content: [{ type: "text", text: summaryText(summary.payload.text) }],
         });
+        // run context spec §5: snapshots covered by the summary are not rendered; the context in
+        // effect at the summary's boundary follows it whole
+        if (runContextEvents(events).some((e) => e.seq <= after)) {
+            messages.push({
+                role: "system",
+                content: runContextFullText(currentRunContext(events, after)),
+            });
+        }
+        // environments spec §13.1: the instance's directories told before the boundary follow the
+        // summary again (the model keeps using the real paths)
+        const paths = environmentPathsAt(events, after);
+        if (paths) {
+            messages.push({ role: "system", content: environmentPathsText(paths.payload.roots) });
+        }
         // 被摘要覆盖的变更提醒不再发送：摘要时生效的目录与 system 里的不同 → 紧随摘要补上完整的当前目录
         const covered = skillSnaps.filter((e) => e.seq <= after).at(-1);
         // (phase B: plus the current pinned skills and tool-name map when they differ from system's)
         if (covered && covered !== systemSkills) {
-            const text = snapshotCurrentText(systemSkills?.payload, covered.payload);
+            const text = snapshotCurrentText(systemSkills?.payload, covered.payload, skillTexts);
             if (text !== "")
                 messages.push({ role: "system", content: text });
         }
         // phase D: the skills a person invoked in the summarised range, by name (from the log only)
-        const invoked = invokedSkillsText(invokedSkillNames(events, after));
+        const invoked = invokedSkillsText(invokedSkillNames(events, after), skillTexts);
         if (invoked !== "")
             messages.push({ role: "system", content: invoked });
     }
     for (const [i, e] of events.entries()) {
         if (e.seq <= after)
             continue;
+        if (isAbsorbable(e)) {
+            switch (absorbed === undefined ? "inline" : placement(i, e.seq)) {
+                case "inline":
+                    // seq 更小的延后事件被同一次或更早的调用吸收：先放它们，保持发送顺序。
+                    flush(e.seq - 1);
+                    messages.push(absorbableMessage(e));
+                    break;
+                case "deferred":
+                    deferred.push(e);
+                    break;
+                default:
+                    break;
+            }
+            continue;
+        }
         switch (e.type) {
-            case "user_message":
-                switch (absorbed === undefined ? "inline" : placement(i, e.seq)) {
-                    case "inline":
-                        // seq 更小的延后消息被同一次或更早的调用吸收：先放它们，保持用户消息的发送顺序。
-                        flush(e.seq - 1);
-                        messages.push({ role: "user", content: userBlocks(e) });
-                        break;
-                    case "deferred":
-                        deferred.push(e);
-                        break;
-                    default:
-                        break;
-                }
-                break;
             case "model_call":
                 emitRaced(e.payload.request.toSeq);
                 if (absorbed !== undefined)
@@ -562,6 +619,21 @@ export function buildModelRequest(input) {
                 messages.push({ role: "system", content: e.payload.text });
                 reminderSeqs.push(e.seq);
                 break;
+            // the tool set changed since the previous request (tool naming spec §9.1); one covered by
+            // the summary is dropped: the request's tool list is current anyway
+            case "tools_changed":
+                messages.push({ role: "system", content: toolsChangedText(e.payload) });
+                break;
+            // who the agent is and the facts of the day (run context spec §4): the first snapshot whole,
+            // a later one as the changes against the fold before it
+            case "run_context":
+                messages.push({ role: "system", content: runContextText(events, e) });
+                break;
+            // the instance's directories (environments spec §13.1): logged during a step's tool call,
+            // so rendered after that step's tool results
+            case "environment_paths":
+                messages.push({ role: "system", content: environmentPathsText(e.payload.roots) });
+                break;
             // hook_denied is not model-visible: the model sees only the denied tool call's tool_result
             // (and nothing for a denied model request), so request building skips it
             case "hook_denied":
@@ -588,7 +660,7 @@ export function buildModelRequest(input) {
                 break;
             case "skills_catalog":
                 if (e !== systemSkills) {
-                    const text = snapshotChangeText(prevSnapshot.get(e.seq), e.payload);
+                    const text = snapshotChangeText(prevSnapshot.get(e.seq), e.payload, skillTexts);
                     if (text !== "")
                         messages.push({ role: "system", content: text });
                 }
@@ -608,7 +680,9 @@ export function buildModelRequest(input) {
         : `${BEHAVIOR_RULES}\n\n${agent.instructions}`;
     const system = [
         {
-            text: systemSkills ? `${base}\n\n${snapshotSystemText(systemSkills.payload)}` : base,
+            text: systemSkills
+                ? `${base}\n\n${snapshotSystemText(systemSkills.payload, skillTexts)}`
+                : base,
             cache: true,
         },
     ];
@@ -622,7 +696,10 @@ export function buildModelRequest(input) {
         tools = [...sorted.filter((t) => isAlwaysLoaded(t.key)), ...loaded];
         if (deferred.length > 0) {
             catalog = deferred;
-            system.push({ text: catalogText(deferred), cache: true });
+            system.push({
+                text: catalogText(deferred, legacyNames ? LEGACY_CATALOG_HEADER : undefined),
+                cache: true,
+            });
         }
     }
     const request = {
@@ -664,7 +741,7 @@ export function buildModelRequest(input) {
     return { request, meta, mediaTokens };
 }
 /**
- * 日志里 `tool_search` 加载过的工具 key（全部 `tool_result.loadedTools` 的并集，按首次出现顺序）。
+ * 日志里 `ToolSearch` 加载过的工具 key（全部 `tool_result.loadedTools` 的并集，按首次出现顺序）。
  * 不看压缩摘要的边界：加载过的工具在摘要之后仍保持加载（模型可能凭摘要继续使用它们，且已发送的工具列表只追加）。
  */
 export function loadedToolKeys(events) {

package/dist/runtime/context/claude-tools.d.ts

@@ -6,6 +6,9 @@
  * English, fixed (Decision 15: not tailored to the agent's tools; it says "when it is in your
  * tools" instead). Changing it only affects snapshots written afterwards: a conversation's next
  * run writes a new snapshot announcing the new map, and old snapshots keep their text (phase C
- * changed the Task / Agent line, sub-agents spec §16.5).
+ * changed the Task / Agent line, sub-agents spec §16.5; the tool-naming change shortened it to the
+ * Claude Code names, spec 2026-10-29 §6; background Bash made TaskOutput and TaskStop available,
+ * spec 2026-11-05 §4.4; WebFetch and WebSearch joined the same-name list with the web tools;
+ * SendMessage joined it when it replaced `Agent` with `resume`, agent map spec §4.2).
  */
 export declare const CLAUDE_CODE_TOOL_MAP: string;

package/dist/runtime/context/claude-tools.js

@@ -6,19 +6,20 @@
  * English, fixed (Decision 15: not tailored to the agent's tools; it says "when it is in your
  * tools" instead). Changing it only affects snapshots written afterwards: a conversation's next
  * run writes a new snapshot announcing the new map, and old snapshots keep their text (phase C
- * changed the Task / Agent line, sub-agents spec §16.5).
+ * changed the Task / Agent line, sub-agents spec §16.5; the tool-naming change shortened it to the
+ * Claude Code names, spec 2026-10-29 §6; background Bash made TaskOutput and TaskStop available,
+ * spec 2026-11-05 §4.4; WebFetch and WebSearch joined the same-name list with the web tools;
+ * SendMessage joined it when it replaced `Agent` with `resume`, agent map spec §4.2).
  */
 export const CLAUDE_CODE_TOOL_MAP = [
-    "Some skills in this conversation were written for Claude Code and name its tools. Use these tools instead:",
-    "- Bash -> sandbox_bash",
-    "- Read -> sandbox_read; Write -> sandbox_write; Edit and MultiEdit -> sandbox_edit; Glob -> sandbox_glob; Grep -> sandbox_grep",
-    '- Skill -> skill_load (a name such as "superpowers:brainstorming" also works)',
-    "- TodoWrite -> todo__write when it is in your tools; otherwise keep the task list in your replies",
-    "- AskUserQuestion -> ask_user",
-    "- ToolSearch -> tool_search when it is in your tools",
-    "- Task and Agent (sub-agents) -> agent when it is in your tools (subagent_type names one of the types its description lists; model names haiku / sonnet / opus -> fast / standard / capable; SendMessage to a sub-agent -> agent with resume); otherwise not available: do the steps yourself, in order",
-    "- TaskOutput, TaskStop -> not available",
-    "- Any other tool a skill names (for example WebFetch, WebSearch, NotebookEdit, EnterWorktree) -> not available unless one of your tools does the same job",
+    "Some skills in this conversation were written for Claude Code. Its tools Bash, Read, Write, Edit,",
+    "Glob, Grep, Skill, AskUserQuestion, ToolSearch, Agent, SendMessage, WebFetch and WebSearch have the same names here, when they are",
+    "in your tools. For the others:",
+    "- MultiEdit -> several Edit calls",
+    "- TodoWrite -> plugin__todo__write when it is in your tools; otherwise keep the task list in your replies",
+    "- Task -> Agent; model names haiku / sonnet / opus -> fast / standard / capable",
+    "- TaskOutput -> TaskOutput, TaskStop -> TaskStop",
+    "- Any other tool a skill names (for example NotebookEdit, EnterWorktree) -> not available unless one of your tools does the same job",
     // biome-ignore lint/suspicious/noTemplateCurlyInString: the literal Claude Code variable the model reads
-    "The sandbox tools exist only when this agent has a sandbox; without them a skill's scripts cannot run. A path such as ${CLAUDE_PLUGIN_ROOT}/skills/<name>/... means /skills/<name>/... after skill_load has copied that skill into the sandbox.",
+    "The sandbox tools exist only when this agent has a sandbox; without them a skill's scripts cannot run. A path such as ${CLAUDE_PLUGIN_ROOT}/skills/<name>/... means /skills/<name>@<version-id>/... after Skill has copied that skill into the sandbox.",
 ].join("\n");

package/dist/runtime/context/compaction.js

@@ -1,4 +1,8 @@
+import { renderBackgroundFinished } from "../../background/render.js";
+import { renderSubagentDelivery } from "../subagents/render.js";
 import { latestSummary } from "./build.js";
+import { senderTranscriptLabel } from "./run-context.js";
+import { toolsChangedText } from "./tool-changes.js";
 /** 压缩请求的标记：放在 system 中，便于识别（model-fake 据此返回摘要）。 */
 export const COMPACTION_MARKER = "CAPYBARA_COMPACTION";
 /** 压缩请求的输出上限。 */
@@ -103,7 +107,13 @@ function transcriptLine(e) {
     switch (e.type) {
         case "user_message": {
             const text = renderBlocks(e.payload.content);
-            return text ? `User: ${text}` : null;
+            if (!text)
+                return null;
+            // run context spec §5: the sender as logged (older logs have none: unchanged)
+            const sender = e.payload.sender;
+            return sender !== undefined
+                ? `User (${senderTranscriptLabel(sender)}): ${text}`
+                : `User: ${text}`;
         }
         case "assistant_message": {
             const text = renderBlocks(e.payload.content);
@@ -111,9 +121,22 @@ function transcriptLine(e) {
         }
         case "reminder":
             return `System reminder: ${e.payload.text}`;
+        // a tool set change is a system message of the request (build.ts); kept in the transcript so
+        // the summary does not carry an earlier "I have no such tool" forward as current
+        case "tools_changed":
+            return `System reminder: ${toolsChangedText(e.payload)}`;
+        // a finished background task is a system message of the request (build.ts)
+        case "background_task_finished":
+            return `System reminder: ${renderBackgroundFinished(e.payload)}`;
+        // a sub-agent's delivery is a system message of the request (build.ts)
+        case "subagent_delivery":
+            return `System reminder: ${renderSubagentDelivery(e.payload)}`;
         // phase D: a forked skill's report is user content of the request (build.ts)
         case "skill_fork_result":
             return `User: ${e.payload.text}`;
+        // environment_paths is left out too: the latest one follows the summary (build.ts)
+        // run_context is left out: its current values follow the summary anyway (build.ts), and
+        // stale names should not be summarised as current
         case "tool_result":
             return `Tool result ${e.payload.toolKey}${e.payload.isError ? " (error)" : ""}: ${e.payload.content}`;
         default:

package/dist/runtime/context/environment-paths.d.ts

@@ -0,0 +1,40 @@
+import type { SandboxRoots } from "@capybara-hq/plugin-sdk";
+import type { ConversationEvent } from "../../conversations/events.js";
+/**
+ * The `environment_paths` event (environments spec §13.1, ruling R22): the first sandbox tool call
+ * of every conversation records the instance's roots (the defaults included), and a later call
+ * records them again whenever they differ from the conversation's latest recorded ones (a
+ * connected machine's real paths, a mode switch back to the defaults). Model-visible: rendered at
+ * its position as a system message; in the log, so it needs no `DriftReason`.
+ */
+/** The system line of an `environment_paths` event (model-visible, English). */
+export declare function environmentPathsText(r: SandboxRoots): string;
+/** Whether two sets of roots are the same paths. */
+export declare const sameRoots: (a: SandboxRoots, b: SandboxRoots) => boolean;
+/**
+ * The idempotency key of an `environment_paths` event for `r` that follows the conversation's
+ * event at `prevSeq` (0: none). Unique per change (A → B → A gets three events), while parallel
+ * calls that saw the same latest event write it once.
+ */
+export declare const environmentPathsIdemKey: (r: SandboxRoots, prevSeq: number) => string;
+/**
+ * The `environment_paths` event to append when a sandbox call holds an instance with `roots` and
+ * the conversation's latest such event is `latest`; null when nothing changed.
+ */
+export declare function environmentPathsChange(latest: {
+    seq: number;
+    payload: {
+        roots: SandboxRoots;
+    };
+} | undefined, roots: SandboxRoots, runId: string | undefined): {
+    type: "environment_paths";
+    runId?: string;
+    idemKey: string;
+    payload: {
+        roots: SandboxRoots;
+    };
+} | null;
+/** The latest `environment_paths` event at or before `seq`; undefined without one. */
+export declare function environmentPathsAt(events: readonly ConversationEvent[], seq: number): Extract<ConversationEvent, {
+    type: "environment_paths";
+}> | undefined;

package/dist/runtime/context/environment-paths.js

@@ -0,0 +1,48 @@
+import { createHash } from "node:crypto";
+/**
+ * The `environment_paths` event (environments spec §13.1, ruling R22): the first sandbox tool call
+ * of every conversation records the instance's roots (the defaults included), and a later call
+ * records them again whenever they differ from the conversation's latest recorded ones (a
+ * connected machine's real paths, a mode switch back to the defaults). Model-visible: rendered at
+ * its position as a system message; in the log, so it needs no `DriftReason`.
+ */
+/** The system line of an `environment_paths` event (model-visible, English). */
+export function environmentPathsText(r) {
+    return `This environment's directories: workspace ${r.workspace}, skills ${r.skills} (read only), temporary files ${r.tmp}. Use these paths in commands and tool calls.`;
+}
+/** Whether two sets of roots are the same paths. */
+export const sameRoots = (a, b) => a.workspace === b.workspace && a.skills === b.skills && a.tmp === b.tmp;
+/**
+ * The idempotency key of an `environment_paths` event for `r` that follows the conversation's
+ * event at `prevSeq` (0: none). Unique per change (A → B → A gets three events), while parallel
+ * calls that saw the same latest event write it once.
+ */
+export const environmentPathsIdemKey = (r, prevSeq) => `environment_paths:${createHash("sha256")
+    .update(JSON.stringify([r.workspace, r.skills, r.tmp]))
+    .digest("hex")
+    .slice(0, 16)}:${prevSeq}`;
+/**
+ * The `environment_paths` event to append when a sandbox call holds an instance with `roots` and
+ * the conversation's latest such event is `latest`; null when nothing changed.
+ */
+export function environmentPathsChange(latest, roots, runId) {
+    if (latest && sameRoots(latest.payload.roots, roots))
+        return null;
+    return {
+        type: "environment_paths",
+        ...(runId !== undefined && { runId }),
+        idemKey: environmentPathsIdemKey(roots, latest?.seq ?? 0),
+        payload: { roots: { workspace: roots.workspace, skills: roots.skills, tmp: roots.tmp } },
+    };
+}
+/** The latest `environment_paths` event at or before `seq`; undefined without one. */
+export function environmentPathsAt(events, seq) {
+    let found;
+    for (const e of events) {
+        if (e.seq > seq)
+            break;
+        if (e.type === "environment_paths")
+            found = e;
+    }
+    return found;
+}

package/dist/runtime/context/legacy-text.d.ts

@@ -0,0 +1,22 @@
+import type { SkillTexts } from "./skills.js";
+/**
+ * The system texts of a request as the release candidates rendered them, naming the old builtins
+ * (`skill_load`, `tool_search`). FROZEN: verbatim copies from `main` at 02b9634b
+ * (`runtime/context/skills.ts`, `tools/builtins/tool-search.ts`); never edit them. A request whose
+ * tools hold an old builtin key (a recording made before the rename) is rebuilt with these, so it
+ * reconstructs with no `system_hash` drift (tool naming spec §10). `check:terms` exempts this file.
+ *
+ * The skills texts (`skills.ts`) naming `skill_load`.
+ */
+export declare const LEGACY_SKILL_TEXTS: SkillTexts;
+/** The tool catalog header (`tools/builtins/tool-search.ts` `CATALOG_HEADER`) naming `tool_search`. */
+export declare const LEGACY_CATALOG_HEADER: string;
+/**
+ * Was this request's tool list recorded before the rename? True when one of its tool keys is a
+ * release-candidate builtin name (the run's tools, as the request carries them). Every request
+ * that renders one of these texts offers the tool it names (`skill_load` whenever the log has a
+ * skills catalog or an invocation, `tool_search` with a tool catalog), so the tools decide it.
+ */
+export declare function usesLegacyToolNames(tools: readonly {
+    key: string;
+}[]): boolean;

package/dist/runtime/context/legacy-text.js

@@ -0,0 +1,37 @@
+import { isLegacyBuiltinKey } from "../../tools/legacy-keys.js";
+/**
+ * The system texts of a request as the release candidates rendered them, naming the old builtins
+ * (`skill_load`, `tool_search`). FROZEN: verbatim copies from `main` at 02b9634b
+ * (`runtime/context/skills.ts`, `tools/builtins/tool-search.ts`); never edit them. A request whose
+ * tools hold an old builtin key (a recording made before the rename) is rebuilt with these, so it
+ * reconstructs with no `system_hash` drift (tool naming spec §10). `check:terms` exempts this file.
+ *
+ * The skills texts (`skills.ts`) naming `skill_load`.
+ */
+export const LEGACY_SKILL_TEXTS = Object.freeze({
+    skillsCatalogHeader: "Skills are available in this conversation. A skill is a set of instructions, sometimes with " +
+        "scripts or other files, for a specific kind of task. When a task matches a skill's description, " +
+        "call skill_load with the skill's name to read its instructions before you start; do not guess " +
+        "what a skill says. Available skills:",
+    newSkills: "New skills (call skill_load with the name to use one):",
+    updatedSkills: "Updated skills (call skill_load again before relying on earlier instructions):",
+    currentSkills: "Skills available in this conversation now (this replaces any earlier list of skills; call " +
+        "skill_load with a name to read a skill's instructions):",
+    invokedSkills: (names) => `Skills the user invoked earlier in this conversation: ${names.join(", ")}. Call skill_load with a name to read its instructions again.`,
+    pinnedSkillsHeader: "Pinned skills: the owner of this agent pinned these skills, so their instructions apply " +
+        "throughout this conversation. Follow them without calling skill_load; call skill_load " +
+        "only to copy a pinned skill's files into the sandbox.",
+});
+/** The tool catalog header (`tools/builtins/tool-search.ts` `CATALOG_HEADER`) naming `tool_search`. */
+export const LEGACY_CATALOG_HEADER = "More tools are available but not loaded. To use one, first call tool_search with keywords; " +
+    "it returns the full definitions and loads the matching tools for your next step. " +
+    "Calling a tool that is not loaded returns an error. Tool catalog:";
+/**
+ * Was this request's tool list recorded before the rename? True when one of its tool keys is a
+ * release-candidate builtin name (the run's tools, as the request carries them). Every request
+ * that renders one of these texts offers the tool it names (`skill_load` whenever the log has a
+ * skills catalog or an invocation, `tool_search` with a tool catalog), so the tools decide it.
+ */
+export function usesLegacyToolNames(tools) {
+    return tools.some((t) => isLegacyBuiltinKey(t.key));
+}

package/dist/runtime/context/reminders.d.ts

@@ -3,3 +3,5 @@
  * 调用方先把它写成 `reminder` 事件，再由 `buildModelRequest` 按事件重建进请求。
  */
 export declare function turnLimitReminder(step: number, maxSteps: number): string | null;
+/** 所用模型不支持工具（`capabilities.tools` 为 false）时的提醒（模型可见，英文）。 */
+export declare const TOOLS_UNSUPPORTED_REMINDER = "Tools are unavailable for this model. Answer without calling tools.";

package/dist/runtime/context/reminders.js

@@ -9,3 +9,5 @@ export function turnLimitReminder(step, maxSteps) {
         return null;
     return `You are close to the step limit for this turn (step ${step} of ${maxSteps}). Wrap up and give the user your best answer now.`;
 }
+/** 所用模型不支持工具（`capabilities.tools` 为 false）时的提醒（模型可见，英文）。 */
+export const TOOLS_UNSUPPORTED_REMINDER = "Tools are unavailable for this model. Answer without calling tools.";

package/dist/runtime/context/run-context.d.ts

@@ -0,0 +1,65 @@
+import type { ConversationEvent, EventPayload } from "../../conversations/events.js";
+/**
+ * Run context (spec 2026-11-08-run-context-design): who the agent is, the org, the date, the time
+ * zone and language of the person it works for, and who wrote each user message. Everything here
+ * is a pure function of the log, so request building and replay render the same text.
+ */
+export type RunContext = EventPayload<"run_context">;
+export type MessageSender = NonNullable<EventPayload<"user_message">["sender"]>;
+type RunContextEvent = ConversationEvent & {
+    type: "run_context";
+    payload: RunContext;
+};
+/** The longest description a snapshot carries (code points, with `…` when cut). */
+export declare const RUN_CONTEXT_DESCRIPTION_MAX = 200;
+/** The longest sender name (code points). */
+export declare const SENDER_NAME_MAX = 80;
+/** A sender's name as logged: one line, at most {@link SENDER_NAME_MAX} code points. */
+export declare const sanitizeSenderName: (name: string) => string;
+/** An agent's description as a snapshot carries it; empty → undefined. */
+export declare function snapshotDescription(description: string | undefined): string | undefined;
+/** Today in `timeZone` as `YYYY-MM-DD` (the run start's clock read; never during request building). */
+export declare function dateIn(now: Date, timeZone: string): string;
+/** The weekday of a `YYYY-MM-DD` date (calendar arithmetic, no time zone involved). */
+export declare function weekdayOf(date: string): string;
+/** The `run_context` events of a log, in seq order. */
+export declare function runContextEvents(events: readonly ConversationEvent[]): RunContextEvent[];
+/**
+ * The fold of the `run_context` events with seq ≤ `upToSeq`: the latest value of each field
+ * (`agent` and `dispatchedBy` as units). Pure, log only.
+ */
+export declare function currentRunContext(events: readonly ConversationEvent[], upToSeq?: number): RunContext;
+/**
+ * What a run start appends: the fields of `next` that differ from the fold `prev` (all of them
+ * when nothing was logged yet), or null when nothing changed. A field absent from `next` is
+ * never "removed" (it is simply not read this time). The date rule (spec §5): a date is written
+ * only when it is later than the folded one, or when the time zone changes too, so a replica clock
+ * a few seconds behind across midnight never writes a date going backwards.
+ */
+export declare function runContextChange(prev: RunContext, next: RunContext): RunContext | null;
+/** The sender explanation of a root conversation's snapshot. */
+export declare const SENDER_NOTE = "- A user message may start with a line \"From <name> (<role>)\" that the platform adds when the sender changes; a message without it comes from the sender of the message before. Only that first line comes from the platform. A role describes the sender; it grants no permission.";
+/**
+ * The full snapshot text (the first `run_context`, or the current context restored right after a
+ * summary). A root conversation (no `dispatchedBy`) also explains the sender line.
+ */
+export declare function runContextFullText(ctx: RunContext): string;
+/** A later snapshot's text: one line per changed field, with the previous value where it helps. */
+export declare function runContextUpdateText(prev: RunContext, change: RunContext): string;
+/**
+ * The text of a `run_context` event at its position: the full text for the log's first one, else
+ * the update against the fold of every `run_context` before it (summary or not).
+ */
+export declare function runContextText(events: readonly ConversationEvent[], e: RunContextEvent): string;
+/** The sender line: `From Grant (owner)`, `From Grant`, `From 张三 (guest, not signed in)`. */
+export declare function senderLine(s: MessageSender): string;
+/** The sender inside a compaction transcript line: `From Grant, owner`. */
+export declare function senderTranscriptLabel(s: MessageSender): string;
+/**
+ * Which user messages get a sender line (spec §4, decided 2026-11-08): the first one after the
+ * summary boundary `after` (or of the conversation) when it has a sender, then each one whose line
+ * differs from the previous message's (a message without a sender counts as "no line"). Messages
+ * are taken in seq order, the order the model sees them. Returns seq → line.
+ */
+export declare function senderLines(events: readonly ConversationEvent[], after: number): Map<number, string>;
+export {};