@tencent-ai/agent-sdk 0.3.263-dev.90f0e98.202609190050 → 0.3.263

package/cli/dist-server/types/node/code-ratio/cli-svn-commit-watcher.d.ts

@@ -1,111 +0,0 @@
-import { Application, ApplicationLifecycle } from '@celljs/core';
-import { ProductManager } from '@genie/product';
-import { type ICwdService } from '@genie/cbc-worktree';
-/**
- * CLI 端的 svn commit 监听 + 上报。
- *
- * 设计要点：
- *
- *   - **多仓**：从 `process.cwd()` 出发发现「全部」svn 工作副本——
- *     既兼容「直接打开工作副本（或其子目录）」（沿父链向上找 `.svn`），
- *     也兼容「打开一个父目录、其下挂多个独立工作副本」（向下有限层扫描）。
- *     每个工作副本各自 `fs.watch(.svn/wc.db)`、各自维护 lastRevision、各自上报。
- *   - 监听 `.svn/wc.db`：svn commit/update 都会动这个文件。
- *   - lastRevision 持久化到 `~/.codebuddy/code-ratio/cli-svn-watcher-lastRev-<hash>`，
- *     按 repoRoot 区分，CLI 重启后补差量、避免重复上报。
- *   - 用户身份过滤交给 `getLikelyCurrentSvnUserCandidates` / `isLikelyCurrentUser`，
- *     按各仓库 URL 分别匹配 auth realm，「未知身份不放行」避免 svn update 误报。
- *   - feature gate 不在 watcher 里判：`reporter.observeCommit()` 已做检查。
- */
-export declare class CliSvnCommitWatcher implements ApplicationLifecycle<Application> {
-    protected readonly productManager?: ProductManager;
-    protected readonly cwdService?: ICwdService;
-    private logger?;
-    private readonly repos;
-    /** feature gate 是否已判定 enabled 并触发过挂载，保证只挂一次（幂等）。 */
-    private gateResolved;
-    /** 等待 late-enable 的配置订阅（未启用时挂，enabled 后退订）。 */
-    private gateSubscription?;
-    /** cwd 变更订阅（首轮种子值 attach、之后变更重绑）。 */
-    private cwdChangeSubscription?;
-    /** 标记是否已完成首轮 attach，区分种子值与后续 cwd 变更。 */
-    private attachedOnce;
-    initialize(): void;
-    /**
-     * 入库率 feature gate + late-enable 订阅（对齐 git watcher / plugin-core）。
-     *
-     * 未启用入库率能力时**完全不做** svn 工作副本发现扫描 / watcher / 轮询定时器，
-     * 避免预热池默认开启后对错误继承的 home 目录做大量无意义扫描。
-     * ProductManager 未注册（headless / 单测）时保守退回：直接走 cwd 订阅。
-     */
-    private mountWhenEnabled;
-    /**
-     * 订阅 cwd 变更，把 attach 绑到最新 cwd（对齐 ConfigWatchService）。
-     * 首轮种子值 attach、之后 cwd 变更先 dispose 旧 watcher 再按新 cwd 重新 attach。
-     * CwdService 未注册（单测）时退回：直接 attach 一次。
-     */
-    private subscribeCwd;
-    /**
-     * 是否仍处于预热（prewarm）待机态：argv 含 `--prewarm` 且 PrewarmServer 状态
-     * 为 `idle`（尚未收到 activate）。详见 git watcher 同名方法的说明。
-     *
-     * 待机时跳过首轮 attach，等 activate 后 dispatcher 的 cwd 广播（状态已转为
-     * activating）再绑定，避免对错误继承的 home 做工作副本发现扫描。
-     */
-    private isPrewarmStandby;
-    flushOnExit(): Promise<void>;
-    notifyExternalSvnCommit(): Promise<void>;
-    dispose(): void;
-    /**
-     * 关闭并清空所有工作副本 watcher/timer，但**不**退订 gate/cwd。
-     * 供 cwd 变更重绑复用（先 disposeWatchers 再 attachAll），dispose() 也调用它。
-     */
-    private disposeWatchers;
-    private attachAll;
-    private attachRepo;
-    private scheduleScan;
-    private checkAndReport;
-}
-export interface SvnDiscoveryDeps {
-    /** 沿父链向上找工作副本根；默认用 `findSvnWorkingCopyRoot`。 */
-    findUpRoot?: (startPath: string) => string | undefined;
-    /** 判断某目录是否是 svn 工作副本根；默认用 `isSvnWorkingCopy`。 */
-    isWorkingCopy?: (dir: string) => boolean;
-    /** 列出某目录下的直接「子目录绝对路径」；默认走 fs.readdirSync。 */
-    listSubdirectories?: (dir: string) => string[];
-    /** 向下扫描最大深度。 */
-    maxDepth?: number;
-    /** 发现的工作副本数量上限。 */
-    maxRepos?: number;
-    /** 诊断回调：把扫描过程打到日志。 */
-    onTrace?: (msg: string) => void;
-}
-/**
- * 从 `cwd` 发现需要监听的全部 svn 工作副本根：
- *
- *   1. 先沿父链向上找：若 `cwd` 本身或其某个祖先是工作副本，则视为「打开了工作
- *      副本（或其子目录）」，直接返回该唯一根（其下子目录都属于同一个 wc）。
- *   2. 否则向下有限层扫描子目录，把每个含 `.svn` 的目录当成独立工作副本根，
- *      命中后剪枝不再深入（兼容 svn 1.7+「整棵 wc 只有顶层一个 .svn」的布局，
- *      也避免把 1.6 时代每级目录的 .svn 误判成多个仓库）。
- *
- * 纯函数 + 依赖注入，便于单测，不直接耦合真实 fs。
- */
-export declare function discoverSvnWorkingCopies(cwd: string, deps?: SvnDiscoveryDeps): string[];
-interface SvnUserCandidateOptions {
-    env?: NodeJS.ProcessEnv;
-    repoUrls?: Array<string | undefined>;
-    authCacheDirs?: string[];
-    readDir?: (dirPath: string) => string[];
-    readFile?: (filePath: string) => string;
-}
-/**
- * 计算当前 SVN 用户候选集。不再与操作系统登录用户绑定：
- *   - 显式环境变量 `SVN_USER` / `SVN_USERNAME`；
- *   - SVN auth cache（`~/.subversion/auth/svn.simple/*` 或 Windows `%APPDATA%`），
- *     按当前仓库 URL 匹配 realm 后取 username。
- * 读不到任何身份时返回空数组，调用方据此「未知身份不放行」，避免 svn update 误报。
- */
-export declare function getLikelyCurrentSvnUserCandidates(options?: SvnUserCandidateOptions): string[];
-export declare function isLikelyCurrentUser(author: string | undefined, currentUserCandidates?: string[]): boolean;
-export {};

