expr, cargo-fuzz: address review nits

Drop the duplicated value_between doc summary line, and document that the
fuzz runner's interrupted classification treats a kernel OOM SIGKILL as
interrupted too, relying on libFuzzer's rss limit to catch memory blowups
as artifact-producing OOMs first.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Q5GiWioZM6CWrwWgfBADDR

Author: def-

src/expr/src/interpret.rs

@@ -256,7 +256,6 @@ impl<'a> ResultSpec<'a> {
         }
     }
 
-    /// A spec that matches values between the given (non-null) min and max.
     /// A spec for the values between `min` and `max` inclusive.
     ///
     /// Unordered bounds widen to [`ResultSpec::value_all`] instead of collapsing

test/cargo-fuzz/mzcompose.py

@@ -437,7 +437,10 @@ def _reap(self, job: Job) -> None:
         ):
             # Killed by a signal (Ctrl-C, step timeout, an external kill)
             # without a crash artifact: an interrupted run, not a crash.
-            # Crashes always leave an artifact, so this cannot mask one.
+            # libFuzzer-detected crashes always leave an artifact, so this
+            # cannot mask one. A kernel OOM SIGKILL is also reported as
+            # interrupted; the rss limit passed to libFuzzer catches memory
+            # blowups as artifact-producing OOMs well before the kernel does.
             self.succeeded.append(job)
             say(
                 f"- {job.name} interrupted by signal {-job.returncode} [{secs}s]  "