Saga Orchestration Patterns for managing distributed transactions and long-running business processes without two-phase commit. Inputs and Outputs What you provide: - Service boundaries and ownership (which service owns which step) - Transaction requirements (which steps must be atomic, which can be eventual) - Failure modes for each step (transient vs. permanent, retry policy) - SLA requirements per step (informs timeout configuration) - Existing event/messaging infrastructure (Kafka, RabbitMQ, SQS, etc.) What this skill produces: - Saga definition with ordered steps, action commands, and co…