Problem

When timeout reporting is suppressed, a FuzzTest runner can exit successfully before completing any input. In the observed DDL case, a later corpus-cleanup error fails the run. Fixing cleanup must not let the timed-out session pass.

Acceptance Criteria

• Resmoke and Evergreen fail when a fuzzing session times out without completing any input, even with a zero exit status and no saved crash.
• The failure identifies the binary and named test, retains timeout diagnostics, and survives cleanup or a later successful named test.
• Healthy runs without coverage growth, deadlines after completed inputs, explicit skips, diagnostic-only modes, and valid partial batches retain their intended behavior.
• Add bounded regression tests and validate the fix in Mongo.

Implementation

Investigate a Mongo-owned fix in buildscripts/resmokelib/testing/testcases/cpp_libfuzzer_test.py first. A single batch's output count does not prove session-wide completion; validate detection before choosing the implementation. Prefer avoiding vendored changes. No dependency on a broad FuzzTest upgrade is proposed.