aws-runtime-bridge 1.9.92 → 1.9.93

package/dist/routes/pty.d.ts

@@ -30,41 +30,23 @@ interface PtySessionEntry extends PtySessionSummary {
     persistent: boolean;
 }
 export declare const ptySessions: Map<string, PtySessionEntry>;
-/**
- * 解析 PTY 空闲清理时间。
- * 主流程：读取环境变量 -> 非法值回退默认值 -> 用于 WebSocket 全断开后的延迟清理。
- */
+
 export declare function resolvePtyIdleTtlMs(env?: NodeJS.ProcessEnv): number;
-/**
- * 选择默认 shell。
- * 主流程：Windows 优先 pwsh/powershell/cmd；Unix 优先 SHELL/bash/sh，返回可执行文件名与参数。
- */
+
 export declare function resolveDefaultShell(platform?: NodeJS.Platform, env?: NodeJS.ProcessEnv, existsSync?: (path: fs.PathLike) => boolean): {
     shell: string;
     args: string[];
 };
-/**
- * 校验并解析 shell 选择。
- * 主流程：auto 使用默认 shell；显式 shell 必须命中 allowlist，避免前端任意执行二进制。
- */
+
 export declare function resolveRequestedShell(requestedShell: unknown, platform?: NodeJS.Platform, env?: NodeJS.ProcessEnv): {
     shell: string;
     args: string[];
 };
-/**
- * 判断候选路径是否位于允许根目录中。
- * 具体逻辑：使用 path.relative 处理 Windows/Unix 分隔符，拒绝向上穿越和跨盘路径。
- */
+
 export declare function isPathInsideRoot(candidatePath: string, rootPath: string): boolean;
-/**
- * 解析并校验 PTY 工作目录。
- * 主流程：要求绝对目录存在；如果配置 AWS_PTY_ALLOWED_ROOTS，则必须位于允许根目录内。
- */
+
 export declare function resolvePtyWorkspacePath(workspacePath: unknown, env?: NodeJS.ProcessEnv): string;
