Before durable history, we have a search optimisation which treats an invisible birthmark as a tombstone. We could do that because we were choosing the stable versions to write to disk. With the change to always write the newest committed versions to disk, this is no longer valid and we should remove it.

Also in durable history, read can be simplified to first walk the update chain then las to find the first visible update.