Cucumber 7.0 default plugin shift impacts alert clarity when using pretty and json together

Goal: Configure Cucumber to emit step‑level alerts via the pretty plugin while simultaneously generating JSON output for downstream alerting, keeping console noise low.

Constraint: Starting with Cucumber 7.0 the default plugin list changed to ['progress']; adding both 'pretty' and 'json' plugins does not guarantee a deterministic order, which can cause interleaving of pretty‑formatted step lines and JSON events, especially when the monochrome flag strips ANSI codes.

Questions: Does Cucumber provide a mechanism to enforce plugin output order or to isolate streams? Can users rely on monochrome plus plugin selection to avoid interleaving in CI logs? Is there a recommended pattern or workaround to obtain clear step alerts and clean JSON without noise?