The fence arms only on a StoreFenced error that no code in this build creates.
The 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.
- The
StoreFencedstring appears once, at its declaration; the predicate testing for it has only readers, no producer. - 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_restwith a fallback of off. - Neither the field nor the constant exists in v2.1.247.
StoreFenced
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_hover_rest Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.248: off
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.