Resuming a session no longer points at a transcript file that was never there.
What's wrong with this entry?
Working out which transcript file belongs to a session id now reports one of three answers: found, definitely absent, or present but unverifiable. An unverifiable candidate is remembered and used as a last resort instead of the code inventing a path that does not exist.
- Listing calls to the storage backend are memoized during a single resolution, so repeated transcript listings do not re-page the backend.
unverifiable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.