docs: replace transactional-engine references with orchestration engine

Update architecture.md, configuration.md, examples.md, getting-started.md,
README.md, and data-jobs guide to reflect the consolidation of
lib-transactional-engine into fireflyframework-orchestration.

Author: ancongui

README.md

@@ -44,11 +44,11 @@ The starter features abstract controller and service base classes that eliminate
 - Job execution result persistence and audit trails
 - CQRS auto-configuration for command/query integration
 - EDA auto-configuration for event-driven data processing
-- Transactional engine integration for saga-based data flows
+- Orchestration engine integration for saga-based data flows
 - Resilience patterns with circuit breaker and retry decorators
 - Observability with Micrometer metrics and distributed tracing
 - Enrichment caching with configurable cache key generation
-- Step event bridge for transactional engine coordination
+- Orchestration engine support (Saga, TCC, Workflow)
 - Persistence auto-configuration for job results and audit entries
 
 ## Requirements

docs/common/README.md

@@ -46,7 +46,7 @@ These topics are relevant whether you're building data jobs, data enrichers, or
 - Enrichment configuration
 - EDA (Event-Driven Architecture) configuration
 - CQRS configuration
-- Transactional engine configuration
+- Orchestration engine configuration
 - Observability configuration
 - Resiliency configuration
 

docs/common/architecture.md

@@ -60,7 +60,7 @@ The `fireflyframework-starter-data` starter is built on **Hexagonal Architecture
 │  │  │ DataJobController (REST API Port)           │   │         │
 │  │  │ JobOrchestrator (Orchestration Port)        │   │         │
 │  │  │ EventPublisher (EDA Port)                   │   │         │
-│  │  │ StepEventPublisher (SAGA Port)              │   │         │
+│  │  │ OrchestrationEventPublisher (Orchestration Port)│  │         │
 │  │  └─────────────────────────────────────────────┘   │         │
 │  │                                                    │         │
 │  │              DOMAIN CORE                           │         │
@@ -87,7 +87,7 @@ The `fireflyframework-starter-data` starter is built on **Hexagonal Architecture
 #### Outbound Ports (Driven)
 - **JobOrchestrator** - Interface for workflow orchestration
 - **EventPublisher** - Interface for event publishing
-- **StepEventPublisher** - Interface for SAGA step events
+- **OrchestrationEventPublisher** - Interface for orchestration events
 - Defines what the application needs
 - Implemented by infrastructure adapters
 
@@ -105,9 +105,7 @@ config/
 ├── EdaAutoConfiguration            # Event-driven architecture
 ├── JobOrchestrationAutoConfiguration  # Job orchestration setup
 ├── JobOrchestrationProperties      # Configuration properties
-├── StepBridgeConfiguration         # SAGA step event bridge
-├── StepEventsProperties            # Step event configuration
-└── TransactionalEngineAutoConfiguration  # SAGA support
+└── OrchestrationAutoConfiguration  # Orchestration engine support
 ```
 
 **Key Features:**
@@ -269,13 +267,13 @@ public interface JobResultMapper<S, T> {
 }
 ```
 
-### 7. Step Events Layer
+### 7. Orchestration Events Layer
 
-SAGA integration bridge:
+Orchestration engine integration:
 
 ```
-stepevents/
-└── StepEventPublisherBridge  # Bridges SAGA to EDA
+orchestration/
+└── EventGateway  # Bridges orchestration events to EDA (provided by fireflyframework-orchestration)
 ```
 
 ---
@@ -296,8 +294,8 @@ stepevents/
 │  └────────────┬───────────────────────────────┘         │
 │               │                                         │
 │  ┌────────────▼───────────────────────────────┐         │
-│  │  StepEventPublisherBridge                  │         │
-│  │  - SAGA step events                        │         │
+│  │  Orchestration EventGateway               │         │
+│  │  - Orchestration step events               │         │
 │  │  - Metadata enrichment                     │         │
 │  └────────────┬───────────────────────────────┘         │
 └───────────────┼─────────────────────────────────────────┘
