Silent batch fuzzing failures

Hello everyone

We've been using CFL in [rsonpath](https://github.com/rsonquery/rsonpath/) with some success (e.g. https://github.com/rsonquery/rsonpath/issues/281 caught by fuzzing).

Recently, I started getting seemingly spurious failures tracked under https://github.com/rsonquery/rsonpath/issues/749 and discovered that actually, the batch fuzzing was failing for quite some time with timeouts and out-of-memory errors. However, none of those were actually reported as a failure of the pipeline. For example, [here](https://github.com/rsonquery/rsonpath/actions/runs/21124947339) three out of four of our fuzzers failed, yet the pipeline is green. We have a separate action step to automatically create an issue in case of a failure, and that also wasn't triggered. Regarding this, I have three separate questions:

1. How to increase the memory limit? Locally I'd use `rss_limit_mb`, but I don't know how to pass it into the fuzzer through the `.clusterfuzzlite` configuration.
2. How to ensure that my pipeline fails when fuzzers fail for _any_ reason, including timeouts and OOM?
3. Do you know what could cause a failure like [here](https://github.com/rsonquery/rsonpath/actions/runs/21055100156/job/60549667679)?

```sh
2026-01-16 04:08:04,449 - root - INFO - Done downloading corpus. Contains 2479 elements.
2026-01-16 04:08:04,449 - root - INFO - Starting fuzzing
time="2026-01-16T04:10:25Z" level=error msg="error waiting for container: unexpected EOF"
```

I'd appreciate your help with either of those points.