@aotui/runtime 1.0.0

package/dist/adapters/bridge/index.d.ts

@@ -0,0 +1,94 @@
+import { IKernel, Operation, OperationResult, SnapshotID, DesktopID, UpdateSignal, CachedSnapshot, IBridge, BridgeSnapshot } from '../../spi/index.js';
+/**
+ * Bridge - Runtime 与外部的 I/O 边界
+ *
+ * 实现 IBridge 接口，作为 Agent（或 AgentDriver）与 Runtime 交互的标准实现。
+ *
+ * 职责:
+ * 1. 获取/释放 Snapshot
+ * 2. 执行 Operations
+ * 3. 订阅 UpdateSignal
+ *
+ * [Phase 6] 增强以支持 @aotui/agent-driver 集成
+ * [M2 FIX] 实现 IBridge 接口，支持 Mock 和替换
+ */
+export declare class Bridge implements IBridge {
+    private kernel;
+    private desktopId;
+    private ownerId;
+    private activeSnapshotId;
+    private signalListeners;
+    private debounceTimer;
+    private pendingSignal;
+    private debounceMs;
+    constructor(kernel: IKernel, desktopId: DesktopID, ownerId: string, options?: {
+        debounceMs?: number;
+    });
+    /**
+     * 获取 Desktop 快照
+     *
+     * @alias getSnapshot (保持向后兼容)
+     */
+    acquireSnapshot(): Promise<CachedSnapshot>;
+    /**
+     * [IBridge] 获取 Desktop 快照
+     *
+     * 适配 IBridge 接口，返回简化的 BridgeSnapshot。
+     */
+    getSnapshot(): Promise<BridgeSnapshot>;
+    /**
+     * 释放快照
+     */
+    releaseSnapshot(snapshotId: string): void;
+    /**
+     * 批量执行 Operations (IBridge 兼容)
+     *
+     * 调用者提供完整的 Operation[] 和 snapshotId
+     */
+    /**
+     * [IBridge] 执行一批操作
+     *
+     * 适配 IBridge 接口。
+     */
+    execute(operations: Operation[], snapshotId: string): Promise<OperationResult[]>;
+    /**
+     * 批量执行 Operations (内部实现)
+     *
+     * 调用者提供完整的 Operation[] 和 snapshotId
+     */
+    executeOperations(operations: Operation[], snapshotId: SnapshotID): Promise<OperationResult[]>;
+    /**
+     * [IBridge] 订阅 Desktop 状态变化
+     *
+     * 适配 IBridge 接口。
+     */
+    subscribe(listener: () => void): () => void;
+    /**
+     * 订阅 Desktop 更新信号
+     *
+     * @returns 取消订阅函数
+     */
+    onUpdate(listener: () => void): () => void;
+    /**
+     * 处理来自 Desktop 的信号 (带防抖)
+     */
+    handleSignal(signal: UpdateSignal): void;
+    private emitSignal;
+    /**
+     * [RFC-011] Push LLM text to Runtime's LLMOutputChannelService
+     * [RFC-020] Now accepts structured payload with reasoning and content
+     *
+     * Routes through Kernel to Desktop's llmOutputChannel.
+     */
+    pushLLMOutput(payload: {
+        reasoning?: string;
+        content?: string;
+    }, type: 'complete', meta?: {
+        model?: string;
+        usage?: {
+            promptTokens: number;
+            completionTokens: number;
+            totalTokens: number;
+        };
+    }): void;
+}

package/dist/adapters/bridge/index.js

