follow-up(statistics): P3 cleanups from #116 review (comparison coverage) #120
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#120
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?
Follow-ups from the pass-2 review of #116 (#104 comparison coverage threshold). All P3; no P1/P2 remained.
Standards
compare_visitors/PeriodVisitors.per_day()zero-division guarantee. The comment says the clamped threshold ensures both sides cover at least one day, butPeriodQuality.coverageis1.0whenbusiness_days == 0, so a fully closed side with no data passes whenever the other side is partial. Callers prevent it today (earlyCLOSED_PERIOD; entrances skip closed cycles). Guard insideper_day()/compare_visitors(treatcovered_days == 0as non-comparable) or reword the comment to name the callers' guard.statistics_min_comparison_coveragerow (only the Pydantic rejection is tested).1.1intest_threshold_outside_its_bounds_is_rejected; useMIN_COMPARISON_COVERAGE_CEILING + 0.1.test_threshold_and_its_bounds_are_namedonly checks the constants are ordered.Spec
docs/api/README.md): "Each comparison states itsbasis", butbasisis null on withheld comparisons and onusual_weekday. Say "each calculated comparison exceptusual_weekday".🤖 Generated with Claude Code