package/cli/dist-server/types/node/code-ratio/code-ratio-reporting-service.d.ts

@@ -1,90 +0,0 @@
-import { Session } from '../../vendor/cbc-core/node/index.js';
-import { CodeRatioReporter } from '@genie/code-ratio';
-import { CodeRatioRepoResolver } from './vcs-repo-resolver';
-/**
- * Service token for the CLI-side code-ratio reporting helper.
- *
- * Editor tools depend on this token instead of the raw `CodeRatioReporter`
- * so they don't need to know how to resolve VCS context, map ChangeType
- * values or swallow reporter errors. All of that lives here.
- */
-export declare const CodeRatioReportingService: unique symbol;
-/**
- * Minimal, CLI-friendly parameters for the edit tools' code-ratio
- * reporting hook. Tools already have these values on hand after
- * successfully applying an edit, so building the input is a one-liner.
- */
-export interface EditChangeReport {
-    /** Absolute path of the file that was just written / edited. */
-    absoluteFilePath: string;
-    /** File content before the edit (empty string for new files). */
-    originalContent: string;
-    /** File content after the edit. */
-    newContent: string;
-    /** Whether this edit created a new file (drives ChangeType). */
-    isNewFile: boolean;
-    /** Tool name (e.g. `Write`, `Edit`, `MultiEdit`, `NotebookEdit`). */
-    toolName?: string;
-    /** Tool call identifier, if available from the agent runtime. */
-    toolCallId?: string;
-    /** Session context, used to derive conversationId / modelId / traceId. */
-    session?: Session;
-}
-/**
- * CLI-side code-ratio reporting helper.
- *
- * Contract: calling `reportEditChange` never throws, never blocks the
- * edit flow and never affects the tool's return value. Any failure
- * (missing reporter, non-git workspace, VCS metadata incomplete, etc.)
- * is logged at debug level and silently dropped.
- */
-export interface CodeRatioReportingService {
-    /**
-     * Report an AI-authored file change (Write / Edit / MultiEdit /
-     * NotebookEdit / NotebookWrite). Safe to call unconditionally after a
-     * successful file write.
-     */
-    reportEditChange(report: EditChangeReport): void;
-}
-/**
- * Default implementation. The reporter and resolver are looked up
- * through the cell container rather than enforced through strict DI,
- * because `@genie/code-ratio` is an optional peer dependency: builds
- * that don't bundle it (or tests that don't register it) must still
- * be able to instantiate the editor tools.
- *
- * Constructor arguments exist purely for unit tests; production code
- * relies on the cell container resolution below.
- */
-export declare class CodeRatioReportingServiceImpl implements CodeRatioReportingService {
-    protected readonly repoResolver?: CodeRatioRepoResolver;
-    private logger?;
-    private reporterProvider;
-    /**
-     * NOTE: must remain parameter-less.
-     *
-     * 早期版本曾把 unit-test overrides 通过构造函数对象参数注入，触发了一个
-     * 隐蔽的 cell/inversify bug：`@Component` 装饰会让 TS emit
-     * `design:paramtypes` 元数据，把 `overrides?: { ... }` 的对象类型擦成
-     * `Object`；cell 容器实例化时会按 paramtypes 在容器里查找 `Object` 的
-     * 绑定，由于不存在，统一抛出
-     *   "No matching bindings found for serviceIdentifier: Object"
-     * 该错误从 ApplicationLifecycle 一路冒泡，导致整个 CLI 启动失败。
-     *
-     * 修复：constructor 改为无参，单测改用 {@link configureForTesting}
-     * 注入测试桩，从而**完全不让 paramtypes 元数据被生成**。
-     */
-    constructor();
-    /**
-     * Test-only seam. Production code must not call this.
-     *
-     * 不通过 constructor 注入是为了避免 cell 装饰器生成 `design:paramtypes`
-     * 元数据，把测试用的 overrides 对象类型当成 IoC 依赖（详见 constructor
-     * 注释里的 bug 历史）。
-     */
-    configureForTesting(overrides: {
-        repoResolver?: CodeRatioRepoResolver;
-        reporterProvider?: () => CodeRatioReporter | undefined;
-    }): void;
-    reportEditChange(report: EditChangeReport): void;
-}

