Pacer 0.4.5

Fixes hourly usage filed under the wrong hour

Follow-up to v0.4.4, and the deeper half of the same problem.

Removing leftover rows only helped when the entry's new hour had no row yet. When both hours already had rows, the numbers were simply filed under the wrong one and nothing corrected them — on the maintainer's history, 64 of 1,440 hourly buckets held another hour's totals, one reading 289,000 output tokens too low while its neighbour ran 253,000 too high.

The cause: Pacer stored the date an entry belonged to but recalculated the hour every time it read one, using whatever timezone was current. A daylight-saving or timezone change silently refiled all your history. Daily totals were never affected because the date was stored rather than recalculated.

The hour is now stored alongside the date, so it can't move. Your existing history is rebuilt automatically on first launch after updating — it takes under a minute and never deletes anything.

If you want to check your own store: make verify-data.