Have reducer provide info about why further reduction was not possible

The reducer will give you the smallest example it can find.

It might be useful if it also gave you one (or a few) smaller examples that were not interesting, to provide some context around why reduction couldn't get further.

Start by locating the reducer entry point and tracing how it selects the smallest interesting example. Define how smaller non-interesting examples should be retained and presented, then add coverage for the reported context; the issue names no files or tests, so repository search is needed first.

Written by the indexing model from the issue text.