durable_workflow 0.1.0

data/.claude/todo/phase-5-validation/03-EXAMPLE-SUPPORT-AGENT.md

@@ -0,0 +1,95 @@
+# 03-EXAMPLE-SUPPORT-AGENT: AI-Powered Support System
+
+## ⚠️ STATUS: FUTURE/ASPIRATIONAL
+
+**This document describes a FUTURE example that requires features not yet implemented:**
+
+- `type: agent` step - NOT IMPLEMENTED
+- `type: guardrail` step - NOT IMPLEMENTED
+- `type: handoff` step - NOT IMPLEMENTED
+- `DurableWorkflow::Extensions::AI` - NOT IMPLEMENTED
+- `DurableWorkflow::Extensions::AI::MCP::Server` - NOT IMPLEMENTED
+- `DurableWorkflow.register_service()` - NOT IMPLEMENTED (services use `Object.const_get`)
+- `DurableWorkflow::Runners::Stream` - NOT IMPLEMENTED
+- `runner.subscribe` - NOT IMPLEMENTED
+
+**Do not attempt to run this example until these features are built.**
+
+---
+
+## Goal
+
+Full-featured example app demonstrating AI extension with MCP integration. Claude Desktop can connect to this as an MCP server.
+
+## Required Features (Not Yet Built)
+
+1. **AI Extension** (`lib/durable_workflow/extensions/ai/`)
+   - Agent step executor
+   - Tool calling integration
+   - Model configuration (OpenAI, Anthropic)
+   - Handoff between agents
+
+2. **Guardrails**
+   - Content moderation
+   - Prompt injection detection
+
+3. **MCP Server**
+   - stdio transport for Claude Desktop
+   - Tool discovery and invocation
+
+4. **Event Streaming**
+   - `runner.subscribe` for real-time events
+   - Stream runner for progressive output
+
+---
+
+## Directory Structure (When Implemented)
+
+```
+examples/support_agent/
+  README.md
+  Gemfile
+  workflow.yml
+  services.rb
+  tools.rb
+  run.rb                    # Interactive CLI
+  mcp_server.rb             # MCP stdio server for Claude Desktop
+  config/
+    claude_desktop.json     # Example Claude Desktop config
+```
+
+---
+
+## Workflow Design (Aspirational)
+
+The workflow would:
+1. Receive customer message
+2. Run content moderation guardrail
+3. Triage with AI agent to classify request
+4. Route to specialized agent (billing, technical, general)
+5. Execute tools as needed (lookup_order, create_ticket, etc.)
+6. Support handoffs between agents
+7. Return response
+
+---
+
+## Implementation Prerequisites
+
+Before this example can work, implement:
+
+1. `lib/durable_workflow/extensions/ai/` module
+2. `agent` executor in `lib/durable_workflow/core/executors/agent.rb`
+3. `guardrail` executor for content checks
+4. `handoff` executor for agent transfers
+5. MCP server transport layer
+6. Event subscription system
+
+See the original design below for reference when implementing.
+
+---
+
+## Original Design Reference
+
+[The rest of this file contains the aspirational design that was here before.
+It should be used as a reference when implementing these features, NOT as
+working documentation.]

data/.claude/todo/phase-5-validation/04-EXAMPLE-ORDER-FULFILLMENT.md