package/cli/dist-server/types/node/code-ratio/fs-file-reader.d.ts

@@ -1,26 +0,0 @@
-import { CodeRatioFileReader } from '@genie/code-ratio';
-/**
- * CLI-side implementation of CodeRatioFileReader.
- *
- * The five editor tools (write / edit / multi-edit / notebook-edit /
- * notebook-write) already have `originalContent` in hand when they call
- * into the reporter, so this reader is a defensive fallback: the
- * reporter itself will invoke it only when the caller omits `oldContent`.
- *
- * Input is a POSIX, repo-relative path (per the protocol). We resolve it
- * against the current repo root (provided by CodeRatioRepoResolver) and
- * read through `FileUtils.readFileWithEncodingDetection`, which reuses
- * the same encoding detection that the edit tools use for writing, so
- * the old/new content pair stays byte-comparable for diffing.
- *
- * Failure policy: any error (missing resolver, path outside the repo,
- * file does not exist, permission denied, encoding failure, ...) is
- * swallowed and `undefined` is returned. The reporter then treats it as
- * `invalid-input` and skips the upload, never breaking the tool flow.
- */
-export declare class FsFileReader implements CodeRatioFileReader {
-    private logger?;
-    constructor();
-    readFile(filePath: string): Promise<string | undefined>;
-    private resolveAbsolute;
-}

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

@@ -1,5 +0,0 @@
-export * from './vcs-repo-resolver';
-export * from './fs-file-reader';
-export * from './code-ratio-reporting-service';
-export * from './cli-git-commit-watcher';
-export * from './cli-svn-commit-watcher';

package/cli/dist-server/types/node/code-ratio/repo-discovery.d.ts

