{"version":"2.1.248","anchor":"transcript-store-fence-is-wired-but-nothing-in-this-build-ca","canonical_anchor":"transcript-store-fence-is-wired-but-nothing-in-this-build-ca","heading":"Transcript store fence is wired but nothing in this build can trip it","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/transcript-store-fence-is-wired-but-nothing-in-this-build-ca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Transcript store fence is wired but nothing in this build can trip it\n\nA latch can make a session stop writing its transcript, but nothing can trip it here.\n\n**What**\n\nThe transcript writer has a new latch that, once armed, makes the session stop writing its transcript entirely: appends and queue drains rethrow, session metadata re-append returns early, and the compaction backstop is skipped. It arms only on a write error tagged with the new code `StoreFenced`, and nothing in this build creates such an error.\n\n**Details**\n\n- The `StoreFenced` string appears once, at its declaration; the predicate testing for it has only readers, no producer.\n- An emitter would have to come from the storage backend, which is loaded from a dynamically required chunk and only runs under storage v5, itself behind `tengu_hover_rest` with a fallback of off.\n- Neither the field nor the constant exists in v2.1.247.\n\n**Evidence**\n\n`StoreFenced`\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.248; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}