One new switch controls both early artifact comment reads and a lease-based auto-reply mode, off by default.
tengu_slate_lantern_ember gates the control-plane read and lease-based auto-reply arming, falling back to off.
tengu_slate_lantern_ember 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.236: on
tengu_slate_lantern On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.236: on
Read once, for one account on one subscription tier, against v2.1.236. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A new remote flag, falling back to off, is read in exactly two places: it turns on the early control-plane read for artifact auto-reply scans and confirmations, and it selects a lease-based mode for deciding when auto-replies are armed. With the fallback off, both keep current behaviour.
- The similarly named, older
tengu_slate_lantern, also off by default, still controls whether the live-channel token is minted at all.
tengu_slate_lantern_ember
Strings lifted out of the shipped bundle, so the claim above can be checked against them.