@@ -0,0 +1,94 @@
+# 04-EXAMPLE-ORDER-FULFILLMENT: E-Commerce Order Processing
+
+## ⚠️ STATUS: FUTURE/ASPIRATIONAL
+
+**This document describes a FUTURE example that requires features not yet implemented:**
+
+- Ruby expression evaluation in YAML (e.g., `$item.quantity * $item.price`) - NOT SUPPORTED
+- `DurableWorkflow.register_service()` - NOT IMPLEMENTED (use `Object.const_get`)
+- `DurableWorkflow::Runners::Stream` - NOT IMPLEMENTED
+- `runner.subscribe` - NOT IMPLEMENTED
+- `runner.run_until_complete` with block - NOT IMPLEMENTED
+- Loop step with inline computation - NOT SUPPORTED (no expression eval)
+
+**The resolver only supports `$ref` substitution, NOT expression evaluation.**
+
+**Do not attempt to run this example until these features are built or the example is rewritten.**
+
+---
+
+## Goal
+
+Complete order fulfillment workflow demonstrating complex business logic, service integration, approvals, and error handling.
+
+## Why This Example Doesn't Work
+
+The workflow.yml in the original design relies heavily on Ruby expressions:
+
+```yaml
+# These DO NOT WORK - no expression evaluation
+set:
+  line_total: "$item.quantity * $item.price"    # ❌ No arithmetic
+  subtotal: "$subtotal + $line_total"           # ❌ No arithmetic
+  tax: "$subtotal * $tax_rate"                  # ❌ No arithmetic
+  shipping_cost: "$subtotal >= 100 ? 0 : 9.99"  # ❌ No ternary
+```
+
+## How To Make This Work
+
+To implement this example with current capabilities:
+
+1. **Move ALL computation to services** - Every arithmetic operation must be in Ruby code
+2. **Use `Object.const_get` for services** - Define as global modules/classes
+3. **Use `Runners::Sync`** - The only working runner
+4. **Simplify the workflow** - Use fewer steps, delegate logic to services
+
+Example of correct approach:
+
+```ruby
+module OrderCalculator
+  def self.calculate_totals(items:, tax_rate: 0.08)
+    subtotal = items.sum { |i| i[:quantity] * i[:price] }
+    tax = subtotal * tax_rate
+    shipping = subtotal >= 100 ? 0 : 9.99
+    {
+      subtotal: subtotal,
+      tax: tax,
+      shipping: shipping,
+      total: subtotal + tax + shipping
+    }
+  end
+end
+```
+
+```yaml
+- id: calculate
+  type: call
+  service: OrderCalculator
+  method: calculate_totals
+  input:
+    items: "$input.items"
+  output: totals
+  next: end
+```
+
+---
+
+## Implementation Prerequisites
+
+To run this example AS DESIGNED (with expressions), implement:
+
+1. Expression evaluation in resolver (or a dedicated `eval` step type)
+2. `DurableWorkflow.register_service()` method
+3. `Runners::Stream` with event subscription
+4. `run_until_complete` with halt handling
+
+OR rewrite the example to work with current constraints.
+
+---
+
+## Original Design Reference
+
+[The original design below should be used as a reference for what the workflow
+SHOULD do, but the YAML syntax needs to be rewritten to use services for all
+computation.]

data/.claude/todo/phase-5-validation/05-EXAMPLE-DATA-PIPELINE.md

@@ -0,0 +1,145 @@
+# 05-EXAMPLE-DATA-PIPELINE: ETL Data Processing
+
+## ⚠️ STATUS: FUTURE/ASPIRATIONAL
+
+**This document describes a FUTURE example that requires features not yet implemented:**
+
+- Ruby expression evaluation in YAML - NOT SUPPORTED
+- `DurableWorkflow.register_service()` - NOT IMPLEMENTED (use `Object.const_get`)
+- `DurableWorkflow.subscribe(pattern:)` - NOT IMPLEMENTED
+- `DurableWorkflow::Runners::Stream` - NOT IMPLEMENTED
+- `runner.subscribe` - NOT IMPLEMENTED
+- Parallel branches as named hash - NOT SUPPORTED (use array of step defs)
+
+**The resolver only supports `$ref` substitution, NOT expression evaluation.**
+
+**Do not attempt to run this example until these features are built or the example is rewritten.**
+
+---
+
+## Goal
+
+Data processing pipeline demonstrating transforms, parallel execution, external MCP consumption, and streaming events.
+
+## Why This Example Doesn't Work
+
+The workflow.yml relies on:
+
+```yaml
+# These DO NOT WORK
+set:
+  job_id: "'JOB-' + Date.now().toString(36)"  # ❌ No JS/Ruby eval
+  raw_data: "$csv_data.concat($api_data || [])"  # ❌ No method calls
+  stats:
+    extracted: "$raw_data.length"  # ❌ No method calls
+
+# Parallel branches format is wrong
+branches:
+  csv_extract:    # ❌ Named hash not supported
+    - id: ...
+  api_extract:    # ❌ Should be array of steps
+    - id: ...
+```
+
+## How To Make This Work
+
+1. **Move ALL computation to services** - Merging arrays, counting, etc.
+2. **Use array format for parallel branches**:
+
+```yaml
+branches:
+  - id: extract_csv
+    type: call
+    service: CSVExtractor
+    ...
+  - id: extract_api
+    type: call
+    service: APIExtractor
+    ...
+```
+
+3. **Use `Object.const_get` for services** - Global modules
+4. **Use `Runners::Sync`** - The only working runner
+5. **Skip event streaming** - Not implemented
+
+---
+
+## Example Files That Were Created (Broken)
+
+The `examples/data_pipeline/` directory was created but has been **deleted** because it relied on non-existent features:
+
+- `run.rb` - Used `register_service`, `Runners::Stream`, `runner.subscribe`
+- `stream_monitor.rb` - Used `DurableWorkflow.subscribe(pattern:)`
+- `workflow.yml` - Used Ruby expressions throughout
+
+---
+
+## Implementation Prerequisites
+
+To run this example AS DESIGNED, implement:
+
+1. Expression evaluation in resolver
+2. `DurableWorkflow.register_service()` method
+3. `DurableWorkflow.subscribe(pattern:)` for global event subscription
+4. `Runners::Stream` with event callbacks
+5. Named branch support in parallel step (or document array-only)
+
+OR rewrite the example to work with current constraints.
+
+---
+
+## Minimal Working Alternative
+
+Here's a simplified data pipeline that WOULD work:
+
+```ruby
+module DataPipeline
+  def self.run_etl(source_file:, output_path:)
+    # Extract
+    records = CSV.read(source_file, headers: true).map(&:to_h)
+
+    # Validate
+    valid, invalid = records.partition { |r| r["email"]&.include?("@") }
+
+    # Transform
+    transformed = valid.map do |r|
+      r.merge("domain" => r["email"]&.split("@")&.last)
+    end
+
+    # Load
+    File.write("#{output_path}/records.json", JSON.pretty_generate(transformed))
+    File.write("#{output_path}/errors.json", JSON.pretty_generate(invalid))
+
+    {
+      extracted: records.size,
+      valid: valid.size,
+      invalid: invalid.size,
+      output_path: output_path
+    }
+  end
+end
+```
+
+```yaml
+steps:
+  - id: start
+    type: start
+    next: process
+
+  - id: process
+    type: call
+    service: DataPipeline
+    method: run_etl
+    input:
+      source_file: "$input.source_file"
+      output_path: "$input.output_path"
+    output: result
+    next: end
+
+  - id: end
+    type: end
+    result:
+      stats: "$result"
+```
+
+This delegates everything to the service, which is the correct pattern given current resolver limitations.

