feat: rename

Author: qddegtya

examples/simple-browser-use/.gitignore

@@ -0,0 +1 @@
+*.png

examples/simple-browser-use/README.md

@@ -0,0 +1,104 @@
+# Browser Use Example
+
+This example demonstrates how to use AStack to build a browser automation pipeline that can understand natural language intents, execute web browsing tasks, and return formatted results.
+
+## Overview
+
+The Browser Use example showcases:
+
+1. Natural language task planning using an LLM-powered agent
+2. Browser automation with Playwright
+3. State management for tracking browser context
+4. Result processing and DOM snapshot filtering
+5. Automatic resource cleanup
+6. Pipeline-based execution flow
+
+## Pipeline Architecture
+
+The pipeline consists of several components working together:
+
+```mermaid
+graph TD
+ %% Components
+ Planner[PlanningAgent]
+ Browser[BrowserAgent]
+ BrowserState[BrowserStateComponent]
+ Formatter[ResultFormatter]
+ 
+ %% Define ports as nodes to show this-connection
+ Browser_Result["browser.result"]
+ Browser_Stop["browser.stop"]
+ 
+ %% Connections
+ Planner -->|plan| Browser
+ Browser -->|stateUpdate| BrowserState
+ BrowserState -->|broadcast| Browser
+ Browser --> Browser_Result
+ Browser_Result -->|data| Formatter
+ Browser_Result -->|"Self-Connection"| Browser_Stop
+ Browser_Stop --> Browser
+ 
+ %% Style
+ classDef component fill:#f9f9f9,stroke:#333,stroke-width:1px;
+ classDef port fill:#e1f5fe,stroke:#0288d1,stroke-width:1px;
+ classDef selfconnect fill:#ffecb3,stroke:#ffa000,stroke-width:1px;
+ class Planner,Browser,BrowserState,Formatter component;
+ class Browser_Result,Browser_Stop port;
+ 
+ %% Notes
+ subgraph Pipeline Flow
+ direction TB
+ note1[User Intent] -->|Input| Planner
+ Formatter -->|Output| note2[Formatted Result]
+ end
+ 
+ %% Style for this-connection
+ linkStyle 4 stroke:#F44336,stroke-width:2px,stroke-dasharray: 5 5;
+```
+
+### Component Responsibilities
+
+- **PlanningAgent**: Converts natural language intent into a step-by-step plan for browser automation
+- **BrowserAgent**: Executes browser automation actions using Playwright
+- **BrowserStateComponent**: Manages and broadcasts browser state (DOM, URL, etc.) to other components
+- **ResultFormatter**: Filters DOM snapshot data and passes through relevant results
+
+### Data Flow
+
+1. User intent is sent to the `PlanningAgent`
+2. `PlanningAgent` creates a plan and sends it to `BrowserAgent`
+3. `BrowserAgent` executes browser actions and sends state updates to `BrowserStateComponent`
+4. `BrowserStateComponent` broadcasts state to interested components
+5. `BrowserAgent` sends result data to `ResultFormatter` and signals itself to close
+6. `ResultFormatter` filters out DOM snapshot data and passes through relevant results
+7. Pipeline returns the formatted result
+
+## Usage
+
+```bash
+# Install dependencies
+pnpm install
+
+# Run the example with a custom query
+DEEPSEEK_API_KEY=your_api_key pnpm start "your query here"
+
+# Or use the default query
+DEEPSEEK_API_KEY=your_api_key pnpm start
+```
+
+## Key Design Patterns
+
+- **"Everything is a Component" Principle**: All functionality is encapsulated in composable components
+- **Zero-Adapter Design**: Components communicate directly through ports without adapters
+- **Automatic Resource Management**: Browser resources are automatically cleaned up after task completion
+- **Declarative Pipeline Configuration**: Components and connections are defined declaratively
+
+## Extending the Example
+
+You can extend this example by:
+
+1. Adding new browser tools (e.g., form filling, file downloads)
+2. Implementing error recovery strategies
+3. Adding authentication support
+4. Creating specialized components for specific websites
+5. Adding visualization for real-time monitoring