A v5 storage backend path exists for transcripts and changelog, but nothing supplies a backend in this build.
What
New code paths route storage through a backend object rather than the filesystem, covering transcript loads, the usage-report session scan and changelog fetch and migration.
Details
- Transcript loading takes a
storageV5{ backend, key }option; a permission failure yields an empty transcript, other errors throw. - The usage-report session scan enumerates entries under the
transcriptnamespace with cursor paging instead of walking project directories. - Changelog fetch and migration write to a storage key with an
ifAbsentprecondition. - All three fall back to the existing file paths when no backend is supplied; what supplies a backend could not be determined in this build.
Evidence
loadTranscriptFile: v5 read inaccessible (permission) — empty result
Strings lifted out of the shipped bundle, so the claim above can be checked against them.