data/.env.example

@@ -0,0 +1,3 @@
+# Copy to .env and fill in your API keys
+OPENAI_API_KEY=sk-your-openai-key-here
+ANTHROPIC_API_KEY=sk-ant-your-anthropic-key-here

data/.rubocop.yml

@@ -0,0 +1,64 @@
+AllCops:
+  TargetRubyVersion: 3.1
+  NewCops: enable
+  SuggestExtensions: false
+  Exclude:
+    - 'vendor/**/*'
+    - 'examples/**/*'
+    - 'spec/**/*'
+    - 'test/**/*'
+
+# Disable noisy cops for this project
+Style/Documentation:
+  Enabled: false
+
+Metrics/MethodLength:
+  Enabled: false
+
+Metrics/AbcSize:
+  Enabled: false
+
+Metrics/CyclomaticComplexity:
+  Enabled: false
+
+Metrics/PerceivedComplexity:
+  Enabled: false
+
+Metrics/ClassLength:
+  Enabled: false
+
+Metrics/ParameterLists:
+  Enabled: false
+
+Layout/LineLength:
+  Max: 200
+
+Gemspec/OrderedDependencies:
+  Enabled: false
+
+Naming/PredicateMethod:
+  Enabled: false
+
+Naming/MethodParameterName:
+  Enabled: false
+
+Lint/MissingSuper:
+  Enabled: false
+
+Lint/UnusedMethodArgument:
+  Enabled: false
+
+Lint/UnusedBlockArgument:
+  Enabled: false
+
+Lint/DuplicateBranch:
+  Enabled: false
+
+Lint/NonLocalExitFromIterator:
+  Enabled: false
+
+Style/SafeNavigationChainLength:
+  Enabled: false
+
+Style/OptionalBooleanParameter:
+  Enabled: false

data/0.3.amend.md

