max-shrink-time would be nice. I sometimes resort to dumping the first shrink and then manually shrinking it via other strategies for some of my tests. The callback function would be awesome though - even selectively printing the failures as it shrinks would be helpful

I figured max-shrink time would be useful for CI

Absolutely

Even just printing the seed before a shrink would be helpful, to be honest.

Or giving us a way to do so. The callback idea would work though.

Well the callback is already implemented

Looking forward to trying it