@@ -1,32 +0,0 @@
-/**
- * 入库率端侧 watcher 的「多仓发现」共享逻辑（git / svn 通用）。
- *
- * 同时覆盖两类打开方式：
- *   1. 直接打开仓库（或其子目录）：沿父链向上找到唯一仓库根，返回该根。
- *   2. 打开一个父目录、其下挂多个独立仓库：向下有限层扫描子目录，
- *      把每个仓库根收集出来，命中后剪枝不再深入。
- *
- * 纯函数 + 依赖注入，便于单测，不直接耦合真实 fs / 具体 VCS 判定。
- */
-/** 向下扫描发现多仓时的最大深度。深度 1~2 即可覆盖常见场景，3 兼容 `group/project` 再套一层。 */
-export declare const DEFAULT_REPO_SCAN_MAX_DEPTH = 3;
-/** 向下扫描发现的仓库数量上限，避免在超大目录树里无限扫描。 */
-export declare const DEFAULT_MAX_VCS_REPOS = 50;
-/** 向下扫描时跳过的噪音目录，避免进 node_modules / 构建产物等大目录。 */
-export declare const REPO_SCAN_SKIP_DIR_NAMES: Set<string>;
-export interface VcsRootDiscoveryDeps {
-    /** 沿父链向上找仓库根。返回 undefined 表示 cwd 及其祖先都不是仓库。 */
-    findUpRoot?: (startPath: string) => string | undefined;
-    /** 判断某目录是否是仓库根。 */
-    isRoot?: (dir: string) => boolean;
-    /** 列出某目录下的直接「子目录绝对路径」。 */
-    listSubdirectories?: (dir: string) => string[];
-    /** 向下扫描最大深度。 */
-    maxDepth?: number;
-    /** 发现的仓库数量上限。 */
-    maxRepos?: number;
-    /** 可选的诊断回调：用于把扫描过程打到日志，便于线上定位「为什么没发现仓库」。 */
-    onTrace?: (msg: string) => void;
-}
-export declare function discoverVcsRoots(cwd: string, deps?: VcsRootDiscoveryDeps): string[];
-export declare function defaultListSubdirectories(dir: string): string[];

package/cli/dist-server/types/node/code-ratio/vcs-repo-resolver.d.ts

@@ -1,51 +0,0 @@
-import { CodeRatioRepoContext, CodeRatioRepoResolver } from '@genie/code-ratio';
-export { CodeRatioRepoContext, CodeRatioRepoResolver, toPosixRelative } from '@genie/code-ratio';
-export interface VcsRoot {
-    repoRoot: string;
-    vcsType: NonNullable<CodeRatioRepoContext['vcsType']>;
-}
-/**
- * CLI-native implementation of CodeRatioRepoResolver.
- *
- * Unlike agent-craft which can lean on the vscode git extension via
- * VCSManager, the CLI only has filesystem access. We walk up from the
- * given absolute file path to locate the nearest `.git` directory and
- * read remote/branch info through GitInfoExtractor (already used by the
- * existing VCSEventProcessor, so behavior stays consistent).
- *
- * Results are cached per repo root with a 5-minute TTL, matching the
- * cache strategy of VCSEventProcessor.
- */
-export declare class CwdRepoResolver implements CodeRatioRepoResolver {
-    private readonly cache;
-    private logger?;
-    constructor();
-    resolve(absoluteFilePath: string): CodeRatioRepoContext | undefined;
-    getCurrentRepoRoot(): string | undefined;
-    private getRepoEntry;
-    private readGitRepoEntry;
-    private readSvnRepoEntry;
-}
-/**
- * Walk upwards from `startPath` looking for the nearest VCS working copy.
- *
- * SVN is checked alongside Git at every directory level instead of falling
- * back after Git lookup. This matters when an SVN working copy lives inside a
- * Git-managed parent directory: codeDiff must use `vcsType=svn` for files in
- * that working copy rather than inheriting the outer Git repository.
- *
- * Exported for unit testing.
- */
-export declare function findVcsRoot(startPath: string): VcsRoot | undefined;
-/**
- * Git-only compatibility helper retained for existing tests/callers.
- */
-export declare function findRepoRoot(startPath: string): string | undefined;
-/**
- * Strip credentials from a git remote URL. Mirrors the logic used by
- * VCSEventProcessor so that both paths produce identical `repoUrl`
- * values downstream.
- *
- * Exported for unit testing.
- */
-export declare function clearSensitiveData(gitUrl: string): string;

