Tags

Add authorization support to engine

Add AuthProvider interface for pluggable authorization and integrate
it into workflow registration and execution. Include example of
multi-tenant auth implementation.

Fix workflow tests by registering functions and adding configs

The test workflows were missing function registrations and node
configurations, causing execution failures. Register a "test"
function and add the corresponding function config to each node.

Expand README with quick start, real-world examples, and comprehensive

documentation

Parse signal data in mergeSignalData

v1.0.0 - Initial Release with Auth System

Major Features:
- ✅ Flexible, pluggable authorization system (like EventBus pattern)
- ✅ Multi-tenant support with customer isolation
- ✅ Role-based and team-based access control
- ✅ Workflow metadata for auth data storage
- ✅ SQL migrations for metadata columns
- ✅ Comprehensive test coverage (82.7%)
- ✅ All golangci-lint checks passing

Core Features:
- DAG-based workflow execution
- Distributed task processing
- Multiple storage backends (MySQL, PostgreSQL, Redis, Memory)
- Event system for notifications
- Retry policies and Saga pattern
- Built-in node types (HTTP, AI, Transform, etc.)
- REST API and Webhook triggers
- Prometheus metrics

Auth System:
- Minimal interface: CheckAccess(ctx, resource, action)
- No prescribed structure (user_id, customer_id, slug, email - your choice)
- Context-based auth info passing
- Workflow.Metadata for flexible auth data storage
- Optional - no auth provider = everything allowed

Documentation:
- Complete README with auth examples
- Example implementations (examples/auth/)
- Test coverage with multi-tenant scenarios