@@ -325,7 +323,7 @@ stepevents/
 
 **Integration Points:**
 - Job lifecycle events published to EDA
-- SAGA step events bridged to EDA
+- Orchestration step events bridged to EDA
 - Configurable topics and routing
 - Automatic metadata enrichment
 
@@ -359,33 +357,34 @@ stepevents/
 - **Queries** - Read state (CHECK, COLLECT, RESULT)
 - Enables independent scaling of read/write operations
 
-### Integration with lib-transactional-engine
+### Integration with Orchestration Engine
 
 ```
 ┌─────────────────────────────────────────────────────────┐
-│         lib-transactional-engine                        │
+│         fireflyframework-orchestration                  │
 │                                                         │
 │  ┌────────────────────────────────────────────┐         │
-│  │  SAGA Orchestrator                         │         │
+│  │  Orchestration Engine (Saga, TCC, Workflow)│         │
 │  │  - Step execution                          │         │
 │  │  - Compensation logic                      │         │
 │  │  - Transaction coordination                │         │
 │  └────────────┬───────────────────────────────┘         │
 │               │                                         │
-│               │ Step Events                             │
+│               │ Orchestration Events                    │
 │               ▼                                         │
 │  ┌────────────────────────────────────────────┐         │
-│  │  StepEventPublisher (interface)            │         │
+│  │  OrchestrationEventPublisher (interface)   │         │
+│  │  EventGateway (bridges to EDA)             │         │
 │  └────────────────────────────────────────────┘         │
 └───────────────┼─────────────────────────────────────────┘
                 │
                 ▼
 ┌─────────────────────────────────────────────────────────┐
-│              fireflyframework-starter-data                            │
+│              fireflyframework-starter-data               │
 │                                                         │
 │  ┌────────────────────────────────────────────┐         │
-│  │  StepEventPublisherBridge                  │         │
-│  │  (implements StepEventPublisher)           │         │
+│  │  Consumes orchestration events             │         │
+│  │  (EventGateway bridges to EDA)             │         │
 │  │  - Enriches with data context              │         │
 │  │  - Routes to EDA infrastructure            │         │
 │  └────────────┬───────────────────────────────┘         │
@@ -531,7 +530,7 @@ stepevents/
 **Purpose:** Decouple abstraction from implementation
 
 **Implementation:**
-- `StepEventPublisherBridge` bridges SAGA to EDA
+- `EventGateway` bridges orchestration events to EDA
 - Allows independent evolution of both sides
 - Transparent integration
 

docs/common/configuration.md

@@ -9,7 +9,7 @@ Complete configuration reference for `fireflyframework-starter-data` starter.
 - [Job Orchestration](#job-orchestration)
 - [EDA Integration](#eda-integration)
 - [CQRS Integration](#cqrs-integration)
-- [Transactional Engine](#transactional-engine)
+- [Orchestration Engine](#orchestration-engine)
 - [Step Events](#step-events)
 - [Configuration Examples](#configuration-examples)
 
@@ -27,7 +27,7 @@ firefly:
     eda:                   # Event-Driven Architecture settings
     cqrs:                  # CQRS pattern settings
     orchestration:         # Job orchestration settings
-    transactional:         # SAGA/transactional settings
+    orchestration:         # Orchestration engine settings
   stepevents:              # Step event bridge settings
   eda:                     # fireflyframework-eda configuration
 ```
@@ -47,8 +47,8 @@ firefly:
       enabled: true        # Enable CQRS integration (default: true)
     orchestration:
       enabled: true        # Enable job orchestration (default: true)
