Need better dev tools

It's difficult to tell exactly what's going on with the required data and fetches.

It would be nice if there existed development data that could describe the following:

1. What data is required and from which components (a count would be nice too)
2. What is the current reduced requirement for each data element (e.g. lowest freshness, etc.)
3. What is the state of each data element? (e.g. fresh, stale, timed-out, fetching)
4. When will the data element be fetched next? (e.g. timeout in 1.8 secs, stale in 55 secs)

Start by tracing how fresh-data represents required data and fetches; the issue names no files, tests, or entry points. Compare the existing development experience with the four requested visibility areas: requirements and component counts, reduced requirements, element state, and the next fetch timing. Done means the scope and presentation of this development data are defined and verified.

Written by the indexing model from the issue text.