package/cli/dist-server/types/node/control-signal/stdout-writer.d.ts

@@ -1,99 +0,0 @@
-import { type StdioChannel } from '../utils/stdio-persistence';
-export declare const StdoutWriter: unique symbol;
-export interface StdoutWriter {
-    /** Serialize `data` as one JSON line. Never throws. */
-    write(data: unknown): void;
-    /** Enqueue a pre-serialized single line (trailing newline appended if missing). Never throws. */
-    writeLine(line: string): void;
-    /** Resolves once every enqueued line has been handed to the fd (or dropped on error). */
-    flush(): Promise<void>;
-    /**
-     * Wait for the queue to drain with a STALL bound rather than an absolute one:
-     * as long as the consumer keeps accepting writes (progress), keep waiting —
-     * a slow-but-alive consumer is never cut off. Give up only after
-     * `stallTimeoutMs` of ZERO progress (consumer provably stuck/gone).
-     * Never rejects.
-     */
-    flushOrStall(stallTimeoutMs: number): Promise<{
-        complete: boolean;
-        remainingBytes: number;
-    }>;
-    /** Number of lines dropped because the physical write failed. */
-    readonly failedWrites: number;
-    /**
-     * Attach（or 替换）stdio 持久化通道；未 attach 时 tap 是 no-op。
-     * 由 stream-json 模式的驱动逻辑在拿到 sessionId 后调用；调用前累积的
-     * 消息通过 attach 时可选传入的 `backlog` 一次性回放到通道。
-     *
-     * 传 null 显式清除。
-     */
-    attachPersistChannel(channel: StdioChannel | null, backlog?: unknown[]): void;
-    /**
-     * 打开 pre-attach 输出缓冲。开启后 `writeLine` 会把每条消息同时压进内部
-     * 缓冲区（cap 4096），直到 `attachPersistChannel` 时统一回放到通道并清空。
-     * 未 arm 时不缓冲，热路径零额外开销。
-     *
-     * 由 stream-json 驱动逻辑在 executeStreamMode 入口调用，因为此时 sessionId
-     * 尚未拿到但 stdout 已经会发出 initialize control_response / system init
-     * 等消息 —— 不预缓冲这些消息就永远无法落盘。
-     */
-    armPersistPrebuffer(): void;
-    /**
-     * CLI 退出前 flush 已 attach 的持久化通道。未 attach 时立即 resolve。
-     * 永不 reject —— 落盘失败在 append 阶段已被静默计数。
-     */
-    flushPersistChannel(): Promise<void>;
-}
-export declare class StdoutWriterImpl implements StdoutWriter {
-    private queue;
-    private queuedBytes;
-    private inFlightBytes;
-    private pumping;
-    private idleWaiters;
-    /** Invoked after each physical write settles — the stall detector's progress signal. */
-    private progressListeners;
-    private _failedWrites;
-    private loggedFailures;
-    /**
-     * stdio 持久化通道。由 stream-json 驱动逻辑在拿到 sessionId 后 attach。
-     * 未 attach 时 `tapPersist` 是 no-op，热路径无额外开销。
-     */
-    private persistChannel;
-    /**
-     * attach 之前所有 stdout 消息的 pre-attach 缓冲。sessionId 在首个 HTTP
-     * response 之后才知道；response 到手时 CLI 通常已经 stdout 推过 initialize
-     * control_response / system init / status / file-history-snapshot / 甚至
-     * error result 等消息 —— 不缓冲就永远拿不到这些"session 生成前"的 stdout。
-     * cap 防内存爆炸；启用 stdio 持久化时才积累（`_persistArmed` 门控）。
-     */
-    private outputPrebuffer;
-    private _persistArmed;
-    private static readonly PREBUFFER_CAP;
-    get failedWrites(): number;
-    attachPersistChannel(channel: StdioChannel | null, backlog?: unknown[]): void;
-    armPersistPrebuffer(): void;
-    flushPersistChannel(): Promise<void>;
-    private tapPersist;
-    private appendChunkToChannel;
-    write(data: unknown): void;
-    writeLine(line: string): void;
-    flush(): Promise<void>;
-    flushOrStall(stallTimeoutMs: number): Promise<{
-        complete: boolean;
-        remainingBytes: number;
-    }>;
-    private kickPump;
-    private pump;
-    /**
-     * One physical write. Resolves when the runtime reports the chunk as
-     * handled (callback fired) — success or failure alike; failures are
-     * counted and logged, never thrown.
-     */
-    private writeChunk;
-    /**
-     * Log to the file logger only — stdout itself is the failing component,
-     * so no console fallback. Throttled: the first failure and then every
-     * 100th, to avoid log storms while keeping the signal.
-     */
-    private reportFailure;
-}

