Documentation-only task for the Manual application timezone control feature. Updates docs/ARCHITECTURE.md and timezone docstrings/comments to state that the application timezone is set manually by an admin from the admin app, that the stored value is the single source of local-time truth for the whole application (panel snapshot overdue/today, both panel cards, completion timestamps, the missed-sweep scheduler, admin reads), that empty means the API host local zone, and that an admin save re-plans the sweep scheduler. No behavioural code; no schema change.
Documentation-only task for the Manual application timezone control feature. Updates docs/ARCHITECTURE.md and timezone docstrings/comments to state that the application timezone is set manually by an admin from the admin app, that the stored value is the single source of local-time truth for the whole application (panel snapshot overdue/today, both panel cards, completion timestamps, the missed-sweep scheduler, admin reads), that empty means the API host local zone, and that an admin save re-plans the sweep scheduler. No behavioural code; no schema change.
Add an "Application timezone" section to docs/ARCHITECTURE.md: the
timezone is set only by an admin from the admin app (GET/PATCH
/api/v1/admin/settings), is the single source of local time for the
panel, completions, the missed-sweep scheduler and the admin app, means
the API host's local zone while empty (published as the effective zone),
and an admin save of timezone or day_rollover_time re-plans the sweep.
Correct docstrings and comments that still described the local date as
Home Assistant's ("HA-local", read from hass.config.time_zone by the
integration) or the stored zone as reported from Home Assistant.
Comment and docstring changes only; no behaviour change.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The CONF_TIMEZONE comment claimed the integration always uses Home
Assistant's time_zone and ignores the field; it actually relays the
API's effective application timezone. Also reword two materialize.py
docstrings that described the household date as HA-derived.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Documentation-only task for the Manual application timezone control feature. Updates docs/ARCHITECTURE.md and timezone docstrings/comments to state that the application timezone is set manually by an admin from the admin app, that the stored value is the single source of local-time truth for the whole application (panel snapshot overdue/today, both panel cards, completion timestamps, the missed-sweep scheduler, admin reads), that empty means the API host local zone, and that an admin save re-plans the sweep scheduler. No behavioural code; no schema change.
Add an "Application timezone" section to docs/ARCHITECTURE.md: the timezone is set only by an admin from the admin app (GET/PATCH /api/v1/admin/settings), is the single source of local time for the panel, completions, the missed-sweep scheduler and the admin app, means the API host's local zone while empty (published as the effective zone), and an admin save of timezone or day_rollover_time re-plans the sweep. Correct docstrings and comments that still described the local date as Home Assistant's ("HA-local", read from hass.config.time_zone by the integration) or the stored zone as reported from Home Assistant. Comment and docstring changes only; no behaviour change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Independent Codex gpt-5.6-terra review completed for this exact commit.