An inline TODO tracked this. And we were reminded of it when
recently implementing storage integration tests. Let's fix it so
we don't have to port the buggy behavior to future storage backends.
The new call to read() should be fast because the revision
fulltext should be cached as part of calling renamed(). So the
overhead here should be minimal.