@@ -0,0 +1,199 @@
+import { BRIDGE_DEFAULTS } from '../../spi/config/index.js';
+/**
+ * Bridge - Runtime 与外部的 I/O 边界
+ *
+ * 实现 IBridge 接口，作为 Agent（或 AgentDriver）与 Runtime 交互的标准实现。
+ *
+ * 职责:
+ * 1. 获取/释放 Snapshot
+ * 2. 执行 Operations
+ * 3. 订阅 UpdateSignal
+ *
+ * [Phase 6] 增强以支持 @aotui/agent-driver 集成
+ * [M2 FIX] 实现 IBridge 接口，支持 Mock 和替换
+ */
+export class Bridge {
+    kernel;
+    desktopId;
+    ownerId;
+    activeSnapshotId = null;
+    signalListeners = new Set();
+    debounceTimer = null;
+    pendingSignal = null;
+    debounceMs;
+    constructor(kernel, desktopId, ownerId, options) {
+        this.kernel = kernel;
+        this.desktopId = desktopId;
+        this.ownerId = ownerId;
+        this.debounceMs = options?.debounceMs ?? BRIDGE_DEFAULTS.debounceMs;
+    }
+    // ═══════════════════════════════════════════════════════════════
+    //  Snapshot Management (IBridge 兼容)
+    // ═══════════════════════════════════════════════════════════════
+    /**
+     * 获取 Desktop 快照
+     *
+     * @alias getSnapshot (保持向后兼容)
+     */
+    async acquireSnapshot() {
+        const newSnap = await this.kernel.acquireSnapshot(this.desktopId);
+        if (this.activeSnapshotId && this.activeSnapshotId !== newSnap.id) {
+            this.kernel.releaseSnapshot(this.activeSnapshotId);
+        }
+        this.activeSnapshotId = newSnap.id;
+        return newSnap;
+    }
+    /**
+     * [IBridge] 获取 Desktop 快照
+     *
+     * 适配 IBridge 接口，返回简化的 BridgeSnapshot。
+     */
+    async getSnapshot() {
+        const cached = await this.acquireSnapshot();
+        return {
+            id: cached.id,
+            markup: cached.markup,
+            timestamp: Date.now()
+        };
+    }
+    /**
+     * 释放快照
+     */
+    releaseSnapshot(snapshotId) {
+        if (this.activeSnapshotId === snapshotId) {
+            this.activeSnapshotId = null;
+        }
+        this.kernel.releaseSnapshot(snapshotId);
+    }
+    // ═══════════════════════════════════════════════════════════════
+    //  Operation Execution
+    // ═══════════════════════════════════════════════════════════════
+    /**
+     * 批量执行 Operations (IBridge 兼容)
+     *
+     * 调用者提供完整的 Operation[] 和 snapshotId
+     */
+    /**
+     * [IBridge] 执行一批操作
+     *
+     * 适配 IBridge 接口。
+     */
+    async execute(operations, snapshotId) {
+        return this.executeOperations(operations, snapshotId);
+    }
+    /**
+     * 批量执行 Operations (内部实现)
+     *
+     * 调用者提供完整的 Operation[] 和 snapshotId
+     */
+    async executeOperations(operations, snapshotId) {
+        const results = [];
+        // [Fix] Auto-acquire lock for the operations batch
+        // This ensures the Agent (or Bridge owner) has permission to execute.
+        this.kernel.acquireLock(this.desktopId, this.ownerId);
+        try {
+            for (const op of operations) {
+                // 确保 snapshotId 一致
+                const operation = {
+                    ...op,
+                    context: {
+                        ...op.context,
+                        snapshotId
+                    }
+                };
+                try {
+                    const result = await this.kernel.execute(this.desktopId, operation, this.ownerId);
+                    results.push(result);
+                }
+                catch (err) {
+                    results.push({
+                        success: false,
+                        error: {
+                            code: 'E_EXECUTION',
+                            message: err instanceof Error ? err.message : String(err)
+                        }
+                    });
+                }
+            }
+        }
+        finally {
+            // [Fix] Always release lock after batch execution
+            this.kernel.releaseLock(this.desktopId, this.ownerId);
+        }
+        return results;
+    }
+    // ═══════════════════════════════════════════════════════════════
+    //  Signal Handling
+    // ═══════════════════════════════════════════════════════════════
+    /**
+     * [IBridge] 订阅 Desktop 状态变化
+     *
+     * 适配 IBridge 接口。
+     */
+    subscribe(listener) {
+        return this.onUpdate(listener);
+    }
+    /**
+     * 订阅 Desktop 更新信号
+     *
+     * @returns 取消订阅函数
+     */
+    onUpdate(listener) {
+        this.signalListeners.add(listener);
+        return () => {
+            this.signalListeners.delete(listener);
+        };
+    }
+    /**
+     * 处理来自 Desktop 的信号 (带防抖)
+     */
+    handleSignal(signal) {
+        this.pendingSignal = signal;
+        if (this.debounceTimer) {
+            clearTimeout(this.debounceTimer);
+        }
+        this.debounceTimer = setTimeout(() => {
+            this.emitSignal();
+        }, this.debounceMs);
+    }
+    emitSignal() {
+        if (this.pendingSignal) {
+            this.signalListeners.forEach(l => l());
+            this.pendingSignal = null;
+        }
+    }
+    // ═══════════════════════════════════════════════════════════════
+    //  [RFC-011] LLM Output Channel
+    // ═══════════════════════════════════════════════════════════════
+    /**
+     * [RFC-011] Push LLM text to Runtime's LLMOutputChannelService
+     * [RFC-020] Now accepts structured payload with reasoning and content
+     *
+     * Routes through Kernel to Desktop's llmOutputChannel.
+     */
+    pushLLMOutput(payload, type, meta) {
+        console.log('[Bridge] pushLLMOutput called:', {
+            reasoningLength: payload.reasoning?.length ?? 0,
+            contentLength: payload.content?.length ?? 0,
+            type,
+            model: meta?.model
+        });
+        // Access Desktop via Kernel
+        const desktop = this.kernel.getDesktop(this.desktopId);
+        if (!desktop) {
+            console.warn('[Bridge] Desktop not found');
+            return;
+        }
+        // 1. Push to LLMOutputChannel (for local subscribers)
+        if (desktop.getLLMOutputChannel) {
+            const channel = desktop.getLLMOutputChannel();
+            channel.push(this.desktopId, payload, { ...meta, type });
+        }
+        // 2. Broadcast to all Workers via IPC
+        if (desktop.broadcastLLMOutput) {
+            desktop.broadcastLLMOutput(payload, type, meta);
+        }
+        console.log('[Bridge] LLM text pushed and broadcasted');
+    }
+}
+//# sourceMappingURL=index.js.map

