{"version":"2.1.269","anchor":"per-model-weekly-usage-window-docstring-clarified-to-disting","canonical_anchor":"per-model-weekly-usage-window-docstring-clarified-to-disting","heading":"Per-model weekly usage window docstring clarified to distinguish 'unknown' from 'empty'","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/per-model-weekly-usage-window-docstring-clarified-to-disting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Per-model weekly usage window docstring clarified to distinguish 'unknown' from 'empty'\n\nDocumentation for per-model weekly usage data now spells out what 'missing' means versus 'empty'\n\n**What**\n\nThe internal documentation comment for the per-model weekly usage-window data was rewritten to clarify a distinction: if the field is absent entirely, nothing is known about it (for example because the data came from a cache or the account was hidden by an allowlist), whereas an empty array means the server answered and confirmed there are no usage windows for the account.\n\n**Why**\n\nThis is a documentation clarification for a data field rather than a behavior change; it helps whoever reads this usage data avoid confusing 'we don't know' with 'we know there's nothing'.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}