package/cli/dist-server/types/node/elicitation/elicitation-service.d.ts

@@ -1,100 +0,0 @@
-import { type CreateElicitationResponse } from '@genie/agent-client-protocol';
-import { Session } from '../../vendor/cbc-core/node/index.js';
-import { Logger } from '@genie/telemetry';
-import { AcpAgent } from '../acp/acp-protocol';
-import { SdkElicitationClient, SdkHooksManager } from '../control-signal/control-signal-protocol';
-/**
- * QR / 表单类交互远超单次交互点击时间尺度；与 AskService 的 10 分钟一致。
- * 调用方可通过 `elicit(options.timeoutMs)` 覆盖。
- */
-export declare const ELICITATION_DEFAULT_TIMEOUT_MS: number;
-/** Prevent an untrusted client response from adding unbounded text to model context. */
-export declare const ELICITATION_RESPONSE_REASON_MAX_LENGTH = 2000;
-/**
- * elicitation 通道目标。两条等价通道，协议形状一致（参数命名对齐 ACP）：
- * - acp：ACP 会话，经 `elicitation/create` + `elicitation/complete`；
- * - sdk：stream-json（agent-sdk-js），经 control-signal `elicitation_create`
- *   请求 + `elicitation` 频道通知。
- */
-export type ElicitationTarget = {
-    kind: 'acp';
-    agent: AcpAgent;
-    acpSessionId: string;
-} | {
-    kind: 'sdk';
-    acpSessionId: string;
-};
-export interface ElicitationRequestPayload {
-    /**
-     * 顶部提示语（客户端渲染在表单上方）。ACP 官方位置。
-     */
-    message?: string;
-    /**
-     * 收集的结构化答复的受限 JSON Schema。与 MCP elicitation 保持一致。
-     * 传空 `{ type: 'object', properties: {} }` 表示"不收集内容，只等
-     * accept/decline/cancel"（同 payment 卡片的用法）。
-     */
-    requestedSchema: Record<string, unknown>;
-    /**
-     * 可选：本次调用触发该 elicitation 的工具调用 id。写进 ACP 官方
-     * `SessionScope.toolCallId`，用于挂靠到具体的 tool_call 卡片。
-     */
-    toolCallId?: string;
-    /**
-     * 可选：SDK ≥0.25 提供的 elicitation id，跨越 create/complete 关联同一
-     * 张卡片。省略时由本 service 生成一个 `elic_<ts>_<rand>` id。
-     */
-    elicitationId?: string;
-    /**
-     * 可选：附加 `_meta` 字段。会与本 service 生成的 `_meta['codebuddy.ai']`
-     * 合并（浅合并到 `codebuddy.ai` 子键下）。
-     */
-    metaCodebuddyAi?: Record<string, unknown>;
-}
-export interface ElicitOptions {
-    /** 覆盖默认 10 分钟超时。传 0 / 非有限值走默认。 */
-    timeoutMs?: number;
-    /** 外部 abort 信号；触发时按 cancel 语义收敛并 dismiss 卡片。 */
-    signal?: AbortSignal;
-}
-export declare const ElicitationService: unique symbol;
-export interface ElicitationService {
-    /**
-     * 根据 session 解析可用的 elicitation 通道。返回 undefined 表示当前
-     * 会话不满足派发条件（无 ACP 连接 / 未声明 capability / 非 stream-json /
-     * 非 form 模式），调用方应回退到 LLM-mediated 或直接失败。
-     */
-    resolveTarget(session: Session): ElicitationTarget | undefined;
-    /**
-     * 下发 elicitation 并等待用户响应。永不 throw（包括超时/abort/传输错误），
-     * 按 ACP 官方扁平形状返回 `{ action, content?, _meta? }`；abort/timeout/
-     * 传输错误统一 map 成 `{ action: 'cancel' }`，且会尽力发一次
-     * `elicitation/complete` 让客户端把卡片翻掉。
-     */
-    elicit(target: ElicitationTarget, payload: ElicitationRequestPayload, options?: ElicitOptions): Promise<CreateElicitationResponse>;
-    /**
-     * 从响应里提取 `action` 标签；非法形状（老客户端 catch-all 回的 question
-     * 形状）返回 undefined，调用方按 cancel 处理。
-     */
-    responseAction(response: CreateElicitationResponse | undefined): 'accept' | 'decline' | 'cancel' | undefined;
-    /**
-     * 读取 CodeBuddy 扩展槽中的通用原因。只接受非空字符串，不解释或映射内容；
-     * 超长值会在安全上限处截断，避免宿主回包无限放大模型上下文。
-     */
-    responseReason(response: CreateElicitationResponse | undefined): string | undefined;
-}
-export declare class ElicitationServiceImpl implements ElicitationService {
-    protected readonly sdkHooksManager: SdkHooksManager;
-    protected readonly sdkElicitationClient?: SdkElicitationClient;
-    protected readonly logger: Logger;
-    private idCounter;
-    resolveTarget(session: Session): ElicitationTarget | undefined;
-    responseAction(response: CreateElicitationResponse | undefined): 'accept' | 'decline' | 'cancel' | undefined;
-    responseReason(response: CreateElicitationResponse | undefined): string | undefined;
-    elicit(target: ElicitationTarget, payload: ElicitationRequestPayload, options?: ElicitOptions): Promise<CreateElicitationResponse>;
-    /**
-     * Best-effort 关掉客户端仍在显示的 elicitation 卡片（超时 / abort /
-     * 传输错误后）。同 payment 侧的语义，只是不带业务终态载荷。
-     */
-    private dismiss;
-}

