A new artifact relay flag is read by one function that nothing appears to call.
tengu_cobalt_plinth_fennel is compiled off, read once, and its reader has no visible caller anywhere in the build.
tengu_cobalt_plinth_fennel 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.247: not a boolean we can read
Read once, for one account on one subscription tier, against v2.1.247. 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 artifact-relay flag, compiled to off, is read by a single small function whose name was freed up by renaming the route-classifying helper that used to own it. No call to that function appears in the surrounding module, and the flag name occurs exactly once in the whole build.
- Name reuse across scopes in this build means a caller elsewhere cannot be ruled out; either way the fallback is off, so whatever it selects needs a server-side value.
- Live in the same module: the relay now reports once per session, under
artifact_frame_relay/bot_context_not_served, that bot contexts are not relayed.
tengu_cobalt_plinth_fennel
Strings lifted out of the shipped bundle, so the claim above can be checked against them.