Complain when overwriting a dirty cache on read

We got rid of the `setClean()` method on ResourceCacheEntry, but we
still need to transition from a dirty to non-dirty cache state, and
sometimes this is actually expected, totally normal behavior.

Something is still kinda wonky about cache clean/dirty handling -- more
thinking / work necessary to figure out how to proceed.
Bump version to 1.0.7