Flags can explain whether their value came from an override, the server, a cache or the default.
A flag-provenance table is built but the check that consults it returns a constant false.
What's wrong with this entry?
A new table turns a flag's origin into a sentence: a local override, the experiment payload fetched this session, the on-disk cache left by an earlier session, the built-in default because experiments are off (a third-party model provider, or telemetry opted out), or the built-in default because the cache was cold. The check that decides whether to consult it is a constant returning false in this build, so the accessor always reports the default path.
from GrowthBook (the disk cache of an earlier session)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.