package/dist/adapters/bridge/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/adapters/bridge/index.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,eAAe,EAAE,MAAM,2BAA2B,CAAC;AAE5D;;;;;;;;;;;;GAYG;AACH,MAAM,OAAO,MAAM;IAQH;IACA;IACA;IATJ,gBAAgB,GAAsB,IAAI,CAAC;IAC3C,eAAe,GAAG,IAAI,GAAG,EAAc,CAAC;IACxC,aAAa,GAA0B,IAAI,CAAC;IAC5C,aAAa,GAAwB,IAAI,CAAC;IAC1C,UAAU,CAAS;IAE3B,YACY,MAAe,EACf,SAAoB,EACpB,OAAe,EACvB,OAAiC;QAHzB,WAAM,GAAN,MAAM,CAAS;QACf,cAAS,GAAT,SAAS,CAAW;QACpB,YAAO,GAAP,OAAO,CAAQ;QAGvB,IAAI,CAAC,UAAU,GAAG,OAAO,EAAE,UAAU,IAAI,eAAe,CAAC,UAAU,CAAC;IACxE,CAAC;IAGD,kEAAkE;IAClE,oCAAoC;IACpC,kEAAkE;IAElE;;;;OAIG;IACH,KAAK,CAAC,eAAe;QACjB,MAAM,OAAO,GAAG,MAAM,IAAI,CAAC,MAAM,CAAC,eAAe,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;QAElE,IAAI,IAAI,CAAC,gBAAgB,IAAI,IAAI,CAAC,gBAAgB,KAAK,OAAO,CAAC,EAAE,EAAE,CAAC;YAChE,IAAI,CAAC,MAAM,CAAC,eAAe,CAAC,IAAI,CAAC,gBAAgB,CAAC,CAAC;QACvD,CAAC;QAED,IAAI,CAAC,gBAAgB,GAAG,OAAO,CAAC,EAAE,CAAC;QACnC,OAAO,OAAO,CAAC;IACnB,CAAC;IAED;;;;OAIG;IACH,KAAK,CAAC,WAAW;QACb,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,eAAe,EAAE,CAAC;QAC5C,OAAO;YACH,EAAE,EAAE,MAAM,CAAC,EAAE;YACb,MAAM,EAAE,MAAM,CAAC,MAAM;YACrB,SAAS,EAAE,IAAI,CAAC,GAAG,EAAE;SACxB,CAAC;IACN,CAAC;IAED;;OAEG;IACH,eAAe,CAAC,UAAkB;QAC9B,IAAI,IAAI,CAAC,gBAAgB,KAAK,UAAU,EAAE,CAAC;YACvC,IAAI,CAAC,gBAAgB,GAAG,IAAI,CAAC;QACjC,CAAC;QACD,IAAI,CAAC,MAAM,CAAC,eAAe,CAAC,UAAwB,CAAC,CAAC;IAC1D,CAAC;IAED,kEAAkE;IAClE,uBAAuB;IACvB,kEAAkE;IAElE;;;;OAIG;IACH;;;;OAIG;IACH,KAAK,CAAC,OAAO,CACT,UAAuB,EACvB,UAAkB;QAElB,OAAO,IAAI,CAAC,iBAAiB,CAAC,UAAU,EAAE,UAAwB,CAAC,CAAC;IACxE,CAAC;IAED;;;;OAIG;IACH,KAAK,CAAC,iBAAiB,CACnB,UAAuB,EACvB,UAAsB;QAEtB,MAAM,OAAO,GAAsB,EAAE,CAAC;QAEtC,mDAAmD;QACnD,sEAAsE;QACtE,IAAI,CAAC,MAAM,CAAC,WAAW,CAAC,IAAI,CAAC,SAAS,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;QAEtD,IAAI,CAAC;YACD,KAAK,MAAM,EAAE,IAAI,UAAU,EAAE,CAAC;gBAC1B,mBAAmB;gBACnB,MAAM,SAAS,GAAc;oBACzB,GAAG,EAAE;oBACL,OAAO,EAAE;wBACL,GAAG,EAAE,CAAC,OAAO;wBACb,UAAU;qBACb;iBACJ,CAAC;gBAEF,IAAI,CAAC;oBACD,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,MAAM,CAAC,OAAO,CAAC,IAAI,CAAC,SAAS,EAAE,SAAS,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;oBAClF,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;gBACzB,CAAC;gBAAC,OAAO,GAAG,EAAE,CAAC;oBACX,OAAO,CAAC,IAAI,CAAC;wBACT,OAAO,EAAE,KAAK;wBACd,KAAK,EAAE;4BACH,IAAI,EAAE,aAAa;4BACnB,OAAO,EAAE,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC;yBAC5D;qBACJ,CAAC,CAAC;gBACP,CAAC;YACL,CAAC;QACL,CAAC;gBAAS,CAAC;YACP,kDAAkD;YAClD,IAAI,CAAC,MAAM,CAAC,WAAW,CAAC,IAAI,CAAC,SAAS,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;QAC1D,CAAC;QAED,OAAO,OAAO,CAAC;IACnB,CAAC;IAID,kEAAkE;IAClE,mBAAmB;IACnB,kEAAkE;IAElE;;;;OAIG;IACH,SAAS,CAAC,QAAoB;QAC1B,OAAO,IAAI,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC;IACnC,CAAC;IAED;;;;OAIG;IACH,QAAQ,CAAC,QAAoB;QACzB,IAAI,CAAC,eAAe,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;QACnC,OAAO,GAAG,EAAE;YACR,IAAI,CAAC,eAAe,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;QAC1C,CAAC,CAAC;IACN,CAAC;IAED;;OAEG;IACH,YAAY,CAAC,MAAoB;QAC7B,IAAI,CAAC,aAAa,GAAG,MAAM,CAAC;QAE5B,IAAI,IAAI,CAAC,aAAa,EAAE,CAAC;YACrB,YAAY,CAAC,IAAI,CAAC,aAAa,CAAC,CAAC;QACrC,CAAC;QAED,IAAI,CAAC,aAAa,GAAG,UAAU,CAAC,GAAG,EAAE;YACjC,IAAI,CAAC,UAAU,EAAE,CAAC;QACtB,CAAC,EAAE,IAAI,CAAC,UAAU,CAAC,CAAC;IACxB,CAAC;IAEO,UAAU;QACd,IAAI,IAAI,CAAC,aAAa,EAAE,CAAC;YACrB,IAAI,CAAC,eAAe,CAAC,OAAO,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,EAAE,CAAC,CAAC;YACvC,IAAI,CAAC,aAAa,GAAG,IAAI,CAAC;QAC9B,CAAC;IACL,CAAC;IAED,kEAAkE;IAClE,gCAAgC;IAChC,kEAAkE;IAElE;;;;;OAKG;IACH,aAAa,CACT,OAAiD,EACjD,IAAgB,EAChB,IAOC;QAED,OAAO,CAAC,GAAG,CAAC,gCAAgC,EAAE;YAC1C,eAAe,EAAE,OAAO,CAAC,SAAS,EAAE,MAAM,IAAI,CAAC;YAC/C,aAAa,EAAE,OAAO,CAAC,OAAO,EAAE,MAAM,IAAI,CAAC;YAC3C,IAAI;YACJ,KAAK,EAAE,IAAI,EAAE,KAAK;SACrB,CAAC,CAAC;QAEH,4BAA4B;QAC5B,MAAM,OAAO,GAAG,IAAI,CAAC,MAAM,CAAC,UAAU,CAAC,IAAI,CAAC,SAAS,CAAC,CAAC;QACvD,IAAI,CAAC,OAAO,EAAE,CAAC;YACX,OAAO,CAAC,IAAI,CAAC,4BAA4B,CAAC,CAAC;YAC3C,OAAO;QACX,CAAC;QAED,sDAAsD;QACtD,IAAK,OAAe,CAAC,mBAAmB,EAAE,CAAC;YACvC,MAAM,OAAO,GAAI,OAAe,CAAC,mBAAmB,EAAE,CAAC;YACvD,OAAO,CAAC,IAAI,CAAC,IAAI,CAAC,SAAS,EAAE,OAAO,EAAE,EAAE,GAAG,IAAI,EAAE,IAAI,EAAE,CAAC,CAAC;QAC7D,CAAC;QAED,sCAAsC;QACtC,IAAK,OAAe,CAAC,kBAAkB,EAAE,CAAC;YACrC,OAAe,CAAC,kBAAkB,CAAC,OAAO,EAAE,IAAI,EAAE,IAAI,CAAC,CAAC;QAC7D,CAAC;QAED,OAAO,CAAC,GAAG,CAAC,0CAA0C,CAAC,CAAC;IAC5D,CAAC;CACJ"}

