Expand description
Replay engine — operation-keyed state with visited tracking.
Implement FR1-FR5: history loading, replay/execute mode detection, cached result return, checkpoint execution, and replay status transitions.
The replay engine uses a HashMap<String, Operation> keyed by operation ID
(matching the Python SDK’s approach) and tracks which operations have been
visited. The replay status transitions from Replaying to Executing when
all completed operations in history have been visited.
Structs§
- Replay
Engine - Manage replay state for a durable execution.