{"version":"2.1.222","anchor":"transcript-writes-and-head-tail-reads-can-go-through-the-v5-","canonical_anchor":"transcript-writes-and-head-tail-reads-can-go-through-the-v5-","heading":"Transcript writes and head\/tail reads can go through the v5 storage backend","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/transcript-writes-and-head-tail-reads-can-go-through-the-v5-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Transcript writes and head\/tail reads can go through the v5 storage backend\n\nTranscript writing can be redirected to a different storage layer, but nothing turns that on here.\n\n**What**\n\nTranscript append, truncate and read helpers can now be pointed at a v5 storage backend instead of the filesystem, but only when a backend handle is passed in.\n\n**Details**\n\n- The helpers take an optional backend handle; when present they call `backend.append`, `backend.delete`, `backend.readText` and `backend.stat` with a key rather than touching files.\n- Failures throw Error(\"transcript stream append failed\") or Error(\"transcript stream delete failed\").\n- The exporter class gained a `storageV5` field.\n- storageV5 existed in the previous build but only on the read path; the write path is new here and inert without a handle.\n\n**Evidence**\n\n`transcript stream append failed`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}