@aotui/runtime 1.0.0

package/dist/adapters/system-instruction.js

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

package/dist/adapters/system-instruction.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"system-instruction.js","sourceRoot":"","sources":["../../src/adapters/system-instruction.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,MAAM,CAAC,MAAM,gCAAgC,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwa/C,CAAC"}

package/dist/benchmarks/dom-engine-comparison.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/benchmarks/dom-engine-comparison.js

@@ -0,0 +1,84 @@
+import { Window } from 'happy-dom';
+import { parseHTML } from 'linkedom';
+import { performance } from 'perf_hooks';
+// Helper to measure memory
+function getMemoryUsage() {
+    if (global.gc) {
+        global.gc();
+    }
+    const used = process.memoryUsage().heapUsed / 1024 / 1024;
+    return Math.round(used * 100) / 100;
+}
+const ITERATIONS = 100;
+console.log('--- DOM Engine Benchmark: LinkeDOM vs HappyDOM ---');
+// Warmup
+if (global.gc) {
+    global.gc();
+}
+const baselineMemory = getMemoryUsage();
+console.log(`Baseline Memory: ${baselineMemory} MB`);
+async function benchLinkeDOM() {
+    const memoryStart = getMemoryUsage();
+    const timeStart = performance.now();
+    for (let i = 0; i < ITERATIONS; i++) {
+        const { window, document } = parseHTML('<!DOCTYPE html><html><body></body></html>');
+        // Simple DOM Ops
+        for (let j = 0; j < 100; j++) {
+            const div = document.createElement('div');
+            div.setAttribute('id', `div-${j}`);
+            div.innerHTML = '<span>Hello</span>';
+            document.body.appendChild(div);
+        }
+    }
+    const timeEnd = performance.now();
+    const memoryEnd = getMemoryUsage();
+    return {
+        name: 'LinkeDOM',
+        time: (timeEnd - timeStart) / ITERATIONS,
+        memoryDelta: memoryEnd - memoryStart
+    };
+}
+async function benchHappyDOM() {
+    const memoryStart = getMemoryUsage();
+    const timeStart = performance.now();
+    for (let i = 0; i < ITERATIONS; i++) {
+        const window = new Window();
+        const document = window.document;
+        document.write('<!DOCTYPE html><html><body></body></html>');
+        // Simple DOM Ops
+        for (let j = 0; j < 100; j++) {
+            const div = document.createElement('div');
+            div.setAttribute('id', `div-${j}`);
+            div.innerHTML = '<span>Hello</span>';
+            document.body.appendChild(div);
+        }
+        window.close();
+    }
+    const timeEnd = performance.now();
+    const memoryEnd = getMemoryUsage();
+    return {
+        name: 'HappyDOM',
+        time: (timeEnd - timeStart) / ITERATIONS,
+        memoryDelta: memoryEnd - memoryStart
+    };
+}
+async function run() {
+    // Run LinkeDOM
+    if (global.gc) {
+        global.gc();
+    }
+    const r1 = await benchLinkeDOM();
+    console.log(`[LinkeDOM] Avg Time: ${r1.time.toFixed(2)}ms, Memory Delta: ${r1.memoryDelta} MB`);
+    // Run HappyDOM
+    if (global.gc) {
+        global.gc();
+    }
+    const r2 = await benchHappyDOM();
+    console.log(`[HappyDOM] Avg Time: ${r2.time.toFixed(2)}ms, Memory Delta: ${r2.memoryDelta} MB`);
+    // Comparison
+    console.log('\n--- Comparison ---');
+    console.log(`Speed Ratio (LinkeDOM/HappyDOM): ${(r2.time / r1.time).toFixed(2)}x (Lower is better for LinkeDOM)`);
+    // Note: If result > 1, HappyDOM is slower.
+}
+run();
+//# sourceMappingURL=dom-engine-comparison.js.map