-/**
- * 创建 PTY session。
- * 主流程：校验 cwd/shell -> spawn 真实 PTY -> 注册 output/exit 事件 -> 返回元数据给控制面。
- */
+
 export declare function createPtySession(input: {
     workspacePath: unknown;
     title?: unknown;
@@ -81,25 +63,16 @@ export declare function resolvePtyExitedTtlMs(env?: NodeJS.ProcessEnv): number;
 export declare function resolveMaxPtySessions(env?: NodeJS.ProcessEnv): number;
 export declare function listPtySessions(): PtySessionSummary[];
 export declare function getPtySessionSummary(id: string): PtySessionSummary | undefined;
-/**
- * 生成短期 PTY 连接令牌。
- * 主流程：确认 session 存在 -> 生成随机 token -> 记录 session 绑定和过期时间。
- */
+
 export declare function createPtyConnectToken(sessionId: string): {
     token: string;
     expiresAt: string;
 } | undefined;
-/**
- * 关闭 PTY session。
- * 主流程：关闭连接 -> kill PTY -> 清理定时器和内存索引。
- */
+
 export declare function closePtySession(id: string, reason?: string): boolean;
 export declare function closeAllPtySessions(reason?: string): void;
 export declare const ptyRouter: Router;
-/**
- * 将 PTY WebSocket upgrade 挂到 HTTP server。
- * 主流程：匹配 /pty/sessions/:id/stream -> token 校验 -> session 校验 -> 交给 noServer WSS。
- */
+
 export declare function attachPtyWebSocketServer(server: {
     on: (event: "upgrade", listener: (request: IncomingMessage, socket: Socket, head: Buffer) => void) => unknown;
 }): void;

package/dist/routes/runtime-binding.d.ts

@@ -12,9 +12,6 @@ export interface RuntimeTokenRequestResult {
     updated?: boolean;
     error?: string;
 }
-/**
- * 主流程：MCP Node token 必须通过 /runtime/binding/claim-agent 从启动绑定领取。
- * 不再返回 bridge/user/server scoped runtime token，避免 MCP Node 降级使用旧 bridge 级凭据。
- */
+
 export declare function resolveRuntimeTokenRequest(input: RuntimeTokenRequestInput): RuntimeTokenRequestResult;
 export declare function logRuntimeBindingStartupState(): void;

package/dist/routes/sessions.d.ts

@@ -1,11 +1,4 @@
-/**
- * 会话管理 API 路由
- *
- * 提供 SDK Agent 会话的查询和恢复功能
- */
+
 export declare const sessionsRouter: import("express-serve-static-core").Router;
-/**
- * 解析 active SDK 会话快照状态。
- * 主流程：优先使用 adapter 细粒度状态，其次使用 terminal 路由内存里的最近 runtimeStatus，最后兼容旧会话回退 running。
- */
+
 export declare function resolveActiveSdkSessionSnapshotStatus(adapterStatus?: string, currentRuntimeStatus?: string, currentRuntimeActionType?: string): string;

package/dist/routes/sub-agents.d.ts

@@ -1,13 +1,2 @@
-/**
- * Sub Agent HTTP 路由
- *
- * 提供/dashboard 直连 bridge 拉取 sub-agent 数据的接口：
- *   GET  /runtime/sub-agents/:agentId                     列表（含历史）
- *   GET  /runtime/sub-agents/:agentId/:subId              单个详情
- *   GET  /runtime/sub-agents/:agentId/:subId/events       SSE 实时事件流
- *   POST /runtime/sub-agents/:agentId/:subId/abort        取消运行中的 sub-agent
- *
- * 设计与 acode-todos.ts 同构：validateToken 鉴权，agentId 路径隔离。
- * 数据源：SubAgentStore（持久化历史） + SubAgentManager（运行中实时状态）。
- */
+
 export declare const subAgentsRouter: import("express-serve-static-core").Router;

package/dist/routes/task-context.d.ts

@@ -1,7 +1,2 @@
-/**
- * 任务上下文路由
- *
- * 提供调度中心设置/清除 Agent 当前活跃任务上下文的能力。
- * 文件变更监听服务据此将变更自动归属到正确的任务。
- */
+
 export declare const taskContextRouter: import("express-serve-static-core").Router;

package/dist/routes/terminal.d.ts

@@ -1,9 +1,4 @@
-/**
- * 终端 API 路由
- *
- * 提供 SDK Agent 会话的启动、输入、调整大小和停止功能
- * 终端 UI 仅作为 SDK Agent 的消息输入/状态输出载体
- */
+
 import { TextDecoder } from "node:util";
 import { type AdapterSessionConfig, type ProviderEvent, type RuntimeStatusActionInfo } from "../adapter/index.js";
 import { type RuntimeOutputMetadata } from "../services/session-output.js";
@@ -23,13 +18,7 @@ export interface SdkSessionEntry {
     currentRuntimeActionLabel?: string;
     currentRuntimeActionDetail?: string;
     currentRuntimeActionInput?: string;
-    /**
-     * runtime_capabilities 事件的 actionDetail 缓存。
-     * 修复时序竞争条件：session 启动时 "starting" 状态变更与 runtime_capabilities
-     * 几乎同时发送到服务端，若 capabilities POST 先到达且 runtime_session_id 尚未更新，
-     * 服务端会视为过期会话直接丢弃。缓存此值后，在 session 稳定到 waiting_input 时重发，
-     * 确保能力清单最终送达前端。
-     */
+    
     cachedCapabilitiesActionDetail?: string;
 }
 export declare const sdkSessions: Map<string, SdkSessionEntry>;
@@ -45,15 +34,9 @@ export type RuntimeContextResetSupport = {
     error: string;
 };
 export declare function resolveRuntimeContextResetSupport(providerId: string, hasResetContext: boolean): RuntimeContextResetSupport;
-/**
- * Decide whether SDK startup should wait for an external process PID.
- * Main flow: in-process providers return immediately; external CLI providers keep PID probing for orphan cleanup.
- */
+
 export declare function shouldProbeSdkProcessPid(providerId: string): boolean;
-/**
- * 主流程：解析 runtime stop 请求的状态通知选项。
- * 内部上下文重置可抑制 stopped 广播；普通手动停止默认继续通知调度端。
- */
+
 export declare function parseRuntimeStopOptions(body: unknown): RuntimeStopOptions;
 export declare function resolveStatusChangeUsage(actionInfo?: RuntimeStatusActionInfo): {
     inputTokens: number;
@@ -71,88 +54,46 @@ export declare function buildAcodeCommandOutputPath(agentId: string, now?: Date)
 export declare function countTerminalOutputLines(output: string): number;
 export declare function formatCommandOutputSpilloverNotice(outputPath: string, lineLimit?: number): string;
 export declare function formatCommandInactivityTimeoutNotice(timeoutMs?: number): string;
-/**
- * 标准化终端输入：将前端回车符还原为 shell 可执行命令文本。
- */
+
 export declare function normalizeTerminalCommandInput(value: unknown): string;
-/**
- * 解析终端命令输出解码编码。
- * 主流程：优先使用环境变量覆盖 -> Windows 默认 GB18030 -> 其他平台默认 UTF-8。
- */
+
 export declare function resolveTerminalOutputEncoding(platform?: NodeJS.Platform, env?: NodeJS.ProcessEnv): string;
-/**
- * 终端输出解码器接口。
- */
+
 interface TerminalOutputDecoder {
     decode(chunk?: Uint8Array | ArrayBuffer | null, options?: {
         stream?: boolean;
     }): string;
 }
-/**
- * 创建终端输出流式解码器，避免多字节中文被 chunk 边界截断。
- *
- * 主流程：环境变量显式指定非 utf-8 时固定编码 → 否则自动检测
- * （先 UTF-8，遇替换字符回退 GB18030，覆盖不同程序的不同编码）。
- */
+
 export declare function createTerminalOutputDecoder(encoding?: string): TerminalOutputDecoder;
-/**
- * 解码终端输出 chunk；end=true 时刷新解码器内部剩余字节。
- */
+
 export declare function decodeTerminalOutputChunk(decoder: TerminalOutputDecoder | TextDecoder, chunk?: Buffer, end?: boolean): string;
-/**
- * 解析 cd 命令目标；返回 undefined 表示不是目录切换命令，null 表示仅查看当前目录。
- */
+
 export declare function parseTerminalDirectoryChangeTarget(command: string): string | null | undefined;
-/**
- * 解析 SDK 会话对外展示状态。
- * 主流程：优先使用 adapter 当前细粒度状态，其次使用路由内存记录的最近状态，最后才兼容旧会话回退 running。
- */
+
 export declare function resolveSdkSessionDisplayStatus(adapterStatus?: string, currentRuntimeStatus?: string, currentRuntimeActionType?: string): string;
 export interface PersistedSessionReuseDecision {
     reusable: boolean;
     reason: "active-pid" | "missing-pid" | "dead-pid" | "in-process-provider";
 }
-/**
- * Decide whether a persisted SDK session can be reused for a start request.
- * Main flow: require a live PID, then reject in-process providers whose adapter control channel cannot be restored.
- */
+
 export declare function evaluatePersistedSessionReuse(session: Pick<PersistedSession, "pid"> & Partial<Pick<PersistedSession, "command">>, isPidRunning?: (pid: number) => boolean): PersistedSessionReuseDecision;
-/**
- * 根据 agentId 清理 SDK 会话的所有内存状态。
- *
- * 用于强制停止（force-kill）场景：当进程已被外部/强制手段终止后，
- * 此函数清理 bridge 内部的内存残留（sdkSessions、statusRefreshTimers、
- * startingAgents、terminalCommandStates），防止下次启动时
- * findActiveSdkSessionByAgentId 命中旧条目导致「无法上线」。
- *
- * @param agentId - 要清理的 Agent ID
- * @returns 如果找到并清理了会话则返回 sessionId，否则返回 undefined
- */
+
 export declare function cleanupSdkSessionByAgentId(agentId: string): string | undefined;
-/**
- * 生成显示在终端输出流中的工作目录提示符。
- */
+
 export declare function formatTerminalPrompt(currentDirectory: string): string;
 export declare function buildRuntimeEnv(agentId: string, workspacePath: string | undefined, baseEnv: NodeJS.ProcessEnv, envOverrides?: Record<string, unknown>): Record<string, string>;
-/**
- * 主流程：SDK 模式输入若只是 mini-term 剪贴板临时文件路径，则展开为文件内容再发给模型。
- * 具体实现：只处理整串匹配的绝对临时 paste 文件路径，避免影响显式 `type "path"` 等正常命令。
- */
+
 export declare function resolveSdkInputMessage(input: unknown): Promise<string>;
 export interface ClaudeCodeLaunchConfig {
     envOverrides: Record<string, string>;
     model?: string;
 }
-/**
- * 主流程：将已持久化的 ClaudeCode AI 配置合并到启动配置，再让请求级覆盖保持最高优先级。
- */
+
 export declare function buildClaudeCodeLaunchConfig(savedClaudeConfig: {
     env?: Record<string, unknown>;
 } | null | undefined, requestEnvOverrides?: Record<string, unknown>): ClaudeCodeLaunchConfig;
-/**
- * 将 SDK 工具结束事件转换为时间线返回数据状态。
- * 主流程：格式化工具结果 -> 保留 MCP 专用展示 -> 其它工具按动作类型追加到对应时间线事件。
- */
+
 export declare function buildToolResultTimelineActionInfo(event: ProviderEvent): RuntimeStatusActionInfo | undefined;
 export declare function formatSdkOutputEvent(event: ProviderEvent): string | undefined;
 export declare function buildSdkOutputMetadata(event: ProviderEvent): RuntimeOutputMetadata;
@@ -160,22 +101,7 @@ export declare function resolveRuntimeStatusFromProviderEvent(event: ProviderEve
     status: string;
     actionInfo?: RuntimeStatusActionInfo;
 } | undefined;
-/**
- * 带超时 + 重试的 sendOutput 包装器。
- * ★ 修复 BUG：原 raceSendOutput 超时后仅放行队列，不取消底层请求，
- *   导致顺序错乱 + 切断合法重试。新方案：
- *   1. AbortController 在超时时真正取消底层 axios 请求（防止迟到请求污染顺序）
- *   2. 超时或 sendOutput 抛出非 abort 错误后重试（最多 2 次，1s/2s 退避），
- *      覆盖瞬时网络问题 / 服务端 5xx / axios 超时等
- *   3. 服务端按 (agentId, sessionId, seq) 幂等去重，即使超时的请求最终到达也不会重复
- *   4. 所有重试失败后 resolve（不 reject），放行队列下一条
- *   5. 成功路径必须 clearTimeout，否则 30s 后 timeout promise reject 无人 await，
- *      触发 unhandledRejection 导致进程崩溃
- *
- * @param factory - 接收 AbortSignal，返回 sendOutput Promise（每次重试创建新请求）
- * @param timeoutMs - 单次请求超时
- * @param maxRetries - 最大重试次数（不含首次）
- */
+
 export declare function raceSendOutputWithRetry(factory: (signal: AbortSignal) => Promise<void>, timeoutMs?: number, maxRetries?: number): Promise<void>;
 export declare function resolveSdkProviderId(command?: string): string;
 export {};

package/dist/routes/yml.d.ts

@@ -1,6 +1,2 @@
-/**
- * YAML 配置文件 API 路由
- *
- * 提供 YAML 配置文件的读取和写入功能
- */
+
 export declare const ymlRouter: import("express-serve-static-core").Router;

package/dist/services/acode-package.d.ts

@@ -1,14 +1,4 @@
-/**
- * 获取 ACode 入口文件路径。
- * 本地开发模式：直接使用项目下 package/acode/dist/index.js（修改即生效，无需复制）。
- * 部署模式：~/.aws-bridge/acode/dist/index.js。
- */
+
 export declare function getReleasedAcodeEntryPath(): string;
-/**
- * 释放随 bridge 打包的内置 ACode runtime。
- *
- * 本地开发模式：直接使用项目下 package/acode/dist，跳过复制（修改源码后重新 build 即生效）。
- * 部署模式：复制 dist 与 metadata 到 ~/.aws-bridge/acode，链接 bridge node_modules，
- * 确保 ACode 无需安装即可被 Adapter 动态加载。
- */
+
 export declare function ensureAcodePackageReleased(): string | null;

package/dist/services/agent-event-store.d.ts

@@ -1,9 +1,4 @@
-/**
- * Agent 事件存储
- *
- * 为每个 agent 维护独立的事件环状缓冲区，支持事件追加和输出合并。
- * scheduleEventPush 会消费 entry 进行差量推送。
- */
+
 import { type RingBufferEntry } from "./ring-buffer.js";
 export interface BridgeEventPayload {
     readonly category: "status" | "output" | "question" | "file_changed";
@@ -30,32 +25,17 @@ export interface BridgeEventPayload {
     readonly eventType?: string;
     readonly size?: number;
 }
-/**
- * per-agent 事件存储。
- * 每条 append/appendOrMergeOutput 调用会写入对应 agent 的环状缓冲区，
- * 并返回 RingBufferEntry 供 scheduleEventPush 消费。
- */
+
 declare class AgentEventStore {
     private readonly agents;
     private ensureBuffer;
-    /**
-     * 追加一条事件到指定 agent 的缓冲区。
-     * @returns 新创建的条目
-     */
+    
     append(agentId: string, payload: BridgeEventPayload): RingBufferEntry<BridgeEventPayload>;
-    /**
-     * 追加一条 output 事件到指定 agent 的缓冲区。
-     * 若最后一条也是 output 且来自同一 session + sourceEventType，
-     * 则在 10s 窗口内合并内容。
-     * ★ 修复 BUG：合并到 8000 上限后开新条目，而不是无脑截断头部丢内容。
-     * @returns 被合并或新创建的条目
-     */
+    
     appendOrMergeOutput(agentId: string, payload: BridgeEventPayload): RingBufferEntry<BridgeEventPayload>;
-    /**
-     * 获取指定 agent 的事件数量。
-     */
+    
     size(agentId: string): number;
 }
-/** 全局单例 */
+
 export declare const agentEventStore: AgentEventStore;
 export {};

package/dist/services/agent-process-manager.d.ts

@@ -1,15 +1,7 @@
-/**
- * Agent Process Manager
- *
- * Core lifecycle manager for agent processes on the bridge machine.
- * Provides comprehensive process management including creation, discovery,
- * monitoring, termination, and orphan reclamation capabilities.
- */
+
 import { type ProcessRecord, type ProcessState, type HealthStatus } from './process-registry.js';
 import { type ProcessInfo, type ProcessHealthStatus } from './process-detector.js';
-/**
- * Process configuration for starting a new agent process
- */
+
 export interface ProcessConfig {
     agentId: string;
     sessionId: string;
@@ -18,16 +10,12 @@ export interface ProcessConfig {
     workspacePath: string;
     command: string;
 }
-/**
- * Discovered process with management status
- */
+
 export interface DiscoveredProcess extends ProcessInfo {
     managementStatus: 'managed' | 'orphan' | 'unknown';
     sessionId?: string;
 }
-/**
- * Termination result with escalation level details
- */
+
 export interface TerminationResult {
     success: boolean;
     agentId: string;
@@ -37,164 +25,55 @@ export interface TerminationResult {
     failed: number;
     message: string;
 }
-/**
- * Reclamation result
- */
+
 export interface ReclamationResult {
     success: boolean;
     pid: number;
     action: 'adopted' | 'terminated' | 'failed';
 }
-/**
- * Agent Process Manager
- *
- * Manages the complete lifecycle of agent processes including:
- * - Creation: Register and verify new processes
- * - Discovery: Scan for managed, orphan, and unknown processes
- * - Monitoring: Health checks and heartbeat tracking
- * - Termination: Graceful stop with escalation strategy
- * - Orphan Reclamation: Adopt or terminate orphan processes
- */
+
 export declare class AgentProcessManager {
     private static instance;
     private readonly registry;
-    /**
-     * Private constructor - use getAgentProcessManager() for singleton access
-     */
+    
     private constructor();
-    /**
-     * Get the singleton instance
-     */
+    
     static getInstance(): AgentProcessManager;
-    /**
-     * Start a new process and register it in the process registry
-     *
-     * Flow:
-     * 1. Register process with state='creating'
-     * 2. Verify it's running
-     * 3. Update state to 'running'
-     *
-     * @param config - Process configuration
-     * @throws Error if process registration fails or process is not running
-     */
+    
     startProcess(config: ProcessConfig): Promise<void>;
-    /**
-     * Discover all agent processes on the system
-     *
-     * Scans OS for all agent processes, compares with registry, and returns
-     * a list of discovered processes with their management status.
-     *
-     * @returns Array of discovered processes with management status
-     */
+    
     discoverAllProcesses(): Promise<DiscoveredProcess[]>;
-    /**
-     * Check health of all registered processes
-     *
-     * Updates heartbeat and health status in registry for each managed process.
-     *
-     * @returns Map of agentId to health status
-     */
+    
     healthCheckAll(): Promise<Map<string, ProcessHealthStatus>>;
-    /**
-     * Check health of a single process
-     *
-     * @param agentId - Agent ID to check
-     * @returns Health status of the process
-     */
+    
     healthCheck(agentId: string): Promise<ProcessHealthStatus>;
-    /**
-     * Stop a process with graceful escalation strategy
-     *
-     * Escalation levels:
-     * Level 1: SIGTERM → wait 3s
-     * Level 2: taskkill /T /F (Win) or kill -9 (Unix) → wait 3s
-     * Level 3: terminateProcessTree → wait 5s
-     * Level 4: mark as "unstoppable", return failure
-     *
-     * @param agentId - Agent ID to stop
-     * @returns Termination result with details
-     */
+    
     stopProcess(agentId: string): Promise<TerminationResult>;
-    /**
-     * Send SIGTERM to a process
-     */
+    
     private sendSigterm;
-    /**
-     * Send force kill (SIGKILL on Unix, taskkill /F on Windows)
-     */
+    
     private sendForceKill;
-    /**
-     * Force kill a process immediately using terminateProcessTree
-     *
-     * This bypasses the graceful escalation and uses the most aggressive
-     * termination method immediately.
-     *
-     * @param agentId - Agent ID to force kill
-     * @returns Termination result
-     */
+    
     forceKill(agentId: string): Promise<TerminationResult>;
-    /**
-     * Reclaim an orphan process by agentId
-     *
-     * Finds an orphan process by agentId, and either:
-     * - Adopts it into the registry (if found and not managed)
-     * - Terminates it (if adoption fails or process is problematic)
-     *
-     * @param agentId - Agent ID to find and reclaim
-     * @returns Reclamation result
-     */
+    
     reclaimOrphan(agentId: string): Promise<ReclamationResult>;
-    /**
-     * Scan all orphans and attempt to reclaim each
-     *
-     * @returns Array of reclamation results
-     */
+    
     scanAndReclaimAll(): Promise<Array<{
         agentId: string;
         pid: number;
         action: string;
     }>>;
-    /**
-     * Mark a process as orphaned in the registry
-     *
-     * @param agentId - Agent ID to mark
-     * @returns Whether the operation succeeded
-     */
+    
     markOrphaned(agentId: string): Promise<boolean>;
-    /**
-     * Check if a process is managed
-     *
-     * @param agentId - Agent ID to check
-     * @returns Whether the process is managed
-     */
+    
     isManaged(agentId: string): boolean;
-    /**
-     * Get all managed processes
-     *
-     * @returns Array of all managed process records
-     */
+    
     getAllManagedProcesses(): ProcessRecord[];
-    /**
-     * Get managed processes by state
-     *
-     * @param state - Process state to filter by
-     * @returns Array of process records matching the state
-     */
+    
     getManagedProcessesByState(state: ProcessState): ProcessRecord[];
-    /**
-     * Find processes running on the machine that are NOT in registry
-     *
-     * @returns Array of unmanaged process info
-     */
+    
     getUnmanagedProcesses(): Promise<ProcessInfo[]>;
-    /**
-     * Rebuild the process registry from persisted sessions (e.g. on startup)
-     *
-     * Scans all persisted sessions, checks which processes are still running,
-     * and registers them with appropriate state.
-     *
-     * @param sessions - Array of persisted session data
-     */
+    
     rebuildRegistry(sessions: Array<{
         agentId: string;
         sessionId: string;
@@ -203,50 +82,17 @@ export declare class AgentProcessManager {
         command?: string;
         mode?: 'sdk';
     }>): Promise<void>;
-    /**
-     * Get process statistics
-     *
-     * @returns Statistics for all managed processes
-     */
+    
     getStats(): Record<ProcessState | 'total', number>;
-    /**
-     * Clean up stale registry entries
-     *
-     * Removes records where:
-     * - state is 'terminated' or 'unknown'
-     * - the process is no longer running
-     *
-     * This prevents dead entries from accumulating and inflating counts.
-     *
-     * @returns Number of entries removed
-     */
+    
     cleanupStaleRegistry(): Promise<number>;
-    /**
-     * Remove a process from registry
-     *
-     * @param agentId - Agent ID to remove
-     * @returns Whether the operation succeeded
-     */
+    
     removeProcess(agentId: string): Promise<boolean>;
-    /**
-     * Get a single process record
-     *
-     * @param agentId - Agent ID to get
-     * @returns Process record or undefined
-     */
+    
     getProcess(agentId: string): ProcessRecord | undefined;
-    /**
-     * Get a process record by PID
-     *
-     * @param pid - Process ID to get
-     * @returns Process record or undefined
-     */
+    
     getProcessByPid(pid: number): ProcessRecord | undefined;
 }
-/**
- * Get the AgentProcessManager singleton instance
- *
- * @returns AgentProcessManager instance
- */
+
 export declare function getAgentProcessManager(): AgentProcessManager;
 export type { ProcessRecord, ProcessState, HealthStatus, ProcessInfo, ProcessHealthStatus };

package/dist/services/ai-source-apply.d.ts

@@ -40,7 +40,5 @@ export interface AppliedAiConfigSummary {
         opencode: OpenCodeConfig | null;
     };
 }
-/**
- * 主流程：用当前统一 AI 配置覆盖各 Agent CLI 配置，并跳过未安装 CLI。
- */
+
 export declare function applyCurrentAiConfigToInstalledTools(options: ApplyCurrentAiConfigOptions): Promise<AppliedAiConfigSummary>;