beddel 1.0.6 → 1.0.8

package/README.md

@@ -1,7 +1,7 @@
 # Beddel Protocol
 
 [![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
-[![npm version](https://img.shields.io/badge/npm-1.0.4-brightgreen.svg)](https://www.npmjs.com/package/beddel)
+[![npm version](https://img.shields.io/badge/npm-1.0.8-brightgreen.svg)](https://www.npmjs.com/package/beddel)
 [![TypeScript](https://img.shields.io/badge/TypeScript-5.x-blue.svg)](https://www.typescriptlang.org/)
 [![AI SDK](https://img.shields.io/badge/AI%20SDK-v6-purple.svg)](https://sdk.vercel.ai/)
 
@@ -16,6 +16,7 @@
 - 📦 **Bundle Separation** — Three entry points for server, client, and full API access
 - 🌐 **Multi-Provider** — Built-in support for Google Gemini, Amazon Bedrock, and OpenRouter (400+ models)
 - 🔀 **Semantic Primitives** — `chat` for streaming frontend, `llm` for blocking workflows
+- 📊 **Native Observability** — Built-in workflow tracing with step lifecycle events
 
 ## Installation
 
@@ -142,6 +143,82 @@ export default function Chat() {
 }
 ```
 
+## Observability
+
+Beddel includes native observability support for workflow execution tracing. Enable it in your agent's metadata:
+
+```yaml
+metadata:
+  name: "My Agent"
+  version: "1.0.0"
+  observability:
+    enabled: true
+
+workflow:
+  # ... steps
+```
+
+When enabled, the response includes a `__trace` array with step lifecycle events:
+
+```json
+{
+  "success": true,
+  "data": { ... },
+  "__trace": [
+    { "type": "step-start", "stepId": "fetch-docs", "stepType": "mcp-tool", "stepIndex": 0, "totalSteps": 3, "timestamp": 1705849200000 },
+    { "type": "step-complete", "stepId": "fetch-docs", "stepType": "mcp-tool", "stepIndex": 0, "totalSteps": 3, "timestamp": 1705849201500, "duration": 1500 },
+    { "type": "step-start", "stepId": "analyze", "stepType": "llm", "stepIndex": 1, "totalSteps": 3, "timestamp": 1705849201501 },
+    ...
+  ]
+}
+```
+
+### Event Types
+
+| Event | Description | Extra Fields |
+|-------|-------------|--------------|
+| `step-start` | Step execution begins | — |
+| `step-complete` | Step completed successfully | `duration` (ms) |
+| `step-error` | Step threw an error | `duration` (ms), `errorType` |
+
+### Error Types (Sanitized)
+
+For security, error messages are never exposed. Instead, errors are categorized:
+
+| Error Type | Description |
+|------------|-------------|
+| `timeout` | Operation timed out |
+| `auth_failed` | Authentication/authorization error |
+| `validation` | Input validation failed |
+| `network` | Network connectivity issue |
+| `unknown` | Uncategorized error |
+
+### Streaming with Observability
+
+For `chat` primitives (streaming), trace events are sent as transient data before the stream.
+
+> **Note:** Transient data parts are only accessible via the `onData` callback. They do not appear in the `messages` array.
+
+```typescript
+// Client-side handling with useChat (AI SDK v6)
+import { useChat } from '@ai-sdk/react';
+import { DefaultChatTransport } from 'ai';
+
+const [streamTrace, setStreamTrace] = useState<StepEvent[]>([]);
+
+const { messages, sendMessage, status } = useChat({
+  transport: new DefaultChatTransport({
+    api: '/api/beddel/chat',
+    body: { agentId: 'observability-demo-stream' },
+  }),
+  onData: (dataPart) => {
+    if (dataPart.type === 'data-trace') {
+      setStreamTrace(dataPart.data.events);
+    }
+  },
+});
+```
+
 ## Built-in Providers
 
 | Provider | Environment Variables | Default Model |
@@ -236,6 +313,7 @@ workflow:
 |---------|-------------|---------|
 | `$input.*` | Access request input | `$input.messages` |
 | `$stepResult.varName.*` | Access step result | `$stepResult.llmOutput.text` |
+| `$env.*` | Access environment variables | `$env.NOTION_DATABASE_ID` |
 
 ## Built-in Tools
 

package/dist/agents/{business-analyzer.yaml → google-business/business-analyzer.yaml}

@@ -13,8 +13,9 @@
 
 metadata:
   name: "Business Analyzer"
-  version: "1.0.0"
+  version: "1.1.0"
   description: "Analyzes business reviews and generates actionable insights"
+  builtin: true
 
 workflow:
   # Step 1: Fetch all reviews with auto-pagination
@@ -46,20 +47,28 @@ workflow:
         5. Trend analysis comparing recent vs older reviews
         6. Actionable recommendations
         
-        Format your response as structured JSON.
+        Return ONLY valid JSON (no markdown, no ```):
+        {
+          "sentimentScore": 8,
+          "positiveThemes": [{"theme": "Great service", "count": 15}],
+          "improvementAreas": [{"area": "Wait times", "count": 5}],
+          "urgentReviews": [{"reviewId": "xxx", "rating": 1, "issue": "summary"}],
+          "trendAnalysis": "Recent reviews show improvement...",
+          "recommendations": ["Focus on...", "Consider..."]
+        }
       messages:
         - role: "user"
-          content: |
-            Analyze these business reviews:
-            
-            Total Reviews: $stepResult.reviewsData.totalReviewCount
-            Average Rating: $stepResult.reviewsData.averageRating
-            
-            Reviews Data:
-            $stepResult.reviewsData.reviews
+          content: "$input.reviewsPayload"
+    result: "analysisRaw"
+
+  # Step 3: Parse analysis JSON
+  - id: "parse-analysis"
+    type: "output-generator"
+    config:
+      json: "$stepResult.analysisRaw.text"
     result: "analysis"
 
-  # Step 3: Generate response suggestions for negative reviews
+  # Step 4: Generate response suggestions for negative reviews
   - id: "generate-responses"
     type: "llm"
     config:
@@ -76,24 +85,29 @@ workflow:
         - Keep responses under 150 words
         - Be specific to the complaint mentioned
         
-        Format as JSON array with reviewId and suggestedResponse.
+        Return ONLY valid JSON array (no markdown, no ```):
+        [{"reviewId": "xxx", "rating": 2, "originalComment": "...", "suggestedResponse": "..."}]
+        
+        If no negative reviews, return: []
       messages:
         - role: "user"
-          content: |
-            Generate response suggestions for these reviews:
-            $stepResult.reviewsData.reviews
-    result: "responseSuggestions"
+          content: "$input.reviewsPayload"
+    result: "responsesRaw"
 
-  # Step 4: Compile final report
-  - id: "compile-report"
+  # Step 5: Parse responses JSON
+  - id: "parse-responses"
     type: "output-generator"
     config:
-      template:
-        summary:
-          totalReviews: "$stepResult.reviewsData.totalReviewCount"
-          averageRating: "$stepResult.reviewsData.averageRating"
-          analysisDate: "$input.analysisDate"
-        analysis: "$stepResult.analysis.text"
-        responseSuggestions: "$stepResult.responseSuggestions.text"
-        rawReviews: "$stepResult.reviewsData.reviews"
-    result: "finalReport"
+      json: "$stepResult.responsesRaw.text"
+    result: "responseSuggestions"
+
+# Explicit Return: Define the API response contract
+return:
+  success: true
+  summary:
+    totalReviews: "$stepResult.reviewsData.totalReviewCount"
+    averageRating: "$stepResult.reviewsData.averageRating"
+    pagesFetched: "$stepResult.reviewsData.data.pagesFetched"
+  analysis: "$stepResult.analysis"
+  responseSuggestions: "$stepResult.responseSuggestions"
+  reviews: "$stepResult.reviewsData.reviews"

package/dist/agents/index.d.ts

@@ -3,12 +3,24 @@
  *
  * Lists all agents bundled with the beddel package.
  * These are available automatically without user configuration.
+ *
+ * Agents are organized by category:
+ * - chat/         Streaming chat assistants (different providers)
+ * - mcp/          MCP server integrations (GitMCP, Context7, etc.)
+ * - google-business/  Google Business Profile agents
+ * - marketing/    Lead capture, newsletters, CRM
+ * - utility/      General-purpose tools
+ * - examples/     Demo pipelines showing multi-step workflows
+ */
+/**
+ * Built-in agent definitions with their category paths
  */
+export declare const BUILTIN_AGENT_PATHS: Record<string, string>;
 /**
  * List of built-in agent IDs available in the package
  */
-export declare const BUILTIN_AGENTS: readonly ["assistant", "assistant-bedrock", "assistant-openrouter", "assistant-gitmcp", "text-generator", "multi-step-assistant", "business-analyzer"];
-export type BuiltinAgentId = typeof BUILTIN_AGENTS[number];
+export declare const BUILTIN_AGENTS: readonly string[];
+export type BuiltinAgentId = keyof typeof BUILTIN_AGENT_PATHS;
 /**
  * Get the absolute path to the built-in agents directory
  */
@@ -20,5 +32,14 @@ export declare function isBuiltinAgent(agentId: string): agentId is BuiltinAgent
 /**
  * Get the full path to a built-in agent YAML file
  */
-export declare function getBuiltinAgentPath(agentId: BuiltinAgentId): string;
+export declare function getBuiltinAgentPath(agentId: string): string | null;
+/**
+ * Get all agents in a specific category
+ */
+export declare function getAgentsByCategory(category: string): string[];
+/**
+ * Available categories
+ */
+export declare const AGENT_CATEGORIES: readonly ["chat", "mcp", "google-business", "marketing", "utility", "observability", "examples"];
+export type AgentCategory = typeof AGENT_CATEGORIES[number];
 //# sourceMappingURL=index.d.ts.map

package/dist/agents/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/agents/index.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AASH;;GAEG;AACH,eAAO,MAAM,cAAc,wJAQjB,CAAC;AAEX,MAAM,MAAM,cAAc,GAAG,OAAO,cAAc,CAAC,MAAM,CAAC,CAAC;AAE3D;;GAEG;AACH,wBAAgB,oBAAoB,IAAI,MAAM,CAE7C;AAED;;GAEG;AACH,wBAAgB,cAAc,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,IAAI,cAAc,CAEzE;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,cAAc,GAAG,MAAM,CAEnE"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/agents/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AASH;;GAEG;AACH,eAAO,MAAM,mBAAmB,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAwBtD,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,cAAc,EAAuC,SAAS,MAAM,EAAE,CAAC;AAEpF,MAAM,MAAM,cAAc,GAAG,MAAM,OAAO,mBAAmB,CAAC;AAE9D;;GAEG;AACH,wBAAgB,oBAAoB,IAAI,MAAM,CAE7C;AAED;;GAEG;AACH,wBAAgB,cAAc,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,IAAI,cAAc,CAEzE;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,GAAG,IAAI,CAIlE;AAED;;GAEG;AACH,wBAAgB,mBAAmB,CAAC,QAAQ,EAAE,MAAM,GAAG,MAAM,EAAE,CAI9D;AAED;;GAEG;AACH,eAAO,MAAM,gBAAgB,kGAQnB,CAAC;AAEX,MAAM,MAAM,aAAa,GAAG,OAAO,gBAAgB,CAAC,MAAM,CAAC,CAAC"}

package/dist/agents/index.js

@@ -3,24 +3,46 @@
  *
  * Lists all agents bundled with the beddel package.
  * These are available automatically without user configuration.
+ *
+ * Agents are organized by category:
+ * - chat/         Streaming chat assistants (different providers)
+ * - mcp/          MCP server integrations (GitMCP, Context7, etc.)
+ * - google-business/  Google Business Profile agents
+ * - marketing/    Lead capture, newsletters, CRM
+ * - utility/      General-purpose tools
+ * - examples/     Demo pipelines showing multi-step workflows
  */
 import { fileURLToPath } from 'url';
 import { dirname, join } from 'path';
 // Get the directory where built-in agents are located
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
+/**
+ * Built-in agent definitions with their category paths
+ */
+export const BUILTIN_AGENT_PATHS = {
+    // Chat assistants
+    'assistant': 'chat/assistant.yaml',
+    'assistant-bedrock': 'chat/assistant-bedrock.yaml',
+    'assistant-openrouter': 'chat/assistant-openrouter.yaml',
+    // MCP integrations
+    'assistant-gitmcp': 'mcp/assistant-gitmcp.yaml',
+    // Google Business
+    'business-analyzer': 'google-business/business-analyzer.yaml',
+    // Marketing
+    'newsletter-signup': 'marketing/newsletter-signup.yaml',
+    // Utility
+    'text-generator': 'utility/text-generator.yaml',
+    // Observability
+    'observability-demo': 'observability/observability-demo.yaml',
+    'observability-demo-stream': 'observability/observability-demo-stream.yaml',
+    // Examples
+    'multi-step-assistant': 'examples/multi-step-assistant.yaml',
+};
 /**
  * List of built-in agent IDs available in the package
  */
-export const BUILTIN_AGENTS = [
-    'assistant',
-    'assistant-bedrock',
-    'assistant-openrouter',
-    'assistant-gitmcp',
-    'text-generator',
-    'multi-step-assistant',
-    'business-analyzer',
-];
+export const BUILTIN_AGENTS = Object.keys(BUILTIN_AGENT_PATHS);
 /**
  * Get the absolute path to the built-in agents directory
  */
@@ -31,11 +53,34 @@ export function getBuiltinAgentsPath() {
  * Check if an agent ID is a built-in agent
  */
 export function isBuiltinAgent(agentId) {
-    return BUILTIN_AGENTS.includes(agentId);
+    return agentId in BUILTIN_AGENT_PATHS;
 }
 /**
  * Get the full path to a built-in agent YAML file
  */
 export function getBuiltinAgentPath(agentId) {
-    return join(__dirname, `${agentId}.yaml`);
+    const relativePath = BUILTIN_AGENT_PATHS[agentId];
+    if (!relativePath)
+        return null;
+    return join(__dirname, relativePath);
+}
+/**
+ * Get all agents in a specific category
+ */
+export function getAgentsByCategory(category) {
+    return Object.entries(BUILTIN_AGENT_PATHS)
+        .filter(([_, path]) => path.startsWith(`${category}/`))
+        .map(([id]) => id);
 }
+/**
+ * Available categories
+ */
+export const AGENT_CATEGORIES = [
+    'chat',
+    'mcp',
+    'google-business',
+    'marketing',
+    'utility',
+    'observability',
+    'examples',
+];

package/dist/agents/marketing/newsletter-signup.yaml

@@ -0,0 +1,106 @@
+# Newsletter Signup Agent
+# Registers users to the newsletter with AI analysis and saves to Notion
+#
+# Required Environment Variables:
+# - NOTION_TOKEN (Internal Integration Secret)
+# - NOTION_DATABASE_ID (Database ID for newsletter signups)
+# - GEMINI_API_KEY (for AI analysis)
+#
+# Input:
+# - name: User's name
+# - email: User's email
+# - message: Optional message from user
+# - createdAt: ISO date string
+
+metadata:
+  name: "Newsletter Signup Agent"
+  version: "1.3.0"
+  description: "Registers users to the newsletter with AI analysis and saves to Notion"
+  builtin: true
+
+workflow:
+  # Step 1: Analyze user profile and generate structured JSON
+  - id: "analyze-user"
+    type: "llm"
+    config:
+      provider: "google"
+      model: "gemini-2.0-flash-exp"
+      system: |
+        You are a lead analyst for a technology newsletter.
+        
+        Analyze the user data and return ONLY a valid JSON (no markdown, no ```):
+        {
+          "tags": [{"name": "Tag1"}],
+          "sentiment": {"name": "Positive"},
+          "summary": "One-line summary"
+        }
+        
+        IMPORTANT RULES:
+        - tags: Array of objects with "name". Allowed values: "Support", "Sales", "Partnership", "Feedback"
+        - sentiment: Object with "name". Allowed values: "Positive", "Neutral", "Negative"
+        - summary: Short summary string (maximum 100 characters)
+        
+        Example for a positive message about the product:
+        {"tags": [{"name": "Feedback"}], "sentiment": {"name": "Positive"}, "summary": "User praises the product"}
+        
+        If there is no significant message:
+        {"tags": [{"name": "Feedback"}], "sentiment": {"name": "Neutral"}, "summary": "New newsletter subscriber"}
+        
+        Return ONLY the JSON, nothing else.
+      messages:
+        - role: "user"
+          content: |
+            Name: $input.name
+            Email: $input.email
+            Message: $input.message
+    result: "userAnalysis"
+
+  # Step 2: Parse the JSON from LLM
+  - id: "parse-analysis"
+    type: "output-generator"
+    config:
+      json: "$stepResult.userAnalysis.text"
+    result: "parsedAnalysis"
+
+  # Step 3: Create Notion page with structured data
+  - id: "create-notion-entry"
+    type: "notion"
+    config:
+      action: "createPage"
+      parent:
+        type: "database_id"
+        database_id: "$env.NOTION_DATABASE_ID"
+      properties:
+        Name:
+          title:
+            - text:
+                content: "$input.name"
+        Email:
+          email: "$input.email"
+        Message:
+          rich_text:
+            - text:
+                content: "$input.message"
+        Summary:
+          rich_text:
+            - text:
+                content: "$stepResult.parsedAnalysis.summary"
+        Tags:
+          multi_select: "$stepResult.parsedAnalysis.tags"
+        Sentiment:
+          select: "$stepResult.parsedAnalysis.sentiment"
+        CreatedAt:
+          date:
+            start: "$input.createdAt"
+    result: "notionResult"
+
+# Explicit Return: Define the API response contract
+return:
+  success: true
+  message: "Registration completed successfully!"
+  notionPageId: "$stepResult.notionResult.pageId"
+  notionUrl: "$stepResult.notionResult.url"
+  analysis:
+    tags: "$stepResult.parsedAnalysis.tags"
+    sentiment: "$stepResult.parsedAnalysis.sentiment"
+    summary: "$stepResult.parsedAnalysis.summary"

package/dist/agents/observability/observability-demo-stream.yaml

@@ -0,0 +1,48 @@
+metadata:
+  name: "Beddel Protocol Expert (Streaming)"
+  version: "1.0.0"
+  builtin: true
+  description: "Multi-step assistant with streaming response"
+  observability:
+    enabled: true
+
+workflow:
+  # Step 1: Fetch Beddel documentation via GitMCP
+  - id: "fetch-docs"
+    type: "mcp-tool"
+    config:
+      url: "https://gitmcp.io/botanarede/beddel"
+      tool: "fetch_beddel_documentation"
+      arguments: {}
+    result: "beddelDocs"
+
+  # Step 2: Search for specific content in documentation
+  - id: "search-docs"
+    type: "mcp-tool"
+    config:
+      url: "https://gitmcp.io/botanarede/beddel"
+      tool: "search_beddel_documentation"
+      arguments:
+        query: "$input.query"
+    result: "searchResults"
+
+  # Step 3: Stream response using chat primitive
+  - id: "respond"
+    type: "chat"
+    config:
+      provider: "google"
+      model: "gemini-2.0-flash-exp"
+      system: |
+        You are an expert assistant specialized in the Beddel Protocol.
+        Use the documentation provided to answer questions accurately.
+        
+        Always respond in Portuguese (Brazilian).
+        Be concise but complete. Include code examples when relevant.
+        If the documentation doesn't cover the topic, say so clearly.
+        
+        ## Beddel Documentation Index
+        $stepResult.beddelDocs.data
+        
+        ## Search Results for User Query
+        $stepResult.searchResults.data
+      messages: "$input.messages"

package/dist/agents/observability/observability-demo.yaml

@@ -0,0 +1,67 @@
+metadata:
+  name: "Beddel Protocol Expert"
+  version: "1.0.0"
+  builtin: true
+  description: "Multi-step assistant demonstrating observability - Expert in Beddel Protocol"
+  observability:
+    enabled: true
+
+workflow:
+  # Step 1: Fetch Beddel documentation via GitMCP
+  - id: "fetch-docs"
+    type: "mcp-tool"
+    config:
+      url: "https://gitmcp.io/botanarede/beddel"
+      tool: "fetch_beddel_documentation"
+      arguments: {}
+    result: "beddelDocs"
+
+  # Step 2: Search for specific content in documentation
+  - id: "search-docs"
+    type: "mcp-tool"
+    config:
+      url: "https://gitmcp.io/botanarede/beddel"
+      tool: "search_beddel_documentation"
+      arguments:
+        query: "$input.query"
+    result: "searchResults"
+
+  # Step 3: Generate expert response using documentation context
+  - id: "generate-response"
+    type: "llm"
+    config:
+      provider: "google"
+      model: "gemini-2.0-flash-exp"
+      system: |
+        You are an expert assistant specialized in the Beddel Protocol.
+        Use the documentation provided to answer questions accurately.
+        
+        Always respond in Portuguese (Brazilian).
+        Be concise but complete. Include code examples when relevant.
+        If the documentation doesn't cover the topic, say so clearly.
+        
+        ## Beddel Documentation Index
+        $stepResult.beddelDocs.data
+        
+        ## Search Results for User Query
+        $stepResult.searchResults.data
+      messages:
+        - role: "user"
+          content: "$input.query"
+    result: "expertResponse"
+
+  # Step 4: Structure final output
+  - id: "format-output"
+    type: "output-generator"
+    config:
+      template:
+        query: "$input.query"
+        answer: "$stepResult.expertResponse.text"
+        sources:
+          - "Beddel Protocol Documentation"
+          - "https://github.com/botanarede/beddel"
+    result: "finalOutput"
+
+return:
+  success: true
+  data: "$stepResult.finalOutput"

package/dist/client.d.ts

@@ -4,7 +4,8 @@
  * This entry point exports ONLY types and utilities safe for client-side use.
  * No Node.js dependencies (fs, crypto, etc.) are included here.
  *
- * Usage: import type { ParsedYaml } from 'beddel/client';
+ * Usage: import type { ParsedYaml, BeddelResponse } from 'beddel/client';
  */
-export type { ParsedYaml, WorkflowStep, StepConfig, YamlMetadata, ExecutionContext, PrimitiveHandler, } from './types';
+export type { ParsedYaml, WorkflowStep, StepConfig, YamlMetadata, ExecutionContext, PrimitiveHandler, BeddelResponse, } from './types';
+export type { ObservabilityConfig, StepEvent, StepStartEvent, StepCompleteEvent, StepErrorEvent, } from './types/observability';
 //# sourceMappingURL=client.d.ts.map

package/dist/client.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../src/client.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAGH,YAAY,EACR,UAAU,EACV,YAAY,EACZ,UAAU,EACV,YAAY,EACZ,gBAAgB,EAChB,gBAAgB,GACnB,MAAM,SAAS,CAAC"}
+{"version":3,"file":"client.d.ts","sourceRoot":"","sources":["../src/client.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAGH,YAAY,EACR,UAAU,EACV,YAAY,EACZ,UAAU,EACV,YAAY,EACZ,gBAAgB,EAChB,gBAAgB,EAChB,cAAc,GACjB,MAAM,SAAS,CAAC;AAGjB,YAAY,EACR,mBAAmB,EACnB,SAAS,EACT,cAAc,EACd,iBAAiB,EACjB,cAAc,GACjB,MAAM,uBAAuB,CAAC"}

package/dist/client.js

@@ -4,6 +4,6 @@
  * This entry point exports ONLY types and utilities safe for client-side use.
  * No Node.js dependencies (fs, crypto, etc.) are included here.
  *
- * Usage: import type { ParsedYaml } from 'beddel/client';
+ * Usage: import type { ParsedYaml, BeddelResponse } from 'beddel/client';
  */
 export {};

package/dist/core/workflow.d.ts

@@ -10,16 +10,28 @@
  *   and that Response is returned immediately to the client.
  * - Non-Response results are stored in context.variables for subsequent steps.
  * - If 'return' is defined in YAML, it shapes the final API response.
+ * - When observability is enabled, trace events are collected and attached to results.
  */
 import type { ParsedYaml } from '../types';
 export declare class WorkflowExecutor {
     private steps;
     private returnTemplate?;
+    private observabilityEnabled;
     /**
      * Create a new WorkflowExecutor from parsed YAML.
      * @param yaml - Parsed YAML document containing workflow steps
      */
     constructor(yaml: ParsedYaml);
+    /**
+     * Push a trace event to the context (no-op if observability disabled).
+     * Errors are caught to prevent trace failures from breaking workflow execution.
+     */
+    private pushEvent;
+    /**
+     * Sanitize error into a safe error type category.
+     * SECURITY: Never exposes full error messages, only categorized types.
+     */
+    private sanitizeErrorType;
     /**
      * Execute the workflow pipeline.
      *

package/dist/core/workflow.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"workflow.d.ts","sourceRoot":"","sources":["../../src/core/workflow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,KAAK,EAAE,UAAU,EAA8C,MAAM,UAAU,CAAC;AAIvF,qBAAa,gBAAgB;IACzB,OAAO,CAAC,KAAK,CAAiB;IAC9B,OAAO,CAAC,cAAc,CAAC,CAAU;IAEjC;;;OAGG;gBACS,IAAI,EAAE,UAAU;IAK5B;;;;;;;;;;;;;;;OAeG;IACG,OAAO,CAAC,KAAK,EAAE,OAAO,GAAG,OAAO,CAAC,QAAQ,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CA2D7E"}
+{"version":3,"file":"workflow.d.ts","sourceRoot":"","sources":["../../src/core/workflow.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AAEH,OAAO,KAAK,EACR,UAAU,EAOb,MAAM,UAAU,CAAC;AAIlB,qBAAa,gBAAgB;IACzB,OAAO,CAAC,KAAK,CAAiB;IAC9B,OAAO,CAAC,cAAc,CAAC,CAAU;IACjC,OAAO,CAAC,oBAAoB,CAAU;IAEtC;;;OAGG;gBACS,IAAI,EAAE,UAAU;IAU5B;;;OAGG;IACH,OAAO,CAAC,SAAS;IASjB;;;OAGG;IACH,OAAO,CAAC,iBAAiB;IAYzB;;;;;;;;;;;;;;;OAeG;IACG,OAAO,CAAC,KAAK,EAAE,OAAO,GAAG,OAAO,CAAC,QAAQ,GAAG,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;CAiH7E"}