package/dist/benchmarks/dom-engine-comparison.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"dom-engine-comparison.js","sourceRoot":"","sources":["../../src/benchmarks/dom-engine-comparison.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,WAAW,CAAC;AACnC,OAAO,EAAE,SAAS,EAAE,MAAM,UAAU,CAAC;AACrC,OAAO,EAAE,WAAW,EAAE,MAAM,YAAY,CAAC;AAEzC,2BAA2B;AAC3B,SAAS,cAAc;IACnB,IAAI,MAAM,CAAC,EAAE,EAAE,CAAC;QAAC,MAAM,CAAC,EAAE,EAAE,CAAC;IAAC,CAAC;IAC/B,MAAM,IAAI,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC,QAAQ,GAAG,IAAI,GAAG,IAAI,CAAC;IAC1D,OAAO,IAAI,CAAC,KAAK,CAAC,IAAI,GAAG,GAAG,CAAC,GAAG,GAAG,CAAC;AACxC,CAAC;AAED,MAAM,UAAU,GAAG,GAAG,CAAC;AAEvB,OAAO,CAAC,GAAG,CAAC,oDAAoD,CAAC,CAAC;AAElE,SAAS;AACT,IAAI,MAAM,CAAC,EAAE,EAAE,CAAC;IAAC,MAAM,CAAC,EAAE,EAAE,CAAC;AAAC,CAAC;AAC/B,MAAM,cAAc,GAAG,cAAc,EAAE,CAAC;AACxC,OAAO,CAAC,GAAG,CAAC,oBAAoB,cAAc,KAAK,CAAC,CAAC;AAErD,KAAK,UAAU,aAAa;IACxB,MAAM,WAAW,GAAG,cAAc,EAAE,CAAC;IACrC,MAAM,SAAS,GAAG,WAAW,CAAC,GAAG,EAAE,CAAC;IAEpC,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,UAAU,EAAE,CAAC,EAAE,EAAE,CAAC;QAClC,MAAM,EAAE,MAAM,EAAE,QAAQ,EAAE,GAAG,SAAS,CAAC,2CAA2C,CAAC,CAAC;QACpF,iBAAiB;QACjB,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,GAAG,EAAE,CAAC,EAAE,EAAE,CAAC;YAC3B,MAAM,GAAG,GAAG,QAAQ,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC;YAC1C,GAAG,CAAC,YAAY,CAAC,IAAI,EAAE,OAAO,CAAC,EAAE,CAAC,CAAC;YACnC,GAAG,CAAC,SAAS,GAAG,oBAAoB,CAAC;YACrC,QAAQ,CAAC,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;QACnC,CAAC;IACL,CAAC;IAED,MAAM,OAAO,GAAG,WAAW,CAAC,GAAG,EAAE,CAAC;IAClC,MAAM,SAAS,GAAG,cAAc,EAAE,CAAC;IAEnC,OAAO;QACH,IAAI,EAAE,UAAU;QAChB,IAAI,EAAE,CAAC,OAAO,GAAG,SAAS,CAAC,GAAG,UAAU;QACxC,WAAW,EAAE,SAAS,GAAG,WAAW;KACvC,CAAC;AACN,CAAC;AAED,KAAK,UAAU,aAAa;IACxB,MAAM,WAAW,GAAG,cAAc,EAAE,CAAC;IACrC,MAAM,SAAS,GAAG,WAAW,CAAC,GAAG,EAAE,CAAC;IAEpC,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,UAAU,EAAE,CAAC,EAAE,EAAE,CAAC;QAClC,MAAM,MAAM,GAAG,IAAI,MAAM,EAAE,CAAC;QAC5B,MAAM,QAAQ,GAAG,MAAM,CAAC,QAAQ,CAAC;QACjC,QAAQ,CAAC,KAAK,CAAC,2CAA2C,CAAC,CAAC;QAE5D,iBAAiB;QACjB,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,GAAG,EAAE,CAAC,EAAE,EAAE,CAAC;YAC3B,MAAM,GAAG,GAAG,QAAQ,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC;YAC1C,GAAG,CAAC,YAAY,CAAC,IAAI,EAAE,OAAO,CAAC,EAAE,CAAC,CAAC;YACnC,GAAG,CAAC,SAAS,GAAG,oBAAoB,CAAC;YACrC,QAAQ,CAAC,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC,CAAC;QACnC,CAAC;QAED,MAAM,CAAC,KAAK,EAAE,CAAC;IACnB,CAAC;IAED,MAAM,OAAO,GAAG,WAAW,CAAC,GAAG,EAAE,CAAC;IAClC,MAAM,SAAS,GAAG,cAAc,EAAE,CAAC;IAEnC,OAAO;QACH,IAAI,EAAE,UAAU;QAChB,IAAI,EAAE,CAAC,OAAO,GAAG,SAAS,CAAC,GAAG,UAAU;QACxC,WAAW,EAAE,SAAS,GAAG,WAAW;KACvC,CAAC;AACN,CAAC;AAED,KAAK,UAAU,GAAG;IACd,eAAe;IACf,IAAI,MAAM,CAAC,EAAE,EAAE,CAAC;QAAC,MAAM,CAAC,EAAE,EAAE,CAAC;IAAC,CAAC;IAC/B,MAAM,EAAE,GAAG,MAAM,aAAa,EAAE,CAAC;IACjC,OAAO,CAAC,GAAG,CAAC,wBAAwB,EAAE,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC,qBAAqB,EAAE,CAAC,WAAW,KAAK,CAAC,CAAC;IAEhG,eAAe;IACf,IAAI,MAAM,CAAC,EAAE,EAAE,CAAC;QAAC,MAAM,CAAC,EAAE,EAAE,CAAC;IAAC,CAAC;IAC/B,MAAM,EAAE,GAAG,MAAM,aAAa,EAAE,CAAC;IACjC,OAAO,CAAC,GAAG,CAAC,wBAAwB,EAAE,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,CAAC,qBAAqB,EAAE,CAAC,WAAW,KAAK,CAAC,CAAC;IAEhG,aAAa;IACb,OAAO,CAAC,GAAG,CAAC,sBAAsB,CAAC,CAAC;IACpC,OAAO,CAAC,GAAG,CAAC,oCAAoC,CAAC,EAAE,CAAC,IAAI,GAAG,EAAE,CAAC,IAAI,CAAC,CAAC,OAAO,CAAC,CAAC,CAAC,kCAAkC,CAAC,CAAC;IAClH,2CAA2C;AAC/C,CAAC;AAED,GAAG,EAAE,CAAC"}