package/cli/dist-server/types/node/hooks/admin-trusted.d.ts

@@ -1,41 +0,0 @@
-/**
- * Admin-trusted source gate for frontmatter hooks.
- *
- * Aligns with Claude Code's `isSourceAdminTrusted` in `runAgent.ts:566`:
- * frontmatter hooks declared on user-local `.codebuddy/agents/*.md` or
- * `.codebuddy/skills/SKILL.md` can silently spawn shell commands. We gate
- * their registration so users must opt-in via the
- * `allowUntrustedFrontmatterHooks` setting, unless the source is already
- * admin-trusted (product built-in agents/skills).
- */
-import { Agent as ProductAgent, Skill } from '@genie/product';
-/**
- * An agent is admin-trusted when it's NOT tagged as a custom agent —
- * i.e. product-bundled agents shipped inside cbc itself.
- *
- * Custom agents include:
- * - `.codebuddy/agents/*.md` (user/project local)
- * - plugin marketplace agents
- *
- * Both of these default to "untrusted" for frontmatter hooks; enable via
- * the `allowUntrustedFrontmatterHooks` setting.
- */
-export declare function isAgentAdminTrusted(agent: ProductAgent | undefined): boolean;
-/**
- * A skill is admin-trusted only when it's bundled inside cbc itself
- * (future: product.skills). Currently all discovered skills come from
- * `skill-loader.ts` which unconditionally assigns `source: 'plugin'` —
- * so today this function effectively returns `false` for every skill
- * we see at runtime, forcing the `allowUntrustedFrontmatterHooks` gate.
- *
- * Called by `skill-tool.ts` when the fork path carries SKILL.md
- * `hooks:` frontmatter into the subagent lifecycle.
- */
-export declare function isSkillAdminTrusted(skill: Skill | undefined): boolean;
-/**
- * Resolve whether frontmatter hooks from a given source should be registered.
- *
- * @param isAdminTrusted Whether the source (agent/skill) is admin-trusted
- * @param allowUntrusted Settings flag `allowUntrustedFrontmatterHooks`
- */
-export declare function shouldRegisterFrontmatterHooks(isAdminTrusted: boolean, allowUntrusted: boolean | undefined): boolean;

package/cli/dist-server/types/node/http/api-galileo-metrics.d.ts

