Explicit cache telemetry state — distinguishes the three
"not-enabled" variants from each other so the UI can render an
accurate disabled-reason. A ?noCache URL run produces no
provider, so without this state the cache tab would default to
enabled and mislead the user.
enabled : caching is on AND providers are wired.
disabled-no-cache : caching turned off via ?noCache.
disabled-config : turned off via app config.
not-wired : caching is on but providers haven't been
wired yet (e.g. mid-scene-transition).
Lives in types/ so the data layer (cache-setup.ts) and the UI
layer (ui/data-loading-monitor/metrics/cache.ts) can both reference
it without crossing the layer boundary.
Explicit cache telemetry state — distinguishes the three "not-enabled" variants from each other so the UI can render an accurate disabled-reason. A
?noCacheURL run produces no provider, so without this state the cache tab would default toenabledand mislead the user.enabled: caching is on AND providers are wired.disabled-no-cache: caching turned off via?noCache.disabled-config: turned off via app config.not-wired: caching is on but providers haven't been wired yet (e.g. mid-scene-transition).Lives in
types/so the data layer (cache-setup.ts) and the UI layer (ui/data-loading-monitor/metrics/cache.ts) can both reference it without crossing the layer boundary.