The VSCode extension's gate summary resolves one check later; reported gates are unchanged.
tengu_harbor_willow 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: on
tengu_sable_thrush 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.248: on
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
What's wrong with this entry?
The gate summary sent to the VSCode extension now resolves the sable-thrush check at call time from a bundle chunk instead of at module load. The reported gates are unchanged and still include tengu_harbor_willow and tengu_sable_thrush, whose values come from the server rather than this build.
tengu_sable_thrush
Strings lifted out of the shipped bundle, so the claim above can be checked against them.