From aa8554758d7dbaa0e8a177b430fb5b079363884f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Franc=CC=A7ois=20Pottier?= <francois.pottier@inria.fr>
Date: Wed, 12 Mar 2025 22:30:18 +0100
Subject: [PATCH] CHANGES.

---
 CHANGES.md | 23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/CHANGES.md b/CHANGES.md
index 0545dc2..b957754 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -2,17 +2,18 @@
 
 ## 2025/MM/DD
 
-* The new functions `run_afl` and `run_random` can be used to start Monolith's
-  testing engine without allowing Monolith to parse the command line.
-  The function `main`, which parses the command line and starts testing,
-  can still be used. (Contributed by Gabriel Scherer.)
-
-* If the command line is parsed via `main` then the command line option
-  `--timeout <seconds>` is supported. In random testing mode (only), this
-  option causes testing to stop after the specified time limit has been
-  reached. The process then terminates with an exit code of either 0 (which
-  means no failure scenarios were detected) or 1 (which means that one or more
-  failure scenarios were detected).
+* The new function `run` can be used to start Monolith's testing engine
+  without allowing Monolith to parse the command line. The function `main`,
+  which parses the command line and starts testing, can still be used.
+  (Suggested by Gabriel Scherer.)
+
+* If the command line is parsed via `main` then the command line options
+   `--fuel <int>` and
+   `--max_scenarios <int>` and
+   `--save-scenario <bool>` and
+   `--show-scenario <bool>` and
+  `--timeout <int>`
+  are supported.
 
 * In random testing mode, a single counter and clock is now used for all
   tests, whereas previously a fresh counter and clock would be created every
-- 
GitLab