Look into providing as a proptest strategy

Not too sure what all would go into this, but may be nice to provide a proptest strategy using this library as well. I was thinking that simplifying can deal with making names more basic, contents less complex (less randomness and smaller), and reducing the amount of overall entries, while making things more complex would just be the opposite

No files or tests are named. Start by reviewing the library's existing directory-generation API and the requirements for a proptest strategy, then determine how simplification and complication should affect names, contents, randomness, and entry count. Done means the strategy's scope and behavior are defined and covered by tests.

Written by the indexing model from the issue text.