package/dist/adapters/index.d.ts

@@ -0,0 +1,7 @@
+/**
+ * @aotui/runtime - Adapters Module
+ *
+ * 导出 AOTUI Runtime 的 Adapters
+ */
+export { AOTUIDrivenSource, type AOTUIDrivenSourceOptions } from './aotui-driven-source.js';
+export { DEFAULT_AOTUI_SYSTEM_INSTRUCTION } from './system-instruction.js';

package/dist/adapters/index.js

@@ -0,0 +1,8 @@
+/**
+ * @aotui/runtime - Adapters Module
+ *
+ * 导出 AOTUI Runtime 的 Adapters
+ */
+export { AOTUIDrivenSource } from './aotui-driven-source.js';
+export { DEFAULT_AOTUI_SYSTEM_INSTRUCTION } from './system-instruction.js';
+//# sourceMappingURL=index.js.map

package/dist/adapters/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/adapters/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,iBAAiB,EAAiC,MAAM,0BAA0B,CAAC;AAC5F,OAAO,EAAE,gCAAgC,EAAE,MAAM,yBAAyB,CAAC"}

package/dist/adapters/session/index.d.ts

@@ -0,0 +1,7 @@
+/**
+ * AgentSession Module
+ *
+ * Agent 会话状态管理
+ */
+export type { IAgentSession, IAgentSessionManager } from './types.js';
+export { AgentSession, AgentSessionManager } from './session.js';

package/dist/adapters/session/index.js

@@ -0,0 +1,2 @@
+export { AgentSession, AgentSessionManager } from './session.js';
+//# sourceMappingURL=index.js.map

package/dist/adapters/session/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/adapters/session/index.ts"],"names":[],"mappings":"AAMA,OAAO,EAAE,YAAY,EAAE,mBAAmB,EAAE,MAAM,cAAc,CAAC"}

package/dist/adapters/session/session.d.ts

@@ -0,0 +1,46 @@
+/**
+ * AgentSession Implementation
+ *
+ * Agent 会话状态管理的默认实现
+ */
+import type { IAgentSession, IAgentSessionManager } from './types.js';
+/**
+ * AgentSession 默认实现
+ *
+ * 状态转换:
+ *
+ * ```
+ * [Idle, NoUpdate] --UpdateSignal--> tryStartProcessing() --> [Processing, NoUpdate]
+ *        ^                                                            |
+ *        |                                                            v
+ *        +------ finishProcessing() <------ [Processing, NoUpdate]----+
+ *                     |
+ *                     |  如果有更新
+ *                     v
+ *        +------ finishProcessing() returns true --> 重新触发处理
+ *
+ * [Processing] --UpdateSignal--> markUpdate() --> [Processing, HasUpdate]
+ * ```
+ */
+export declare class AgentSession implements IAgentSession {
+    readonly id: string;
+    private _isIdle;
+    private _hasUpdate;
+    constructor(id: string);
+    get isIdle(): boolean;
+    get hasUpdate(): boolean;
+    tryStartProcessing(): boolean;
+    finishProcessing(): boolean;
+    markUpdate(): void;
+}
+/**
+ * AgentSession 管理器
+ *
+ * 管理多个 AgentSession 实例 (按 sessionId 区分)
+ */
+export declare class AgentSessionManager implements IAgentSessionManager {
+    private sessions;
+    getSession(sessionId: string): IAgentSession;
+    destroySession(sessionId: string): void;
+    getAllSessions(): IAgentSession[];
+}

package/dist/adapters/session/session.js

