Scenarios will be trusted YAML or JSON data files. They will configure the seed, virtual clock, default action delays, rate limits, and typed faults. A fixed scenario and request sequence must produce byte-identical journals across runs.
Use scenarios for behaviours such as:
- failing the first cluster creation request;
- delaying actions by virtual time;
- returning stale reads for a bounded window;
- forcing rate-limit responses;
- holding an action in progress.