-    transactional:
-      enabled: false       # Enable SAGA support (default: true)
+    orchestration:
+      enabled: false       # Enable orchestration engine (default: true)
 ```
 
 **Notes:**
@@ -255,32 +255,19 @@ No additional configuration needed - separation is built into the interfaces.
 
 ---
 
-## Transactional Engine
+## Orchestration Engine
 
 ### Basic Configuration
 
-```yaml
-firefly:
-  data:
-    transactional:
-      enabled: true
-```
-
-### SAGA Configuration
-
-When using SAGAs for distributed transactions:
+The `fireflyframework-orchestration` module is auto-configured via `firefly.orchestration` properties. It consolidates Saga, TCC, and Workflow patterns into a single module with its own `EventGateway` for EDA bridging.
 
 ```yaml
 firefly:
-  transactional:
-    saga:
-      enabled: true
-      default-timeout: 30m
-      max-retries: 3
-      compensation-timeout: 5m
+  orchestration:
+    enabled: true
 ```
 
-**Note:** This configuration is from `lib-transactional-engine`. See that library's documentation for complete options.
+**Note:** See the `fireflyframework-orchestration` module documentation for complete options including Saga, TCC, and Workflow configuration.
 
 ---
 
@@ -348,8 +335,8 @@ firefly:
       orchestrator-type: MOCK              # Use mock for development
       publish-job-events: true
       job-events-topic: dev-job-events
-    transactional:
-      enabled: false                       # Disable SAGAs in dev
+    orchestration:
+      enabled: false                       # Disable orchestration in dev
 
   eda:
     publishers:
@@ -397,7 +384,7 @@ firefly:
         dag-id-prefix: customer_data
         verify-ssl: true
         max-concurrent-dag-runs: 20
-    transactional:
+    orchestration:
       enabled: true
 
   stepevents:
@@ -475,7 +462,7 @@ firefly:
       enabled: true
       orchestrator-type: MOCK              # Use mock orchestrator
       publish-job-events: false            # Don't publish events
-    transactional:
+    orchestration:
       enabled: false
 
 logging:

docs/common/examples.md

@@ -492,7 +492,7 @@ public class CustomerDataEventListener {
 
 ## SAGA Integration
 
-> **Note**: This example demonstrates integration with `lib-transactional-engine` (SAGA orchestrator). The `SagaOrchestrator`, `Saga`, and `Step` classes are from that library, not from fireflyframework-starter-data. This starter provides `StepEventPublisherBridge` to publish step events to the SAGA engine.
+> **Note**: This example demonstrates integration with `fireflyframework-orchestration` (orchestration engine). The `SagaEngine`, `Saga`, and `Step` classes are from that module, not from fireflyframework-starter-data. The orchestration module provides its own `EventGateway` for EDA bridging.
 
 ### Example 8: Multi-Step Data Processing SAGA
 
@@ -501,8 +501,8 @@ public class CustomerDataEventListener {
 @Slf4j
 public class DataProcessingSagaService {
 
-    // SagaOrchestrator is from lib-transactional-engine
-    private final SagaOrchestrator sagaOrchestrator;
+    // SagaEngine is from fireflyframework-orchestration
+    private final SagaEngine sagaEngine;
     private final DataJobService dataJobService;
     // These are your application services
     private final DataTransformationService transformationService;
@@ -533,7 +533,7 @@ public class DataProcessingSagaService {
                 .build())
             .build();
 
-        return sagaOrchestrator.execute(saga)
+        return sagaEngine.execute(saga)
             .map(result -> result.getSagaId())
             .doOnSuccess(sagaId ->
                 log.info("SAGA completed successfully: {}", sagaId))

docs/common/getting-started.md

@@ -154,8 +154,8 @@ firefly:
         password: airflow
         dag-id-prefix: my_service
 
-    # Enable transactional engine (optional)
-    transactional:
+    # Enable orchestration engine (optional)
+    orchestration:
       enabled: false
 
   # Step events configuration (if using SAGAs)

docs/data-jobs/guide.md

@@ -1576,7 +1576,7 @@ All jobs automatically get:
 
 ### Overview
 
-For workflows that require distributed transactions or step-level coordination, integrate with Firefly's transactional engine and event-driven architecture.
+For workflows that require distributed transactions or step-level coordination, integrate with Firefly's orchestration engine and event-driven architecture.
 
 ### Event Publishing