feat(core): add calendar time fields to task schema #99

Merged

barrettruth merged 1 commit from feat/calendar-schema-v2 into main

2026-03-25 19:17:36 +00:00

barrettruth commented

2026-03-25 19:17:25 +00:00

Problem

Tasks only have a due date — no way to represent timed events with start/end, timezones, or all-day flags for calendar views.

Solution

Add startAt, endAt, allDay, timezone columns to tasks table. due stays as the deadline for urgency scoring — separate from the event window. Validation ensures endAt > startAt, valid IANA timezone, boolean allDay. Recurrence shifts startAt/endAt by the same delta as due. CLI types updated. Foundation for #91 and #62.

## Problem Tasks only have a `due` date — no way to represent timed events with start/end, timezones, or all-day flags for calendar views. ## Solution Add `startAt`, `endAt`, `allDay`, `timezone` columns to tasks table. `due` stays as the deadline for urgency scoring — separate from the event window. Validation ensures `endAt > startAt`, valid IANA timezone, boolean `allDay`. Recurrence shifts `startAt`/`endAt` by the same delta as `due`. CLI types updated. Foundation for #91 and #62.