@@ -0,0 +1,76 @@
+/**
+ * AgentSession 默认实现
+ *
+ * 状态转换:
+ *
+ * ```
+ * [Idle, NoUpdate] --UpdateSignal--> tryStartProcessing() --> [Processing, NoUpdate]
+ *        ^                                                            |
+ *        |                                                            v
+ *        +------ finishProcessing() <------ [Processing, NoUpdate]----+
+ *                     |
+ *                     |  如果有更新
+ *                     v
+ *        +------ finishProcessing() returns true --> 重新触发处理
+ *
+ * [Processing] --UpdateSignal--> markUpdate() --> [Processing, HasUpdate]
+ * ```
+ */
+export class AgentSession {
+    id;
+    _isIdle = true;
+    _hasUpdate = false;
+    constructor(id) {
+        this.id = id;
+    }
+    get isIdle() {
+        return this._isIdle;
+    }
+    get hasUpdate() {
+        return this._hasUpdate;
+    }
+    tryStartProcessing() {
+        if (!this._isIdle) {
+            // Agent 正在处理中,无法获取处理权
+            return false;
+        }
+        this._isIdle = false;
+        this._hasUpdate = false; // 开始处理时清除更新标记
+        return true;
+    }
+    finishProcessing() {
+        this._isIdle = true;
+        const hadUpdate = this._hasUpdate;
+        this._hasUpdate = false; // 消费更新标记
+        return hadUpdate;
+    }
+    markUpdate() {
+        this._hasUpdate = true;
+    }
+}
+/**
+ * AgentSession 管理器
+ *
+ * 管理多个 AgentSession 实例 (按 sessionId 区分)
+ */
+export class AgentSessionManager {
+    sessions = new Map();
+    getSession(sessionId) {
+        let session = this.sessions.get(sessionId);
+        if (!session) {
+            session = new AgentSession(sessionId);
+            this.sessions.set(sessionId, session);
+            console.log(`[AgentSessionManager] Created session: ${sessionId}`);
+        }
+        return session;
+    }
+    destroySession(sessionId) {
+        if (this.sessions.delete(sessionId)) {
+            console.log(`[AgentSessionManager] Destroyed session: ${sessionId}`);
+        }
+    }
+    getAllSessions() {
+        return Array.from(this.sessions.values());
+    }
+}
+//# sourceMappingURL=session.js.map

package/dist/adapters/session/session.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"session.js","sourceRoot":"","sources":["../../../src/adapters/session/session.ts"],"names":[],"mappings":"AAOA;;;;;;;;;;;;;;;;;GAiBG;AACH,MAAM,OAAO,YAAY;IAIO;IAHpB,OAAO,GAAY,IAAI,CAAC;IACxB,UAAU,GAAY,KAAK,CAAC;IAEpC,YAA4B,EAAU;QAAV,OAAE,GAAF,EAAE,CAAQ;IAAI,CAAC;IAE3C,IAAI,MAAM;QACN,OAAO,IAAI,CAAC,OAAO,CAAC;IACxB,CAAC;IAED,IAAI,SAAS;QACT,OAAO,IAAI,CAAC,UAAU,CAAC;IAC3B,CAAC;IAED,kBAAkB;QACd,IAAI,CAAC,IAAI,CAAC,OAAO,EAAE,CAAC;YAChB,sBAAsB;YACtB,OAAO,KAAK,CAAC;QACjB,CAAC;QACD,IAAI,CAAC,OAAO,GAAG,KAAK,CAAC;QACrB,IAAI,CAAC,UAAU,GAAG,KAAK,CAAC,CAAE,cAAc;QACxC,OAAO,IAAI,CAAC;IAChB,CAAC;IAED,gBAAgB;QACZ,IAAI,CAAC,OAAO,GAAG,IAAI,CAAC;QACpB,MAAM,SAAS,GAAG,IAAI,CAAC,UAAU,CAAC;QAClC,IAAI,CAAC,UAAU,GAAG,KAAK,CAAC,CAAE,SAAS;QACnC,OAAO,SAAS,CAAC;IACrB,CAAC;IAED,UAAU;QACN,IAAI,CAAC,UAAU,GAAG,IAAI,CAAC;IAC3B,CAAC;CACJ;AAED;;;;GAIG;AACH,MAAM,OAAO,mBAAmB;IACpB,QAAQ,GAA8B,IAAI,GAAG,EAAE,CAAC;IAExD,UAAU,CAAC,SAAiB;QACxB,IAAI,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAC3C,IAAI,CAAC,OAAO,EAAE,CAAC;YACX,OAAO,GAAG,IAAI,YAAY,CAAC,SAAS,CAAC,CAAC;YACtC,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;YACtC,OAAO,CAAC,GAAG,CAAC,0CAA0C,SAAS,EAAE,CAAC,CAAC;QACvE,CAAC;QACD,OAAO,OAAO,CAAC;IACnB,CAAC;IAED,cAAc,CAAC,SAAiB;QAC5B,IAAI,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,SAAS,CAAC,EAAE,CAAC;YAClC,OAAO,CAAC,GAAG,CAAC,4CAA4C,SAAS,EAAE,CAAC,CAAC;QACzE,CAAC;IACL,CAAC;IAED,cAAc;QACV,OAAO,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,MAAM,EAAE,CAAC,CAAC;IAC9C,CAAC;CACJ"}

package/dist/adapters/session/types.d.ts

@@ -0,0 +1,52 @@
+/**
+ * AgentSession Types
+ *
+ * Agent 会话状态管理接口
+ */
+/**
+ * Agent 会话状态接口
+ *
+ * 简化的状态模型:
+ * - isIdle: Agent 是否空闲
+ * - hasUpdate: TUI Desktop 是否有更新
+ */
+export interface IAgentSession {
+    /** 会话 ID (通常对应 Topic ID / Desktop ID) */
+    readonly id: string;
+    /** Agent 是否空闲 (未在处理中) */
+    readonly isIdle: boolean;
+    /** TUI Desktop 是否有待处理的更新 */
+    readonly hasUpdate: boolean;
+    /**
+     * 尝试开始处理
+     * @returns 是否成功获取处理权 (如果已在处理中则返回 false)
+     */
+    tryStartProcessing(): boolean;
+    /**
+     * 标记处理完成,并返回是否有待处理的更新
+     * @returns 如果有待处理更新返回 true,调用者应该重新拉取 snapshot
+     */
+    finishProcessing(): boolean;
+    /**
+     * 标记 TUI Desktop 有更新
+     * 当收到 UpdateSignal 但 Agent 正在处理时调用
+     */
+    markUpdate(): void;
+}
+/**
+ * AgentSession 管理器接口
+ */
+export interface IAgentSessionManager {
+    /**
+     * 获取或创建指定 ID 的会话
+     */
+    getSession(sessionId: string): IAgentSession;
+    /**
+     * 销毁指定会话
+     */
+    destroySession(sessionId: string): void;
+    /**
+     * 获取所有会话
+     */
+    getAllSessions(): IAgentSession[];
+}

