That is, dumping any extra information from Hypothesis clutters up the test
runner output too much to leave this on in general. :(

each, 88 bytes of base64

This way, it can be an empty list.

The first time the node starts there will be no rootcap and there cannot
easily be one unless the node is allowed to start so one can be created.

My guess is most of  the time is spent in create_client_from_config and I
don't know if there's anything we can do about that.

It's not impossible or even disallowed.  However, if a storage index is
repeated it sure as heck better have the same object associated with it -
which this strategy does not ensure.

The new direct positive-path Hypothesis-based test wants to pass in huge
numbers and the float-based implementation does not do well for these inputs.
Happily, we can do better.

Only the documentation was wrong, whew.