In order to be better able to quickly debug "unexpected results" in the BrowseResult, I propose the following enhancements to the BrowseRequest toString method:
1. Add to each field the underlying index field name(s)
2. Add a Lucene compatible query that includes not only the base lucene query, but also includes the Browse selections in a lucene compatible manner and the browse filter
Ideally, it would be possible to also include query or filter elements that are numerical. But I'm not sure how this would work converting this to a Lucene compatible query string or whether Luke supports this currently.