@@ -1,19 +0,0 @@
-/**
- * Chat HTTP 伽利略指标。口径与 daemon `net-galileo-metrics.ts` 对齐：
- *   wb.api.request + outcome / net_class → 成功率、P95、弱网成功率。
- *
- * agent-cli 不依赖 workbuddy-server，此处保持同名常量和分类规则。
- */
-export declare const WB_API_REQUEST_METRIC = "wb.api.request";
-export declare const WEAK_NET_DURATION_MS = 2000;
-export declare const CHAT_API_METRIC_STARTED_AT = "__wbApiMetricStartedAt";
-interface DurationReporter {
-    recordDuration(metric: string, durationMs: number, dimensions?: Record<string, string>): void;
-}
-export declare function reportChatApiRequestToGalileo(reporter: DurationReporter | undefined, input: {
-    method?: string;
-    status?: number;
-    startedAt?: number;
-    error?: unknown;
-}): void;
-export {};

package/cli/dist-server/types/node/http/classify-network-error.d.ts

@@ -1,21 +0,0 @@
-/**
- * CLI 侧网络失败原因分类器。
- *
- * 与 daemon 侧 `@genie/workbuddy-server` 的 `net/classify-network-error.ts` 保持
- * 同一套判定口径（代理 / PAC / CA / DNS / 超时 / 重置 / 拒绝），但因 agent-cli 是
- * 独立发布、不依赖 workbuddy-server，这里单独维护一份纯函数实现。改动分类规则时
- * 两处需同步。
- *
- * 目的：让 CLI 的网络失败日志能一眼区分「代理连不上 / PAC 出问题 / CA 证书校验
- * 失败」，而不是笼统一句 `fetch failed`。
- */
-export type CliNetworkErrorCategory = 'ca' | 'pac' | 'proxy' | 'dns' | 'timeout' | 'reset' | 'refused' | 'unknown';
-export interface CliNetworkErrorClassification {
-    category: CliNetworkErrorCategory;
-    code?: string;
-    detail: string;
-    chain: string;
-}
-export declare function classifyCliNetworkError(error: unknown): CliNetworkErrorClassification;
-/** 产出一行可直接落日志的 CLI 网络错误分类字符串。 */
-export declare function formatCliNetworkErrorForLog(error: unknown): string;

package/cli/dist-server/types/node/http/custom-header-http-interceptor.d.ts

@@ -1,14 +0,0 @@
-import { Application, ApplicationLifecycle } from '@celljs/core';
-import { RestOperations } from '@celljs/http';
-import { ProductManager } from '@genie/product';
-import { CustomHeadersProvider } from './custom-headers-provider';
-/**
- * 把 CODEBUDDY_CUSTOM_HEADERS 注入到打向平台 endpoint 的 RestOperations 请求。
- * 覆盖 imagegen / videogen 以及其它走 axios 单例的平台接口。
- */
-export declare class CustomHeaderHttpInterceptor implements ApplicationLifecycle<Application> {
-    protected readonly restOperations: RestOperations;
-    protected readonly productManager: ProductManager;
-    protected readonly customHeadersProvider: CustomHeadersProvider;
-    initialize(): void;
-}

package/cli/dist-server/types/node/http/fetch-proxy.d.ts

@@ -1,22 +0,0 @@
-import { Application, ApplicationLifecycle } from '@celljs/core';
-import { Logger } from '@genie/telemetry';
-/**
- * CLI 侧 fetch 代理补丁。
- *
- * 使用 ProxyResolver 按优先级链自治解析代理，
- * 失败时清除 OS 缓存并直连重试。
- */
-export declare class FetchProxy implements ApplicationLifecycle<Application> {
-    protected readonly logger: Logger;
-    private originFetch;
-    /**
-     * settingsPath 显式注入，确保 WORKBUDDY_CONFIG_DIR 被尊重
-     * （见 ProxyResolver class JSDoc 顶部 invariant）。
-     *
-     * #57186：daemon 注入 `WORKBUDDY_PAC_RPC_*` env 时自动启用 L0 PAC 反查；env
-     * 缺失时退化为 L1-L4 自治链。
-     */
-    private proxyResolver;
-    initialize(): Promise<void>;
-    onStop(): Promise<void>;
-}