When the following happens:

• request a vault bundle
• open the /browse/vault/ summary page
• wait for status to go to "done"
• download bundle, be happy
• bundle gets removed from cache
• reopen /browse/vault/
• try to download the bundle again

You end up on an error page of the API saying the bundle doesn't exist.

The summary page should query the vault, at least once, to make sure the "done" status is really still correct; If it is not, the page should allow the user to request the bundle again.

Repro: my local storage contains the following data :

[{"object_type":"revision","object_id":"cf26cbe61e3fba59cec4a01a8ad74bbc70233456","email":"","status":"done","fetch_url":"/api/1/vault/revision/cf26cbe61e3fba59cec4a01a8ad74bbc70233456/gitfast/raw/","progress_message":null},{"object_type":"directory","object_id":"a33c64c6a14eae05ea00a25cd34778815f7a6dd0","email":"","status":"done","fetch_url":"/api/1/vault/directory/a33c64c6a14eae05ea00a25cd34778815f7a6dd0/raw/","progress_message":null}]

And the bundle for the revision is not available any longer in the vault.