@tencent-ai/agent-harness 0.2.0-beta.6 → 0.2.0-beta.8

package/cli/dist-server/types/node/utils/terminal-detector-utils.d.ts

@@ -0,0 +1,78 @@
+export declare enum TerminalType {
+    CURSOR = "cursor",
+    WINDSURF = "windsurf",
+    CODIUM = "codium",
+    VSCODE = "vscode",
+    ZED = "zed",
+    ANDROIDSTUDIO = "androidstudio",
+    VISUALSTUDIO = "visualstudio",
+    PYCHARM = "pycharm",
+    INTELLIJ_IDEA = "intellij",
+    WEBSTORM = "webstorm",
+    PHPSTORM = "phpstorm",
+    GOLAND = "goland",
+    RIDER = "rider",
+    CLION = "clion",
+    RUBYMINE = "rubymine",
+    APPCODE = "appcode",
+    DATAGRIP = "datagrip",
+    JETBRAINS = "jetbrains",
+    CODEBUDDY = "codebuddy",
+    CODEBUDDY_CN = "codebuddy_cn",
+    ITERM = "iTerm.app",
+    ITERM_LEGACY = "iTerm",// 旧版 iTerm 的 TERM_PROGRAM 值
+    APPLE_TERMINAL = "Apple_Terminal",
+    GHOSTTY = "ghostty",
+    KITTY = "kitty",
+    ALACRITTY = "alacritty",
+    WEZTERM = "WezTerm",
+    HYPER = "Hyper",
+    TABBY = "Tabby",
+    WARP = "warp",
+    KONSOLE = "konsole",
+    GNOME_TERMINAL = "gnome-terminal",
+    XTERM = "xterm",
+    VTE_BASED = "vte-based",
+    TERMINATOR = "terminator",
+    TILIX = "tilix",
+    RXVT = "rxvt",
+    TERMITE = "termite",
+    WINDOWS_TERMINAL = "windows-terminal",
+    POWERSHELL = "powershell",
+    CONEMU = "conemu",
+    CYGWIN = "cygwin",
+    SCREEN = "screen",
+    TMUX = "tmux",
+    SSH_SESSION = "ssh-session",
+    NON_INTERACTIVE = "non-interactive",
+    UNKNOWN = "unknown"
+}
+export declare abstract class TerminalDetectorUtils {
+    /**
+     * Detect the current terminal type
+     * Returns a string identifier for the terminal, or undefined if detection fails
+     */
+    static detect(): string | undefined;
+    /**
+     * Detect the current terminal and return it as a TerminalType enum value
+     * Returns TerminalType.UNKNOWN if the terminal cannot be determined
+     */
+    static detectAsType(): TerminalType;
+    static isSupported(): boolean;
+    static getSetupDescription(): string;
+    /**
+     * Get a human-readable terminal name
+     */
+    static getTerminalName(): string;
+    /**
+     * 获取当前终端的换行快捷键提示
+     * @param includeSetupHint 是否包含 /terminal-setup 提示
+     * @returns 换行快捷键的描述文本
+     */
+    static getNewlineKeyBindingTip(includeSetupHint?: boolean): string;
+    /**
+     * 获取短版本的换行快捷键（不带提示）
+     * @returns 快捷键名称，如 "Shift + Enter" 或 "Option + Enter"
+     */
+    static getNewlineKeyBinding(): string;
+}

package/cli/dist-server/types/node/vim/index.d.ts

@@ -0,0 +1,2 @@
+export * from './vim-protocol';
+export * from './vim-manager';

package/cli/dist-server/types/node/vim/vim-manager.d.ts

@@ -0,0 +1,12 @@
+import { Subject } from 'rxjs';
+import { SettingsManager } from '../settings/settings-protocol';
+import { VimManager } from './vim-protocol';
+export declare class DefaultVimManager implements VimManager {
+    protected readonly settingsManager: SettingsManager;
+    private static readonly VIM_SETTING_KEY;
+    readonly onDidChangeState: Subject<boolean>;
+    isEnabled(): Promise<boolean>;
+    enable(): Promise<void>;
+    disable(): Promise<void>;
+    toggle(): Promise<boolean>;
+}

package/cli/dist-server/types/node/vim/vim-protocol.d.ts

@@ -0,0 +1,24 @@
+import { Subject } from 'rxjs';
+export declare const VimManager: unique symbol;
+export interface VimManager {
+    /**
+     * 检查 Vim 模式是否启用
+     */
+    isEnabled(): Promise<boolean>;
+    /**
+     * 启用 Vim 模式
+     */
+    enable(): Promise<void>;
+    /**
+     * 禁用 Vim 模式
+     */
+    disable(): Promise<void>;
+    /**
+     * 切换 Vim 模式状态
+     */
+    toggle(): Promise<boolean>;
+    /**
+     * Vim 状态变化的 Subject
+     */
+    readonly onDidChangeState: Subject<boolean>;
+}

