Summary

Adds theallow_async? flag to thecompose DSL to control whether composed reactors can run their steps asynchronously.

Closes#22

Changes

• Addedallow_async? field toReactor.Dsl.Compose struct with default valuetrue
• Updated DSL schema to include the newallow_async? option with documentation
• ModifiedBuilder.Compose to pass theallow_async? option toReactor.Step.Compose
• UpdatedStep.Compose to respect theallow_async? option when callingReactor.run
• Added comprehensive tests intest/reactor/dsl/compose_test.exs to verify functionality
• Updated documentation with usage examples

Usage

compose:create_user,UserReactordoargument:name,input(:user_name)argument:email,input(:user_email)allow_async?false# Forces synchronous executionend

Behavior

• allow_async? true (default): The composed reactor runs withasync?: true, allowing its steps to execute asynchronously
• allow_async? false: The composed reactor runs withasync?: false, forcing all its steps to execute synchronously

Implementation Notes

This implementation uses runtime composition only (no compile-time composition), following the simplified approach introduced in commit716682f. Theallow_async? flag is passed through the DSL → Builder → Step chain and controls theasync? parameter passed toReactor.run inStep.Compose.

Testing

Added comprehensive test coverage including:

• Basic compose functionality withallow_async? option
• DSL structure validation to ensure options are correctly passed through
• Process ID tracking to verify actual async/sync behavior
• Multi-argument compose scenarios