v0.14.4: A fresh time-tracking week no longer inherits last week's rows

v0.14.3 fixed a race condition where switching weeks quickly could let a stale, out-of-order response overwrite a newer one. Some of you kept seeing the same thing afterward — a fresh week showing rows from a previous week, all empty — even with slow, deliberate single clicks, which meant it couldn’t be that race.

The real cause: each week’s row layout (which customer/project/activity rows appear, including empty ones you haven’t logged anything against yet) is supposed to be saved and looked up per specific week. But when a week had no layout of its own — true for any week you hadn’t personally rearranged rows in — the lookup silently fell back to a global, non-week-specific saved layout: whatever week you’d most recently worked in. So switching to any "fresh" week would deterministically show you the full row set from wherever you’d last been, with entries whose dates obviously didn’t match the new week’s columns.

A week with no saved layout of its own now returns empty, rather than falling back to your last-used week. You’ll only see rows for entries that actually exist in the week you’re looking at, unless you’ve explicitly arranged that specific week’s rows yourself.

Download v0.14.4 from the download page or pull the latest release tag.

No database migration is required for this release.