The early artifact comment read needs two separate switches, both of which default off.
The auto-reply scan passes the early-read option only under tengu_slate_lantern_ember, and the read itself needs tengu_onyx_sluice.
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_onyx_sluice 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?
The pre-startup control-plane comment read has one caller, the artifact comment auto-reply scan, and it passes the option only when tengu_slate_lantern_ember is on. Even then the read itself needs tengu_onyx_sluice. Both fall back to off, so neither half runs unless remote config enables both.
- The option defaults to false at the reader itself, and no other code in the build passes it.
- The attempt carries a callback so it is scored whether it succeeds or falls back to the normal read.
- The same change lets a session whose outbound network is blocked reuse an already-successful control-plane result rather than reporting a denial.
controlPlaneReadBeforeBoot
Strings lifted out of the shipped bundle, so the claim above can be checked against them.