hash the file

Keep a hash of the stream, when completed.

As the stream is uploaded, you'll build a hash, and then save it when the stream ends.

Could save it as `filename HASH` which would sort after all the regular chunks.

You could also store the size etc, and then query that easily.

hmm - what about storing the hashes is a separate section (prefix) so that you can easily query what files the store has, and their hashes?

No files, tests, or entry points are named. Start by locating the stream-upload completion path and the LevelDB storage layout, then determine how hashes and file metadata should be indexed. Done means completed uploads have queryable hashes and metadata without disrupting regular chunks, with tests covering the chosen layout.

Written by the indexing model from the issue text.