fix(occupancy): a holiday passed with no frozen record still splits the readers #246
Labels
No labels
blocked
bug
enhancement
high-priority
low-priority
needs-info
needs-triage
ready-for-agent
ready-for-human
referenced
research
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gabogg/hikcentral#246
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
P3 follow-up from PR #178 review pass 4 (spec axis). Plausible, not reproduced.
Finding
Decision 1 (2026-10-02) says: "There must be one source of holiday identity, not two that can disagree." One narrow gap remains:
monitor_service.py:114never freezes the day. Calibration history for that day is backfilled later.occupancy_service.py~565-590) readsoccupancy_holidaysand says holiday.occupancy_repository.py~2842) and the spike reference (~3135) read only the business-day records, so they count the day as ordinary.Acceptance Criteria