package/cli/dist-server/types/vendor/cbc-core/node/agent/agent-protocol.d.ts

@@ -1,6 +1,6 @@
 import { Agent, type AgentInputItem, type AgentOptions, type NonStreamRunOptions, type RunConfig, Runner, RunState, type StreamRunOptions, type Usage } from '../../../cbc-shared/node/index.js';
 import { Agent as ProductAgentConfiguration, Command, LanguageModel, ModelVariantType } from '../../../../workspace/product/lib/common/index.js';
-import type { SecurityReviewFailureReason, W3CTraceContextMeta } from '../../../../workspace/telemetry/lib/common/index.js';
+import type { SecurityReviewFailureReason, SecurityReviewModelCallPayload, SecurityReviewType, W3CTraceContextMeta } from '../../../../workspace/telemetry/lib/common/index.js';
 import type { Session, SessionOptions } from '../session/session-protocol';
 import type { AgentPurpose } from './agent-purpose-protocol';
 import type { AgentRunContinuation, AgentRunOrigin } from './agent-run-scope';
@@ -614,10 +614,15 @@ export interface ReviewerOneTimeRequest {
     temperature: number;
     signal?: AbortSignal;
     purpose: AgentPurpose.SecurityReviewer | AgentPurpose.ContentSecurityReviewer;
-    /** 只用于解析当前主模型，不向审查调用复制历史、工具或权限。 */
+    /** 只用于解析当前主模型和关联上报，不向审查调用复制历史、工具或权限。 */
     callerSession?: Session;
     /** 首次失败时立即通知，整体超时也能保留回退前的错误。 */
     onRecovery?: (recovery: ReviewerRecovery) => void;
+    reviewType: SecurityReviewType;
+    /** 模型已返回但输出不构成有效结论时返回失败原因，用于判定本次调用是否成功。 */
+    validateResult?: (result: ReviewerOneTimeResult) => SecurityReviewFailureReason | undefined;
+    /** 每次模型调用结算一次；signal 以 'timeout' 为 reason 中止时记为超时。 */
+    onModelCall?: (call: SecurityReviewModelCallPayload, callerSession?: Session) => void;
 }
 export interface ReviewerOneTimeResult {
     output: string;
@@ -760,6 +765,11 @@ export interface AgentRunRequest<TContext = Session> extends SessionOptions {
     skipAddHistory?: boolean;
     bypassMessageQueue?: boolean;
     inputOrigin?: AgentRunOrigin;
+    /**
+     * Whether the batch admitted by MessageQueue contains an external user prompt.
+     * Captured before History replaces input with the active conversation history.
+     */
+    hasExternalUserPromptAtAdmission?: boolean;
     /** Process-local arrival callback; never passed to the SDK. */
     onResult?: AgentStandardRunOptions['onResult'];
     traceId?: string;

package/cli/dist-server/types/vendor/cbc-core/node/agent/reviewer-recovery.d.ts

@@ -16,4 +16,11 @@ export declare class ReviewerModelError extends Error {
     constructor(failureReason: SecurityReviewFailureReason, circuitFailureReason?: SecurityReviewFailureReason | undefined);
 }
 export declare function classifyReviewerError(error: unknown, timedOut?: boolean, cancelled?: boolean): SecurityReviewFailureReason;
+type ReviewerAbortReason = Extract<SecurityReviewFailureReason, 'timeout' | 'cancelled'>;
+/** 中止 reason 即失败原因，模型调用上报经 {@link reviewerAbortReason} 读回以区分超时与取消。 */
+export declare function abortReviewer(controller: AbortController, timedOut: boolean): void;
+export declare function reviewerAbortReason(signal: AbortSignal): ReviewerAbortReason;
+/** 输出被截断无法得到完整结论，按输出不合规处理；网关两种 content filter 拼写都会出现。 */
+export declare function classifyReviewerFinishReason(finishReason: string | undefined): Extract<SecurityReviewFailureReason, 'schema_invalid' | 'content_filter'> | undefined;
 export declare function canRetryReviewer(reason: SecurityReviewFailureReason): boolean;
+export {};

package/cli/dist-server/types/vendor/cbc-core/node/context/mods-bridge.d.ts

@@ -1,8 +1,35 @@
-import type { AgentInputItem } from '../../../cbc-shared/node/index.js';
+import { type AgentInputItem } from '../../../cbc-shared/node/index.js';
 import type { PromptContext } from './context-protocol';
 export interface ModsPromptSubmitResult {
     text?: string;
     drop?: string;
+    context?: readonly string[];
+}
+export interface ModsPromptAttachment {
+    readonly type: 'image' | 'audio' | 'document';
+    readonly mediaType?: string;
+    readonly filename?: string;
+}
+export interface ModsExecutionContext {
+    readonly sessionId: string;
+    readonly cwd: string;
+    readonly signal?: AbortSignal;
+}
+export interface ModsToolCall {
+    readonly name: string;
+    readonly input: unknown;
+    readonly callId?: string;
+    readonly agentId?: string;
+    readonly signal?: AbortSignal;
+    readonly onResult?: (result: {
+        context?: readonly string[];
+        isError?: boolean;
+    }) => void;
+}
+export interface ModsToolDescription {
+    readonly description: string;
+    /** Omission keeps the Agent's existing placement policy. */
+    readonly isDeferred?: boolean;
 }
 /** Host-only provenance: a mod initiated submission has already traversed the fold. */
 export declare const MODS_PROMPT_SUBMITTED_KEY = "modsPromptSubmitted";
@@ -29,6 +56,11 @@ export declare const MODS_PROMPT_SUBMITTED_KEY = "modsPromptSubmitted";
  * 不构造对象、不进 async、不改变任何既有行为。
  */
 export interface ModsBridge {
+    /** Host middleware; the execution callback retains validation and permission checks. */
+    toolCall?<T>(input: ModsToolCall, execute: (input: unknown) => Promise<T>): Promise<T>;
+    toolDescription?(name: string, description: string, isDeferred?: boolean): Promise<ModsToolDescription>;
+    /** First-message context, cached by the owning Session until its history resets. */
+    initialContext?(context: PromptContext, render: (context: PromptContext) => Promise<string | undefined>): Promise<readonly string[]>;
     /**
      * 上下文装配完成、尚未拼成最终 prompt 时问一句。
      *
@@ -53,6 +85,7 @@ export interface ModsBridge {
      */
     promptSubmit(input: {
         text: string;
+        attachments?: readonly ModsPromptAttachment[];
         sessionId?: string;
         signal?: AbortSignal;
     }): Promise<ModsPromptSubmitResult | undefined>;
@@ -81,6 +114,9 @@ export interface ModsBridge {
         plugin: string;
     }): void;
 }
+/** A Server query owns its bridge; child work inherits the originating execution. */
+export declare function withModsBridge<T>(bridge: ModsBridge | undefined, context: ModsExecutionContext, run: () => T): T;
+export declare function currentModsExecutionContext(): ModsExecutionContext | undefined;
 /**
  * 注入桥。宿主在 mods 运行时起来之后调用一次。
  *
@@ -101,7 +137,7 @@ export declare function currentModsBridge(): ModsBridge | undefined;
  */
 export declare function throughModsPromptContext(context: PromptContext): Promise<PromptContext>;
 /** A failed third-party fold must not corrupt or lose the original input. */
-export declare function throughModsPromptSubmit(text: string, sessionId?: string, signal?: AbortSignal): Promise<ModsPromptSubmitResult | undefined>;
+export declare function throughModsPromptSubmit(text: string, sessionId?: string, signal?: AbortSignal, attachments?: readonly ModsPromptAttachment[]): Promise<ModsPromptSubmitResult | undefined>;
 /** Mutates only user text, before the shared history/model consumers see these items. */
 export declare function applyModsPromptSubmit(items: AgentInputItem[], sessionId: string, signal?: AbortSignal): Promise<string | undefined>;
 /**

package/cli/dist-server/types/vendor/cbc-core/node/session/background-task-protocol.d.ts

@@ -1,8 +1,22 @@
 import type { AcpTerminalEndReason } from '../../../cbc-shared/node/index.js';
+export interface BackgroundTaskOutputRead {
+    /** Absolute character offset requested for this read, clamped to the current output range. */
+    fromOffset: number;
+    /** Absolute character offset immediately after the returned snapshot. */
+    nextOffset: number;
+    /** Preserved output for the requested range, including an omission marker when needed. */
+    content: string;
+    /** Unread characters no longer retained by the bounded buffer. */
+    omittedLength: number;
+}
 /** Output buffer capabilities used by task producers and consumers. */
 export interface BackgroundTaskOutputBuffer {
     push(data: string): void;
     toString(withMarker?: boolean): string;
+    /** Absolute character offset at the current end of the output stream. */
+    getEndOffset(): number;
+    /** Read output retained after an absolute character offset. */
+    readSince(offset: number): BackgroundTaskOutputRead;
     isEmpty(): boolean;
     getHead(): string;
     getTail(): string;

package/cli/dist-server/types/vendor/cbc-core/node/session/interruption-service.d.ts

@@ -132,6 +132,7 @@ export declare class InterruptionServiceImpl implements InterruptionService {
     reject(item: RunToolApprovalItem, options?: {
         decision?: 'deny' | 'rejectAndExitPlan';
         cancelTurn?: boolean;
+        interrupted?: boolean;
     }): void;
     /**
      * 取消指定 session 上所有未决的 interruption Deferred。
@@ -168,6 +169,9 @@ export declare class InterruptionServiceImpl implements InterruptionService {
      */
     releaseSession(target: string | Session): void;
     protected handleInterruptions(session: Session, interruptions: RunToolApprovalItem[], result?: RunResult<any, any> | StreamedRunResult<any, any> | undefined): Promise<void>;
+    /** An in-process middleware continuation waits here without finishing the SDK run. */
+    requestHostToolApproval(session: Session, item: RunToolApprovalItem): Promise<void>;
+    private autoApproveTool;
     private processInterruptions;
     protected executePendingManualPostCompactHook(session: Session, result: RunResult<any, any> | StreamedRunResult<any, any>): Promise<void>;
     waitFor(session: Session): Promise<void>;

package/cli/dist-server/types/vendor/cbc-core/node/session/session-hook-host-protocol.d.ts

@@ -5,7 +5,8 @@ export interface SessionHookHost {
     readonly notificationTitle: string;
     getWorkDir(): string;
     sendNotification(message: string, notificationType: NotificationType | undefined, session: Session | undefined): Promise<void>;
-    registerWatchPaths(paths: unknown, onChange: (path: string, event: 'change' | 'add' | 'unlink') => void): {
+    /** onChange 返回的 Promise 会被等待，用于对批量文件变更做背压。 */
+    registerWatchPaths(paths: unknown, onChange: (path: string, event: 'change' | 'add' | 'unlink') => void | Promise<void>): {
         watcherCount: number;
         dispose(): void;
     };

package/cli/dist-server/types/vendor/cbc-core/node/session/session-interruption-host-protocol.d.ts

@@ -80,6 +80,8 @@ export interface SessionInterruptionSecurityHost {
         assistedMode: TurnSecurityReviewPolicy['assistedApprovalMode'];
     }): void;
     reportAutomaticApprovalOutcome?(input: {
+        session: Session;
+        toolCallId?: string;
         reviewType: 'tool_call' | 'tool_result' | 'sandbox';
         toolName: string;
         decision: 'allow_once' | 'cancel';
@@ -93,6 +95,7 @@ export interface SessionInterruptionSecurityHost {
         scope: 'sandbox';
         decision: 'allow' | 'deny';
         decidedBy: 'ai' | 'user';
+        assistedMode?: 'manual' | 'silent' | 'risk_hint';
         reason?: string;
         reviewDecision?: 'allow' | 'deny';
         reviewReason?: string;

package/cli/dist-server/types/vendor/cbc-core/node/session/session-protocol.d.ts

@@ -955,6 +955,8 @@ export interface InputText {
 export interface SessionOptions {
     /** Host workspace for local transcript reads/writes; omitted uses the CLI working directory. */
     cwd?: string;
+    /** Set by the native TUI loopback request; ACP sessions set this to false. */
+    interactive?: boolean;
     debug?: boolean | string;
     debugToStderr?: boolean;
     verbose?: boolean;
@@ -1062,13 +1064,13 @@ export interface SessionFactory {
 /**
  * 传给 SessionManager/SessionStore.get() 的选项。
  *
- * 默认情况下，session 反序列化会施加一个逆序截断（仅读最近 ~1000 条历史），
+ * 默认情况下，session 反序列化会从尾部截断（仅读最近 ~1000 条历史），
  * 目的是保证正常运行时（会话续聊、模型上下文装配）的性能与内存占用。
  * 展示型场景（如历史回放给前端完整聊天视图）可以通过 `historyLimit` 放大上限。
  */
 export interface SessionGetOptions {
     /**
-     * 从 jsonl 逆序读取的历史 item 数上限。
+     * 从 jsonl 尾部加载的历史 item 数上限。
      *
      * - 未传：沿用默认 1000（服务于续聊、checkpoint、模型上下文等场景）。
      * - 显式传值：按该值截断（如展示型 replay 传 10000）。
@@ -1561,10 +1563,14 @@ export interface PendingApprovalView {
     queueTotal: number;
 }
 export interface InterruptionService {
+    /** Host middleware may wait for the existing approval path inside a running tool. */
+    requestHostToolApproval(session: Session, item: RunToolApprovalItem): Promise<void>;
     approve(item: RunToolApprovalItem, options?: ApprovalOptions): void;
+    /** `interrupted`：非用户决策的收尾（会话中止、请求异常等），只结算审批状态，不计入审批决策。 */
     reject(item: RunToolApprovalItem, options?: {
         decision?: 'deny' | 'rejectAndExitPlan';
         cancelTurn?: boolean;
+        interrupted?: boolean;
     }): void;
     waitFor(session: Session): Promise<void>;
     /** Resolve the main/leader session for a given session (returns self if already main). */

package/cli/dist-server/types/vendor/cbc-core/node/session/session-store.d.ts

@@ -5,6 +5,12 @@ import { LocalJsonlSessionStore } from './local-jsonl-session-store';
 import { type Session, SessionFactory, type SessionForkMutationOptions, type SessionGetOptions, type SessionRewindMutationOptions, SessionStore, type TranscriptPersistenceMetrics } from './session-protocol';
 import type { Lane, LanePointer, SessionKey, SessionStoreEntry } from './session-store-contract';
 import { SessionImageStorage as ImageBlobService, SessionRestoreHost, SessionStoragePaths, SessionToolOutputStorage as ToolResultBlobService } from './session-store-host-protocol';
+/**
+ * Read transcript tails in moderately sized blocks. Small files naturally use
+ * one read, while large files stop as soon as the requested history window is
+ * complete instead of retaining the entire transcript in memory.
+ */
+export declare const SESSION_REVERSE_READ_CHUNK_BYTES: number;
 /**
  * session/load 回放时 history 的默认最大条数。
  * 达到此阈值且遇到 user message 时停止逆序读取，避免启动时全量读 JSONL。
@@ -31,6 +37,23 @@ export declare const DEFAULT_SESSION_MAX_ITEMS = 1000;
 export declare const SESSION_META_TAIL_REFRESH_LINES = 200;
 /** 文件头 session-meta 兜底读取的字节窗口（存量会话用，不做全量回扫）。与上者配对，见其注释。导出以便 spec 钉住配对约束。 */
 export declare const SESSION_META_HEAD_SCAN_BYTES: number;
+/**
+ * 会话标题事实在 session-meta 里的键（#138181）。
+ *
+ * 标题 item（`custom-title` / `ai-title` / `topic`）只在生成/重命名那一刻写一次，通常在
+ * 文件头；history 逆序读封顶 {@link DEFAULT_SESSION_MAX_ITEMS}，长会话 resume 读不到它
+ * → 标题服务判为未命名、拿窗口内的中途消息重新生成，覆盖原任务名。
+ *
+ * 值是 `SessionTitleFact` 数组（session-title-utils）：标题服务判定所依赖的两条事实 ——
+ * `hasCustomTitle` 看的最新非空 `custom-title`，`hasGeneratedTitle` 看的最新真实
+ * `ai-title`（没有时是 `topic`）。跟着 session-meta 走，就复用了 #128860 的尾部刷新与
+ * 文件头兜底，且 session-meta 是 off-tree 行，不进 history、不会被 replay 再发一次。
+ * 读侧把窗口里缺的事实合成回 history 最前面，按 history 判标题的调用方无需改动。
+ *
+ * 标题事实只增不删（空 custom-title 不覆盖更早的非空项，见 `hasCustomTitle`），
+ * 所以按键继承、不登记 {@link SNAPSHOT_ONLY_SESSION_META_KEYS}。
+ */
+export declare const SESSION_TITLE_META_KEY = "codebuddy.ai/sessionTitle";
 /**
  * Keys of session.meta that persist across processes (the off-tree
  * session-meta line; bin resume only — served sessions never write). A
@@ -38,11 +61,12 @@ export declare const SESSION_META_HEAD_SCAN_BYTES: number;
  * never lands on disk. Literals kept in sync with MAIN_AGENT_META_KEY /
  * MAIN_AGENT_HOST_KIND_KEY (agent/main-agent-session.ts, #97166) and
  * MULTITASK_MODE_META_KEY (multitask overlay) and A2A_CONTEXTS_META_KEY
- * (a2a/a2a-context-store.ts). The spec asserts the sync. Growing this list is
- * a review decision, not a side effect of putting a key on session.meta.
+ * (a2a/a2a-context-store.ts), plus SESSION_TITLE_META_KEY above (#138181).
+ * The spec asserts the sync. Growing this list is a review decision, not a
+ * side effect of putting a key on session.meta.
  * Role / locks / parentSessionId stay runtime-only.
  */
-export declare const PERSISTED_SESSION_META_KEYS: readonly ['codebuddy.ai/mainAgent', 'codebuddy.ai/hostKind', 'multitaskMode', 'codebuddy.ai/a2aContexts'];
+export declare const PERSISTED_SESSION_META_KEYS: readonly ['codebuddy.ai/mainAgent', 'codebuddy.ai/hostKind', 'multitaskMode', 'codebuddy.ai/a2aContexts', "codebuddy.ai/sessionTitle"];
 /**
  * 白名单里「缺席即删除」的键：只认最新那一行的存在性，不向更早的行按键继承。
  *
@@ -244,6 +268,12 @@ export declare class SessionStoreImpl implements SessionStore {
      * 写了，另外三份没写，导致 fork 后关掉多任务写不出墓碑、行数计数带着旧值）。
      */
     private markTailMetaPersisted;
+    /**
+     * 读侧发现尾部快照不全（事实只能从文件头 / 窗口外拼回来）：标记过期并把计数播种成
+     * 阈值，下一批 append 立即补一条完整快照。冷启动 resume 的进程内计数从 0 开始，
+     * 若不播种、本次又没补写就重启，长会话会长期不刷新尾部 meta。
+     */
+    private markTailMetaStale;
     /**
      * 让「最新 session-meta」始终留在读侧的逆序窗口内（#128860 根治的写入侧）。
      *
@@ -255,17 +285,32 @@ export declare class SessionStoreImpl implements SessionStore {
      */
     private refreshTailSessionMeta;
     /**
-     * 文件头的 session-meta 兜底读取。
+     * 把本批追加的标题 item 并进 `session.meta` 的标题事实（#138181 的写入侧）。
+     *
+     * 增量合并「已知事实 + 本批标题」：标题只在生成/重命名时出现，其余批次直接跳过，
+     * 不回扫 history。meta 里还没有这个键（经别的加载路径拿到的 session）时才从内存
+     * history 起底一次。落盘交给紧随其后的 {@link refreshTailSessionMeta}：行距内
+     * 原始标题 item 本身就在尾部窗口里，之后每 {@link SESSION_META_TAIL_REFRESH_LINES}
+     * 行的快照都带着这份事实 —— session-meta 是 off-tree 行，补写不受同 id 响应组约束。
+     */
+    private trackSessionTitleFacts;
+    /**
+     * 文件头的 off-tree 事实兜底读取：session-meta 行与标题 item。
      *
      * `session-meta` 创建行通常在文件靠前的位置（新建会话是第 1 行；子会话/迁移过的
      * 会话可能更靠后），而 history 逆序读有 item 上限——长会话倒着读到不了那里
-     * （#128860）。这里只读文件头一小段，不做全量回扫：
+     * （#128860）。首轮的 `ai-title` 同理，落盘在文件头几行（#138181）。这里只读文件头
+     * 一小段，不做全量回扫：
      * 29MB 的会话里末尾 1100 行只占 20% 字节，回扫到头会把 resume 的读 I/O 放大 5×。
      *
      * 返回窗口内所有 session-meta 的 meta（文件序，旧→新），由
-     * {@link composeSessionMeta} 统一合并。
+     * {@link composeSessionMeta} 统一合并；标题时间线（标题 item 与快照里的标题键混排）
+     * 同为文件序，由 {@link resolveSessionTitleFacts} 折叠。
      */
-    protected readHeadSessionMeta(filePath: string): Promise<SessionMetaLine[] | undefined>;
+    protected readHeadOffTreeFacts(filePath: string): Promise<{
+        metaLines: SessionMetaLine[];
+        titleTimeline: AgentInputItem[];
+    } | undefined>;
     /**
      * 合并去重用的行身份。
      *
@@ -291,6 +336,13 @@ export declare class SessionStoreImpl implements SessionStore {
      */
     protected deserializeSessionFromPath(filePath: string, options?: SessionGetOptions): Promise<Session | undefined>;
     protected getSessionId(filePath: string): string;
+    /**
+     * Read complete UTF-8 JSONL records from newest to oldest with bounded I/O.
+     * Newline bytes are safe boundaries in UTF-8; a record is decoded only
+     * after all of its cross-chunk Buffer fragments have been assembled.
+     */
+    protected readLinesFromEnd(filePath: string, fileSize: number, consumeLine: (line: string) => boolean): Promise<number>;
+    private decodeReverseLine;
     private getPreferredProjectDirs;
     get(id: string, options?: SessionGetOptions): Promise<Session | undefined>;
     getAcrossProjects(id: string, options?: SessionGetOptions): Promise<Session | undefined>;

package/cli/dist-server/types/vendor/cbc-core/node/session/truncation-recovery.d.ts

@@ -98,3 +98,11 @@ export declare function readTruncatedResponseUsage(lastTurnResponse: unknown): {
  * 截断不该因为落在不同入口而收到不同指导。
  */
 export declare function buildRecoveryPrompt(truncatedToolNames?: readonly string[]): string;
+/**
+ * 包成 error-recovery system-reminder 后再注入。
+ *
+ * 裸文本会被 `UserQueryWrapperAgentRunInterceptor` 当成用户输入包进 `<user_query>`，
+ * 模型会把内部续写提示读成用户提问；包成带 data-role 的 reminder 后，它与
+ * `buildErrorRecoveryReminder` 等其他恢复提示同形，也不会被当成规则型 reminder。
+ */
+export declare function buildTruncationRecoveryReminder(truncatedToolNames?: readonly string[]): string;

package/cli/dist-server/types/vendor/cbc-core/node/session-title/session-title-utils.d.ts

@@ -28,6 +28,41 @@ export declare function getEffectiveSessionTitle(messages: AgentInputItem[]): st
  * not disappear merely because old conversation turns are trimmed.
  */
 export declare function getEffectiveSessionTitleItem(messages: AgentInputItem[]): AgentInputItem | undefined;
+/** 标题 item 类型 → 标题文本字段。 */
+declare const SESSION_TITLE_TEXT_FIELDS: {
+    readonly 'custom-title': 'customTitle';
+    readonly 'ai-title': 'aiTitle';
+    readonly topic: 'topic';
+};
+export type SessionTitleItemType = keyof typeof SESSION_TITLE_TEXT_FIELDS;
+/**
+ * 一条可持久化的标题事实（#138181）：原 item 的类型、id、标题文本与落盘时间戳，
+ * 不带 parent 链接 / sessionId。形状与标题 item 兼容，可以和 item 混排后用
+ * {@link resolveSessionTitleFacts} 折叠。
+ */
+export interface SessionTitleFact {
+    type: SessionTitleItemType;
+    id?: string;
+    timestamp?: number;
+    customTitle?: string;
+    aiTitle?: string;
+    topic?: string;
+}
+export declare function isSessionTitleItemType(type: unknown): type is SessionTitleItemType;
+/**
+ * 从标题 item / 标题事实里取出标题服务依赖的事实：最新的真实生成标题（`ai-title`，
+ * 没有时是 `topic`）与最新的非空 `custom-title`，与 {@link hasGeneratedTitle} /
+ * {@link hasCustomTitle} / {@link getEffectiveSessionTitleItem} 同一判定（占位标题不算）。
+ *
+ * 「最新」先比 `timestamp`，缺失或相同再按 `items` 的顺序（调用方按文件序传入）。
+ * 只按位置排序不够：另一个进程补写的快照可能带着旧事实落在更新的重命名之后。
+ * 顺序固定为 [生成, 自定义]。
+ */
+export declare function resolveSessionTitleFacts(items: ReadonlyArray<unknown>): SessionTitleFact[];
+/** 读回持久化的标题事实；形状不对（手改 / 未来格式）按「没有」处理。 */
+export declare function parseSessionTitleFacts(value: unknown): SessionTitleFact[] | undefined;
+/** `items` 里已有这条标题：同 id，或同类型同文本（fork 克隆的标题 id 会被重铸）。 */
+export declare function hasMatchingTitleItem(items: ReadonlyArray<AgentInputItem>, fact: SessionTitleFact): boolean;
 /**
  * Extract the first real user message's full text, used as the LLM input for
  * title generation. Unlike `getEffectiveSessionTitle`'s fallback (which
@@ -49,3 +84,4 @@ export declare function getFirstRealUserMessageText(messages: AgentInputItem[]):
  * both breaks that deadlock and yields a more representative title.
  */
 export declare function getFirstUsableUserMessageText(messages: AgentInputItem[], minLength: number): string | undefined;
+export {};

package/cli/dist-server/types/vendor/cbc-core/node/utils/history-utils.d.ts

@@ -12,6 +12,7 @@ export { CompactSummaryNotFoundError };
  */
 export declare const PROMPT_CONTEXT_ROLES: readonly ["user-context", "additional-data"];
 export declare abstract class HistoryUtils {
+    static readonly PRESERVE_GENERAL_PURPOSE_TASK_HISTORY = "preserveGeneralPurposeTaskHistory";
     /**
      * 获取可供 Agent 使用的活跃历史记录
      * 获取活跃对话链（过滤废弃分支），并且滤自定义类型消息
@@ -265,7 +266,9 @@ export declare abstract class HistoryUtils {
      * @param transcriptPath session jsonl 文件路径，用于包装后缀中的 transcript 链接
      */
     static replaceCompactWithSummary(history: AgentInputItem[], transcriptPath: string): AgentInputItem[];
-    static filterTaskHistory(agent: Agent<any, any>, history: AgentInputItem[]): AgentInputItem[];
+    static filterTaskHistory(agent: Agent<any, any>, history: AgentInputItem[], session?: {
+        meta?: Record<string, unknown>;
+    }): AgentInputItem[];
     /**
      * 找到最后一条明确的 compact boundary 消息（压缩结果），
      * 丢弃它之前的所有历史项，只保留该消息及其后的内容。
@@ -319,18 +322,43 @@ export declare abstract class HistoryUtils {
     static containsUserContext(input: AgentInputItem[], userContext: string): boolean;
     static filterTruncatedHistory(history: AgentInputItem[]): AgentInputItem[];
     /**
-     * 用户取消的普通轮次只保留在 transcript 中，不再进入下一轮模型输入。
+     * 把用户取消的轮次投影成模型可见的"被打断"语义，对齐 Codex
+     * （`core/src/tasks/mod.rs` 在 TurnAbortReason::Interrupted 时记入一条
+     * user 角色的 `<turn_aborted>`）：原 prompt、已发生的工具记录都留在模型
+     * 输入里，取消边界本身换成一条 user 角色的中断说明。
+     *
+     * 于是下一轮模型看到的是「原问题 → 中断说明 → 新问题」三段，既知道上一个
+     * 请求没做完，也不会把它当成仍待执行的指令。
      *
-     * 仅处理已落历史的标准取消形态：本轮 user 之后追加了一条 skipRun 的
-     * assistant "Interrupted by user"。为避免影响 /insights 等特殊顺序，只有当
-     * user→取消边界之间没有已完成 assistant 回复时才剔除该段。
+     * 只处理已落历史的标准取消形态：skipRun 的 assistant "Interrupted by user"
+     * （由 `interruption-service` 写入），且该边界确实终结了一个**尚未得到回复**的
+     * 用户轮次 —— 沿 parentId 能找到真实 user、user 在边界之前、两者之间没有已完成的
+     * assistant 回复。这三个条件沿用原过滤器，是 marker 能成立的因果前提：文案断言
+     * 的是"用户打断了上一轮"，若边界挂在一个已经正常回复完的轮次后面（`/insights`
+     * 等特殊顺序、恢复流程留下的错位记录），投影出去就是在对模型说假话。
      *
-     * 该段内的 function_call / function_call_result 会被保留：取消作废的是用户
-     * 的"待执行意图"，而工具调用已经产生过副作用，属于既成事实。
+     * 守卫不通过时原样返回该条，交回 `filterApiErrorMessages` 按基线行为剔除，
+     * 模型侧语义与改动前完全一致。
+     *
+     * 不落盘、不改 transcript：UI 继续显示原来那条 assistant 占位。
      */
-    static filterCancelledPromptHistory(history: AgentInputItem[]): AgentInputItem[];
+    static projectCancelledTurnMarker(history: AgentInputItem[]): AgentInputItem[];
     private static findCancelledTurnUserId;
-    private static hasCompletedAssistantBetween;
+    /**
+     * 这一段里是否已经出现过**结束该轮的** assistant 答复。
+     *
+     * 不能只看"有没有 completed 的 assistant message"：模型调用工具前常先写一句叙述
+     * （tool-call carrier，真实 jsonl 里就是 `status: 'completed'` 的独立 message，
+     * 见 `history-utils.parallel-tool-calls.spec.ts`）。那句话不是对用户的答复，
+     * 这一轮还在继续 —— 所以每遇到一个 `function_call` 就把"已答复"重置掉。
+     *
+     * 依据的是一轮的结构：assistant message 与 function_call 交替，只有**后面再没有
+     * 工具调用**的那条 assistant message 才是对用户的答复。于是三种形态各自判对：
+     *   - `user → 答复(completed) → 边界`                 → 已答复，边界错位，不投影
+     *   - `user → carrier → call → result → 边界`         → 未答复（工具跑完但还没回答），投影
+     *   - `user → carrier → call → result → 答复 → 边界`  → 已答复，边界错位，不投影
+     */
+    private static hasCompletedAssistantReplyBetween;
     /**
      * 在每次模型请求前应用 content-filter 清理:
      * 上一轮模型响应若以 finish_reason=content_filter 结束,