Unclear Nothing has been read about the tengu_kestrel_moor gate, so whether or how this feature is enabled is unknown.
A new latch, alongside the existing sticky betas and per-turn effort pins, is now stored on the conversation. It is written into the session state file as { type: "atis-latch", sessionId, atis }, merged with "always"/"last-wins" semantics like the existing isolation-latch, and carried through fork and resume via atisLatchAtEntry and the session-state snapshot APIs. Its value originates from client config (atis), and once latched it is preferred over the live config for the rest of the conversation.
tengu_kestrel_moor Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.235: on
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
Nothing has been read about the `tengu_kestrel_moor` gate, so whether or how this feature is enabled is unknown.
New in this build: tengu_kestrel_moor