package/dist/benchmarks/shadow-dom-check.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/benchmarks/shadow-dom-check.js

@@ -0,0 +1,44 @@
+import { Window } from 'happy-dom';
+console.log('--- HappyDOM Shadow DOM Capability Check ---');
+async function checkShadowDOM() {
+    const window = new Window();
+    const document = window.document;
+    const body = document.body;
+    // 1. Basic Creation
+    const host = document.createElement('div');
+    host.id = 'app-root';
+    body.appendChild(host);
+    console.log('[Check 1] attachShadow API exists:', typeof host.attachShadow === 'function');
+    if (typeof host.attachShadow !== 'function') {
+        console.error('❌ HappyDOM does not support attachShadow!');
+        return;
+    }
+    // 2. Closed Mode Isolation
+    const shadowRoot = host.attachShadow({ mode: 'closed' });
+    console.log('[Check 2] shadowRoot is closed (host.shadowRoot should be null):', host.shadowRoot === null);
+    // 3. Render Content inside Shadow
+    const innerDiv = document.createElement('div');
+    innerDiv.id = 'inner-secret';
+    innerDiv.className = 'secret-class';
+    shadowRoot.appendChild(innerDiv);
+    // 4. Query Isolation Test
+    const queriedId = document.getElementById('inner-secret');
+    const queriedClass = document.querySelector('.secret-class');
+    console.log('[Check 3] Query Isolation (ID):', queriedId === null ? 'Pass' : 'Fail');
+    console.log('[Check 4] Query Isolation (Class):', queriedClass === null ? 'Pass' : 'Fail');
+    // 5. Event Retargeting Test (Mock Event)
+    let eventTargetCorrect = false;
+    host.addEventListener('click', (e) => {
+        // When clicking inside shadow, target should be retargeted to host
+        // HappyDOM might simulate this if we dispatch event on innerDiv
+        console.log('[Check 5 Debug] Click target:', e.target.id || e.target.tagName);
+        eventTargetCorrect = (e.target === host);
+    });
+    // Create and dispatch event inside shadow
+    const event = new window.MouseEvent('click', { bubbles: true, composed: true });
+    innerDiv.dispatchEvent(event);
+    console.log('[Check 5] Event Retargeting:', eventTargetCorrect ? 'Pass' : 'Fail');
+    window.close();
+}
+checkShadowDOM();
+//# sourceMappingURL=shadow-dom-check.js.map