package/dist/adapters/session/types.js

@@ -0,0 +1,7 @@
+/**
+ * AgentSession Types
+ *
+ * Agent 会话状态管理接口
+ */
+export {};
+//# sourceMappingURL=types.js.map

package/dist/adapters/session/types.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"types.js","sourceRoot":"","sources":["../../../src/adapters/session/types.ts"],"names":[],"mappings":"AAAA;;;;GAIG"}

package/dist/adapters/system-instruction.d.ts

@@ -0,0 +1,9 @@
+/**
+ * AOTUI 默认系统指令（Runtime 内置资源）
+ *
+ * 说明：
+ * - 作为 AOTUIDrivenSource 的默认 instruction 来源
+ * - 避免依赖仓库根目录文件结构
+ * - 可通过 AOTUIDrivenSourceOptions.instruction / instructionPath 或环境变量覆盖
+ */
+export declare const DEFAULT_AOTUI_SYSTEM_INSTRUCTION = "# AOTUI Desktop System Instruction\n\nYou are an AI Agent operating your own TUI Desktop.\n\nYou are the controller of a TUI (Text-based User Interface) Desktop environment designed specifically for AI Agents. Use the instructions below and the tools available to you to accomplish user requests.\n\nIMPORTANT: This is YOUR workspace, not the user's. The user communicates with you through applications, but YOU are the one controlling this Desktop. Never confuse your Desktop operations with user actions.\n\nIMPORTANT: You must NEVER guess or hallucinate the state of applications. Always read the current TUI state before taking any action. Each operation you execute is atomic - check the result before proceeding.\n\n# What is AOTUI?\n\nAOTUI (Agent-Oriented TUI) is a framework that provides AI Agents with a text-based operating environment, similar to how humans use graphical desktops.\n\n**Core Concepts:**\n\n- **Desktop**: Your personal workspace where applications are installed and views are mounted\n- **Application**: A tool that provides specific functionality\n- **View**: A displayable component within an application that shows content and exposes tools\n- **Tool**: An action you can execute via Function Calling to interact with views\n- **RefName**: A semantic reference to data objects (e.g., `pending[0]`, `recent_msgs[2]`) that you use as tool parameters\n\n**Key Characteristics:**\n\n- **De-visualized**: TUI uses semantic markdown instead of pixels and UI controls\n- **Value-Driven**: Tools accept data objects via RefName instead of primitive IDs\n- **Worker-Isolated**: Each Desktop runs applications in isolated environments for safety and reliability\n\n# Where You Are\n\nYou are currently operating **inside your own TUI Desktop**.\n\nThis Desktop is:\n\n- **Your workspace**: You control what apps are open, what views are mounted, and what operations to execute\n- **Stateful**: Applications maintain internal state (messages, todos, files) that you can query and modify\n- **Event-driven**: Applications emit updates (e.g., new message received), which the TUI system presents to you\n- **Text-based**: Everything is rendered as structured markdown with semantic tags like `<desktop>` and `<view>`\n\nThe user is NOT inside this Desktop. They interact with you through installed applications. When you see \"the user said X\", You need to respond by calling the appropriate tool.\n\nThink of it like this:\n\n- **User's world**: Natural language conversation, high-level requests\n- **Your world**: TUI Desktop where you operate apps, mount views, and execute tools\n\n# Understanding TUI Structure\n\nThe TUI state is provided in your context with the following structure:\n\n```\n<desktop>\n  ## System Instruction (this document)\n  ## Installed Applications (list of available apps with install status)\n  ## System Logs (recent desktop-level events)\n</desktop>\n\n<view id=\"workspace\" type=\"Workspace\" name=\"Workspace\" app_id=\"app_0\" app_name=\"App_X\">\n  ## Application Instruction (explains this view's purpose and tools)\n  ## Content (messages, data with RefName markers, etc.)\n  ## Available Tools (function calls you can make)\n</view>\n\n<view id=\"chat_0\" type=\"ChatDetail\" name=\"Chat with Wills\" app_id=\"app_0\" app_name=\"App_X\">\n  ## Application Instruction\n  ## Content\n  ## Available Tools\n</view>\n```\n\n## TUI View Message Structure\n\nEach `<view>` message is self-contained and includes app identity:\n\n- **`<view id=\"workspace\" type=\"Workspace\" name=\"Workspace\" app_id=\"app_0\" app_name=\"XApp\">`**\n  - `id`: View instance identifier within the app\n  - `type`: View type/category (e.g., `Workspace`, `ChatDetail`)\n  - `name`: Human-readable view name\n  - `app_id`: Source app identifier\n  - `app_name`: Source app name\n  - Contains: Application Instruction, Content, Available Tools\n\n## Data Markers and RefNames\n\nIn the `## Content` section, data objects are marked with special syntax:\n\n**Format**: `(content)[type:refName]`\n\n- **`content`**: The display text (e.g., \"Fix login bug\", \"Hello world!\")\n- **`type`**: Data type hint (e.g., `todo`, `message`, `file`)\n- **`refName`**: Semantic reference you use in tool parameters (e.g., `pending[0]`, `recent_msgs[2]`)\n\n**Examples:**\n\n```markdown\n## Content\n\n### Pending TODOs\n- (Fix login bug)[todo:pending[0]]\n- (Write unit tests)[todo:pending[1]]\n\n### Recent Messages\n- (Hello, how can I help?)[message:recent_msgs[0]]\n- (Please create a TODO)[message:recent_msgs[1]]\n```\n\n**How to Use RefNames:**\n\nWhen calling tools, use the `refName` as parameter values:\n\n```json\n{\n  \"name\": \"app_name-view_type-mark_complete\",\n  \"arguments\": {\n    \"todo\": \"pending[0]\"\n  }\n}\n```\n\nThe Runtime will automatically resolve `pending[0]` to the full TODO object and pass it to the tool handler.\n\nIMPORTANT: Always use RefNames from the current TUI state. Never guess or hardcode values.\n\n## Ref-First Parameter Passing (Global Rule)\n\nWhen a tool parameter expects an `object`, you should pass a RefName item (for example: `plans[0]`, `phases[1]`, `tasks[2]`, `terminals[0]`) rather than manually constructing primitive ids.\n\nRuntime behavior:\n\n- The Runtime automatically resolves RefName to the real object from IndexMap.\n- Tool handlers receive resolved objects (including fields like `id`, `title`, etc.).\n- You do NOT need to convert refs to ids manually in your call arguments.\n\nExamples:\n\n```json\n{\n  \"name\": \"app_name-view_type-open_plan\",\n  \"arguments\": {\n    \"plan\": \"plans[0]\"\n  }\n}\n```\n\n```json\n{\n  \"name\": \"app_2-view_type-send_command\",\n  \"arguments\": {\n    \"terminal\": \"terminals[0]\",\n    \"command\": \"whoami\"\n  }\n}\n```\n\nIMPORTANT:\n\n- Prefer semantic object refs over UI/view identifiers.\n- Do not pass `view_type` unless a tool explicitly requires it.\n- Never guess refs; always use refs shown in current TUI state.\n\n## Available Tools Section\n\nEach `<view>` contains an `## Available Tools` section listing all tools you can call for that view:\n\n**Format:**\n\n```markdown\n## Available Tools\n\n### add_todo\nCreate a new TODO item\n\n**Parameters:**\n- `title` (string, required): TODO title\n- `description` (string, optional): TODO description\n\n---\n\n### mark_complete\nMark a TODO as completed\n\n**Parameters:**\n- `todo` (object, required): TODO object from IndexMap (e.g., pending[0])\n```\n\n**How to Read:**\n\n- **Tool Name**: `add_todo`, `mark_complete`\n- **Description**: What the tool does\n- **Parameters**: Each parameter's name, type, whether required, and description\n  - If type is `object`, the description tells you it's from IndexMap (use a RefName)\n\n**How to Call:**\n\nTool name format: `{app_name}-{view_type}-{tool_name}`\n\nExample: `app_name-view_type-add_todo`\n\n# How to Operate the TUI Desktop\n\nFollow this systematic workflow for all tasks:\n\n## 1. READ - Examine Current State\n\n**Reading Guidelines:**\n\n- Start from `<desktop>` to understand what apps are installed\n- Check each `<view>` message and group by `app_id` / `app_name`\n- Read `## Application Instruction` to understand what each view does\n- Examine `## Content` to see current data with RefName markers\n- Review `## Available Tools` to know what actions you can take\n\nIMPORTANT: Always read the full TUI state before acting. Never assume from memory.\n\n## 2. DECIDE - Determine Action\n\nBased on the TUI state and user request, decide:\n\n- **What is the user asking for?** (e.g., \"add a TODO\", \"search messages\", \"list files\")\n- **Which app/view has the appropriate tool?** (check `## Available Tools`)\n- **What parameters are needed?** (use RefNames like `pending[0]`)\n- **Is the required view already present?** (match `app_id`, `app_name`, `type`, and `id`)\n\n**Decision-Making Principles:**\n\n- Never assume a tool exists without seeing it in `## Available Tools`\n- Never guess parameter values - use RefNames from the TUI Content\n- If you're unsure, read the `## Application Instruction` to understand the intended workflow\n\n## 3. ACT - Execute ONE Tool\n\nUse Function Calling to execute tools. Format: `{app_name}-{view_type}-{tool_name}` or `system-{tool_name}`.\n\n**System Tools:**\n\n| Tool | Parameters | When to Use |\n|------|------------|-------------|\n| `system-open_app` | `{ application: \"app_id\" }` | Need an app that's not currently open |\n| `system-close_app` | `{ application: \"app_id\" }` | Done with an app, want to free context space |\n\n**App Tools:**\n\nExample: `app_name-view_type-tool_name` with `{ \"content\": \"{$content}\" }`\n\nEach app defines its own tools. Always check `## Available Tools` in the view.\n\n**Tool Calling Policy:**\n\n- Execute ONE tool per Function Call\n- Do NOT batch multiple tools\n- Wait for the tool result before proceeding\n- Use RefNames (e.g., `plans[0]`, `tasks[1]`, `terminals[0]`) to pass data objects\n- For object parameters, prefer ref objects over primitive ids\n\n**Example:**\n\n```json\n{\n  \"name\": \"app_name-view_type-mark_complete\",\n  \"arguments\": {\n    \"todo\": \"pending[0]\"\n  }\n}\n```\n\nThis tells the Runtime: \"Get the object referenced by `pending[0]` and pass it to `mark_complete`\".\n\n## 4. CHECK - Review Tool Result\n\nAfter executing a tool, the TUI will show the result in `## Operation Log`:\n\n- **\u2705 Success**: Result contains `{ success: true, data: {...} }`\n- **\u274C Failed**: Result contains `{ success: false, error: { code, message } }`\n\n**Common Errors:**\n\n- `E_UNKNOWN_OPERATION`: The tool doesn't exist in the current view\n- `E_INVALID_ARGS`: Missing required parameters or wrong types\n- `INDEX_OUT_OF_RANGE`: Referenced item (e.g., `todos[5]`) doesn't exist\n- `E_NOT_FOUND`: Referenced app/view doesn't exist\n\n**Error Handling:**\n\n- Check the error code and message\n- Decide recovery strategy: retry with corrected parameters, inform user, or escalate\n- Never ignore errors and continue blindly\n\n## 5. LOOP or WAIT\n\nAfter completing a tool call:\n\n- **More work to do?** \u2192 Go back to step 1 (READ the updated state)\n\n**The Wait Rule:**\n\nAsk yourself: \"Is there more work I need to do NOW?\"\n\n- YES \u2192 Execute the next tool\n\nIMPORTANT: An idle agent should be waiting, not outputting text. Never invent tasks.\nIMPORTANT: After completing a task, either continue to the next step or wait. Do NOT output status updates.\n\n# Tone and Style\n\nYou operate a TUI Desktop. Your \"speech\" is minimal - **actions speak louder than words**.\n\n- Be concise and task-focused\n- First explain what you're about to do - Then do it\n- Never summarize what you just did - move to the next task or wait\n- Your output is logged and consumes tokens. Keep responses short unless the user explicitly asks for detail\n\n**Examples of Appropriate Behavior:**\n\n<example>\n**Scenario**: User assigned you complex tasks.\n\n**Your action**:\n\n1. Recusively Call `app_name-view_type-add_todo` with `{ \"title\": \"{$Task title}\" }`\n2. Check result\n3. If success, solve the tasks one bye one.\n\n**NOT this**: Output \"I will create a TODO for you\" then execute\n</example>\n\n<example>\n**Scenario**: User asks \"Mark the first TODO as done\"\n\n**TUI Content shows:**\n\n```\n### Pending TODOs\n- (Fix login bug)[todo:pending[0]]\n- (Write tests)[todo:pending[1]]\n```\n\n**Your action**: Call `app_name-view_type-mark_complete` with `{ \"todo\": \"pending[0]\" }`\n\n**NOT this**: Call with `{ \"todo\": \"Fix login bug\" }` or guess an ID\n</example>\n\n<example>\n**Scenario**: Tool call failed with E_INVALID_ARGS\n\n**Your action**:\n\n1. Read error message to understand what's wrong\n2. Check `## Available Tools` for correct parameter schema\n3. Retry with corrected arguments OR inform user if data is missing\n</example>\n\n# Proactiveness\n\nYou should be **reactive, not proactive**. Wait for signals before acting.\n\n**Guidelines:**\n\n1. When the user sends a message \u2192 Respond appropriately\n2. When a task is in progress \u2192 Continue until complete, then wait\n3. Never invent tasks. If the TUI shows no pending work, wait.\n4. Never perform actions \"just in case\" or \"to be helpful\"\n\n# Understanding Applications\n\nEach application has its own purpose and tools. Before using an app:\n\n1. **Read the Application Instruction**: Each view has an instruction section explaining:\n   - What the app is for\n   - When to use it\n   - Available tools and their parameters\n\n2. **Check current View messages**: See what views are currently present for each app (`app_id` / `app_name`)\n\n3. **Understand Tool Parameters**: Each tool lists required and optional parameters with types\n   - If type is `object`, use a RefName from the Content (e.g., `pending[0]`)\n   - If type is `string`, provide a literal string value\n\n**Key Conventions:**\n\n- Apps are installed on YOUR Desktop, managed by the system\n- You can open/close apps using system tools\n- Apps expose tools through their views\n- RefNames (e.g., `pending[0]`, `recent_msgs[2]`) provide atomic access to data objects\n\n# AOTUI Unique Features\n\nUnlike traditional CLI tools, AOTUI has these distinct characteristics:\n\n1. **Value-Driven Execution**: Tools accept data objects via RefName instead of primitive IDs\n   - Example: `mark_complete({ todo: \"pending[0]\" })` passes the entire TODO object\n   - Runtime resolves the RefName and provides the full data to the tool handler\n   - This ensures atomic operations and prevents stale data issues\n\n2. **Semantic References**: Data is accessed via semantic paths, not random IDs\n   - `recent_msgs[0]` \u2192 Most recent message\n   - `pending[2]` \u2192 Third pending TODO\n   - `completed[5]` \u2192 Sixth completed TODO\n\n3. **Data Type Markers**: Content uses `(display)[type:refName]` format\n   - Tells you the data type and how to reference it\n   - Example: `(Fix bug)[todo:pending[0]]` means use `pending[0]` to reference this TODO\n   - Example: `(Hello!)[message:recent_msgs[0]]` means use `recent_msgs[0]` for this message\n\n4. **Worker Isolation**: Each app runs in a separate thread\n   - Apps cannot interfere with each other\n   - Crashes are contained and recoverable\n\n5. **Snapshot-Based State**: TUI state is generated from app snapshots\n   - Always reflects the true current state\n   - No stale data or cache inconsistencies\n\n# Help & Guidance\n\nIf the user asks about system capabilities or how to use the Desktop:\n\n- Refer them to the **Installed Applications** section in `<desktop>` to see available apps\n- Each application's View contains an **Application Instruction** section explaining its purpose\n- For technical issues, the user should contact system administrators\n\n# Critical Reminders\n\nIMPORTANT: Always read the current TUI state before taking any action. Never assume state from memory.\nIMPORTANT: Each tool you execute is atomic. Check the result before proceeding to the next action.\nIMPORTANT: Use RefNames from the TUI Content as tool parameters. Never guess or hardcode values.\n";