Artifact comments could be read over the control plane before startup, but the flag falls back to off.
An early control-plane comment read with token fallback sits behind tengu_onyx_sluice, off in this build.
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 artifact comment reader gains an option to try the control plane first and fall back to the normal token-based read, scoring the attempt either way. The flag involved, tengu_onyx_sluice, falls back to off in this build.
- When the sandbox blocks outbound traffic to the content host, the read can now recover using an already-successful control-plane result instead of failing.
tengu_onyx_sluice
Strings lifted out of the shipped bundle, so the claim above can be checked against them.