{"version":"2.1.221","anchor":"transcripts-session-listings-and-the-changelog-can-be-read-a","canonical_anchor":"transcripts-session-listings-and-the-changelog-can-be-read-a","heading":"Transcripts, session listings and the changelog can be read and written through a v5 storage backend","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/transcripts-session-listings-and-the-changelog-can-be-read-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Transcripts, session listings and the changelog can be read and written through a v5 storage backend\n\nTranscripts, session listings and the changelog can be read from a storage backend instead of local files.\n\n**What**\n\nNew 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.\n\n**Details**\n\n- Transcript loading takes a `storageV5` `{ backend, key }` option; a permission failure yields an empty transcript, other errors throw.\n- The usage-report session scan enumerates entries under the `transcript` namespace with cursor paging instead of walking project directories.\n- Changelog fetch and migration write to a storage key with an `ifAbsent` precondition.\n- 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.\n\n**Evidence**\n\n`loadTranscriptFile: v5 read inaccessible (permission) \u2014 empty result`\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}