if restarting the blob-archiver, it does not resume from where it left off

Start the blob-archiver process from '1' - genesis, it will rapidly index blobs, however if the process is stopped and started again (without any changes) it will not carry on from where it left off... if will just add the most recent blobs as they become available.

Start by reproducing the blob-archiver run from genesis, stop it during indexing, and restart it without changes. The issue names no files or tests, so trace the startup and blob-indexing entry points to find where progress is handled. Done means a restarted process continues from its previous position instead of only adding newly available blobs.

Written by the indexing model from the issue text.