package/dist/benchmarks/shadow-dom-check.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"shadow-dom-check.js","sourceRoot":"","sources":["../../src/benchmarks/shadow-dom-check.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAE,MAAM,WAAW,CAAC;AAGnC,OAAO,CAAC,GAAG,CAAC,8CAA8C,CAAC,CAAC;AAE5D,KAAK,UAAU,cAAc;IACzB,MAAM,MAAM,GAAG,IAAI,MAAM,EAAE,CAAC;IAC5B,MAAM,QAAQ,GAAG,MAAM,CAAC,QAAQ,CAAC;IACjC,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,CAAC;IAE3B,oBAAoB;IACpB,MAAM,IAAI,GAAG,QAAQ,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC;IAC3C,IAAI,CAAC,EAAE,GAAG,UAAU,CAAC;IACrB,IAAI,CAAC,WAAW,CAAC,IAAI,CAAC,CAAC;IAEvB,OAAO,CAAC,GAAG,CAAC,oCAAoC,EAAE,OAAO,IAAI,CAAC,YAAY,KAAK,UAAU,CAAC,CAAC;IAE3F,IAAI,OAAO,IAAI,CAAC,YAAY,KAAK,UAAU,EAAE,CAAC;QAC1C,OAAO,CAAC,KAAK,CAAC,2CAA2C,CAAC,CAAC;QAC3D,OAAO;IACX,CAAC;IAED,2BAA2B;IAC3B,MAAM,UAAU,GAAG,IAAI,CAAC,YAAY,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,CAAC,CAAC;IACzD,OAAO,CAAC,GAAG,CAAC,kEAAkE,EAAE,IAAI,CAAC,UAAU,KAAK,IAAI,CAAC,CAAC;IAE1G,kCAAkC;IAClC,MAAM,QAAQ,GAAG,QAAQ,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC;IAC/C,QAAQ,CAAC,EAAE,GAAG,cAAc,CAAC;IAC7B,QAAQ,CAAC,SAAS,GAAG,cAAc,CAAC;IACpC,UAAU,CAAC,WAAW,CAAC,QAAQ,CAAC,CAAC;IAEjC,0BAA0B;IAC1B,MAAM,SAAS,GAAG,QAAQ,CAAC,cAAc,CAAC,cAAc,CAAC,CAAC;IAC1D,MAAM,YAAY,GAAG,QAAQ,CAAC,aAAa,CAAC,eAAe,CAAC,CAAC;IAE7D,OAAO,CAAC,GAAG,CAAC,iCAAiC,EAAE,SAAS,KAAK,IAAI,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC;IACrF,OAAO,CAAC,GAAG,CAAC,oCAAoC,EAAE,YAAY,KAAK,IAAI,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC;IAE3F,yCAAyC;IACzC,IAAI,kBAAkB,GAAG,KAAK,CAAC;IAC/B,IAAI,CAAC,gBAAgB,CAAC,OAAO,EAAE,CAAC,CAAC,EAAE,EAAE;QACjC,mEAAmE;QACnE,gEAAgE;QAChE,OAAO,CAAC,GAAG,CAAC,+BAA+B,EAAG,CAAC,CAAC,MAAc,CAAC,EAAE,IAAK,CAAC,CAAC,MAAc,CAAC,OAAO,CAAC,CAAC;QAChG,kBAAkB,GAAG,CAAC,CAAC,CAAC,MAAM,KAAK,IAAI,CAAC,CAAC;IAC7C,CAAC,CAAC,CAAC;IAEH,0CAA0C;IAC1C,MAAM,KAAK,GAAG,IAAI,MAAM,CAAC,UAAU,CAAC,OAAO,EAAE,EAAE,OAAO,EAAE,IAAI,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;IAChF,QAAQ,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC;IAE9B,OAAO,CAAC,GAAG,CAAC,8BAA8B,EAAE,kBAAkB,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC;IAElF,MAAM,CAAC,KAAK,EAAE,CAAC;AACnB,CAAC;AAED,cAAc,EAAE,CAAC"}

package/dist/cli.d.ts

@@ -0,0 +1,17 @@
+#!/usr/bin/env node
+/**
+ * agentina CLI - Third-Party App Management
+ *
+ * 命令:
+ *   agentina add <source>     安装 App
+ *   agentina remove <name>    卸载 App
+ *   agentina list             列出已安装
+ *   agentina enable <name>    启用 App
+ *   agentina disable <name>   禁用 App
+ *   agentina autostart <name> <on|off>  设置自动启动
+ *   agentina link <path>      链接本地开发目录
+ *   agentina run [name]       Run installed apps (or specific app)
+ *
+ * @module @aotui/cli
+ */
+export {};