Split timeline width across lanes instead of stacking overlapping events

2026-09-07T07:07:32+00:00

The CSS gives every .calendar-event `left: 8px; right: 8px`, and the positioning code only ever overrode `left` (by 16px per column). So two events occupying the same slot both stayed full-width to the right edge and the later one simply covered the earlier one, leaving a 16px sliver. The column assignment was computing a correct answer that the layout then threw away. Reported as two yard-work chores rendering on top of each other. They sit at byte-identical timestamps because a bucket cycle stamps every item it activates with the same due_date, which makes this the maximally-bad case (identical top and height, so the overlap is total). Events now split the available width across the number of lanes in their overlap cluster, and a lone event keeps the full-width behaviour it had. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_018AwnALZL6bD4VBtATDVv3B

Fix swipe-nav false positives on scroll, shopping quick-add overflow

2026-08-30T20:46:36+00:00

Swipe-to-change-tab only ever compared horizontal touch delta against a 50px threshold, with no check against vertical movement -- an ordinary scroll through a long tab (the shopping list, in particular) drifts that far horizontally from natural thumb motion alone, and was getting misread as an intentional swipe. Since timeline sits right before shopping in TAB_ORDER, that's specifically what a rightward drift landed on: "shopping randomly jumps back to timeline." Now requires the horizontal delta to be at least 2x the vertical delta before treating it as a swipe instead of a scroll. Also fixed the shopping tab's inline quick-add row: the store

doot.git/web/static, branch master

Split timeline width across lanes instead of stacking overlapping events

Fix swipe-nav false positives on scroll, shopping quick-add overflow