@@ -0,0 +1,89 @@
+# 0.3 Amendment: Kill Fallback Plague
+
+## 1. `run` signature → `input:` kwarg
+
+```ruby
+# Before
+engine.run({ value: 21 })
+
+# After
+engine.run(input: { value: 21 })
+```
+
+**Files:**
+- `lib/durable_workflow/core/engine.rb` - `def run(input, ...)` → `def run(input: {}, ...)`
+- `lib/durable_workflow/runners/sync.rb` - `def run(input, ...)` → `def run(input: {}, ...)`
+- `lib/durable_workflow/runners/sync.rb` - `def run_until_complete(input, ...)` → `def run_until_complete(input: {}, ...)`
+- `lib/durable_workflow/runners/stream.rb` - same
+- `lib/durable_workflow/runners/adapters/sidekiq.rb` - `engine.run(args[:input] || {}, ...)` → `engine.run(input: args[:input], ...)`
+- `lib/durable_workflow/runners/adapters/inline.rb` - `engine.run(input || {}, ...)` → `engine.run(input:, ...)`
+
+**Examples (update call sites):**
+- `examples/order_fulfillment/run.rb:72` - `runner.run(order)` → `runner.run(input: order)`
+- `examples/file_search_demo.rb:69` - `runner.run({ query: ... })` → `runner.run(input: { query: ... })`
+- `examples/item_processor.rb:75` - `runner.run({...})` → `runner.run(input: {...})`
+- `examples/calculator.rb:148` - `runner.run(input)` → `runner.run(input:)`
+- `examples/approval_request.rb:94,99` - `runner.run({...})` → `runner.run(input: {...})`
+- `examples/support_agent/run.rb:52` - `runner.run({...})` → `runner.run(input: {...})`
+- `examples/service_integration.rb:125,130,135` - `runner.run({...})` → `runner.run(input: {...})`
+- `examples/parallel_fetch.rb:96` - `runner.run({...})` → `runner.run(input: {...})`
+- `examples/hello_workflow.rb:52` - `runner.run({...})` → `runner.run(input: {...})`
+
+**Tests (update call sites):**
+- `test/integration/workflow_test.rb:72,80,113,161,201,246,268`
+- `test/unit/runners/async_test.rb:50,58,66,76,86,130`
+- `test/unit/runners/sync_test.rb:78,88,97,107`
+- `test/unit/runners/stream_test.rb:67,79,91,106,118,133,149`
+- `test/unit/core/engine_test.rb:70,87,100,121,139,160,183,231,252,268`
+
+---
+
+## 2. Indifferent access util
+
+Add `Utils.fetch(hash, key)` - kills `x[key.to_sym] || x[key.to_s]` pattern.
+
+**Add to:**
+- `lib/durable_workflow/utils.rb`
+
+**Replace in:**
+- `lib/durable_workflow/core/resolver.rb:49`
+- `lib/durable_workflow/core/validator.rb:249,255`
+- `lib/durable_workflow/core/executors/transform.rb:44`
+- `lib/durable_workflow/extensions/ai/executors/mcp.rb:26,37`
+- `lib/durable_workflow/extensions/ai/executors/agent.rb:110,111`
+- `lib/durable_workflow/extensions/ai/mcp/adapter.rb:54,55`
+
+---
+
+## 3. dry-struct defaults
+
+Add `.default()` to type attributes:
+
+| Attribute | Default |
+|-----------|---------|
+| `files` | `[]` |
+| `max_results` | `10` |
+| `checks` | `[]` |
+| `arguments` | `{}.freeze` |
+| `data` | `{}` |
+| `reason` | `"Halted"` |
+| `wait` | `"all"` |
+| `tools` | `[]` |
+| `headers` | `{}.freeze` |
+| `transport` | `:http` |
+
+---
+
+## 4. Remove dead fallbacks
+
+After defaults are set, remove `|| {}` / `|| []` from:
+
+- `lib/durable_workflow/core/executors/halt.rb:10,14,18`
+- `lib/durable_workflow/core/executors/end.rb:11`
+- `lib/durable_workflow/core/executors/loop.rb:91`
+- `lib/durable_workflow/core/executors/parallel.rb:24`
+- `lib/durable_workflow/extensions/ai/executors/file_search.rb:10,11`
+- `lib/durable_workflow/extensions/ai/executors/mcp.rb:11`
+- `lib/durable_workflow/extensions/ai/executors/agent.rb:59`
+- `lib/durable_workflow/extensions/ai/executors/guardrail.rb:30,31`
+- `lib/durable_workflow/extensions/ai/ai.rb:70,109,122,123,131,136,141`

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2025-11-28
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at ben@dee.mx. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,22 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+gemspec
+
+# Development
+gem 'minitest', '~> 5.0'
+gem 'rake', '~> 13.0'
+gem 'rubocop', '~> 1.21'
+
+# Storage adapters (for testing)
+gem 'activerecord', '~> 7.0'
+gem 'redis', '~> 5.0'
+gem 'sequel', '~> 5.0'
+gem 'sqlite3', '~> 1.6'
+
+# AI extension (now runtime dependencies via gemspec)
+# ruby_llm, mcp, faraday are declared in gemspec
+
+# Examples
+gem 'dotenv', '~> 3.0'